Re: [Dovecot] I can acces my pop3 account but I can't send an email trough smtp
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Oct 2009, Ricky Tompu Breaky wrote: Sending failed: Your SMTP server does not support The server responded: 5.7.8 Error: authentication failed: generic failure. Choose a different authentication method. The server responded: 5.7.8 Error: authentication failed: generic failure The message will stay in the I'm stucked again. Please help me. Tell me where my mistake. Your mistake is that you believe Dovecot is a MTA. Check your postfix installation. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSsRXEnWSIuGy1ktrAQItQQgApKE+Xlvv95KgY9rVD/uyJMjNqfyrH/BV fVkkkBhoB6dcbbXkLd2tMMrjBD+2XbcazKkZ/QtibCn7lbodwvEtZO6wePjpOxvB T+GZ57mTCdnU4kmCtHphJJyk0Bsua7RFBQRlotRStWE9Qz9b/isBy8siSL6nHVom 3HH0UNssRDblJzeYM8zfjll/hm7KqgO5w3p4Iyfl/qhiwEuUedAOwVlGtYWRGIKY fZOathZ3PB0hfkL+7MkFiNOFangisfcDeoIhNuWXDJxeSeVMZU3GjCefquLni2lc iCOqvPGud0kApuGVuWHiPoaAg8PpPv/PNAnNJ9/+lIe1mYwC2wGVqg== =XTWC -END PGP SIGNATURE-
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Timo Sirainen ha scritto: On Wed, 2009-09-30 at 10:16 +0200, Marco Nenciarini wrote: Sep 30 06:26:15 server dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted There is no additional information from Timo's patch, Oh, annoying. There was a bug in the function it used, this fixes it: http://hg.dovecot.org/dovecot-1.2/rev/401e023c8c29 [snip] The only thing related I can think of is http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1 - did you have that patch applied? Although I couldn't reproduce the problem even with that reverted. Another day, another failure, now with both patches applied. Oct 1 06:26:14 server dovecot: pop3-login: Panic: Leaked file fd 5: dev 0.12 inode 1005 Oct 1 06:26:14 server dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Oct 1 06:26:14 server dovecot: dovecot: child 17609 (login) killed with signal 6 (core dumps disabled) Please note that the time is the same of previous days (just after daily cron execution) Regards, Marco -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4
[Dovecot] Compile dovecot 1.2.5 with managesieve patch 0.11.9?
Hi, is it possible to compile dovecot 1.2.5 with the managesieve patch 0.11.9 which is for dovecot 1.2.4 or is it better to wait if a new managesieve patch is released? Maybe 1.2.5 will work too? Thanks, Seba
Re: [Dovecot] Compile dovecot 1.2.5 with managesieve patch 0.11.9?
Hi Seba, is it possible to compile dovecot 1.2.5 with the managesieve patch 0.11.9 just tested this combination few days ago. works fine for me, but i haven't tested all the small thing yet. maybe there are minor issues, but it generally works. hendrik div-- LWsystems GmbH Co. KG ++ http://www.lw-systems.de/impressum [http://www.lw-systems.de/impressum] Tel: +49 (0)5403 / 5556 ++ Fax: +49 (0)5403 / 7 95 89 97 Ihr Spezialist für Linux, Open Source IT-Sicherheit ### ### LWsystems veranstaltet den LINUX SOLUTION DAY 2009 ### 29. Oktober 2009 ab 13.30 Uhr in Osnabrück ### Alle Details und Agenda unter: http://www.linux-solution-day.de [http://www.linux-solution-day.de/] ### ### Gleich anmelden: mailto:i...@linux-solution-day.de?subject=anmeldung [mailto:i...@linux-solution-day.de?subject=anmeldung] ### ++ LWsystems GmbH Co. KG Sitz der Gesellschaft: Tegelerweg 11, 49186 Bad Iburg Telefon +49 (0)5403 5556 Telefax +49 (0)5403 7958997 Handelsregister: Amtsgericht Osnabrück, HRA 110668 USt.-ID-Nr. DE23852211 Persönlich haftende Gesellschafterin: LWsystems Verwaltungs GmbH Sitz der Gesellschaft: Tegelerweg 11, 49186 Bad Iburg Handelsregister: Amtsgericht Osnabrück, HRB 63 Geschäftsführer: Dipl.-Ing. Ansgar H. Licher, Bad Iburg Dipl.-Ing. Martin Werthmöller, Ibbenbüren Für weitere Firmendetails zu LWsystems siehe / For further company details please look at: http://www.lw-systems.de/impressum [http://www.lw-systems.de/impressum] ++ /div
[Dovecot] imap crashed, (imap) killed with signal 11
There is an error in dovecot 1.2.5 when loggin in: dovecot: Error: child 14816 (imap) killed with signal 11
[Dovecot] imap crashed: (imap) killed with signal 11 in dovecot 1.2.5
Hi, I'm using dovecot 1.2.5 with mysql backend and seems in this new version
I have issues when loggin in, especially if there are mails in Inbox folder.
NOTE: version 1.2.4 worked perfectly and mysql was updated to version 5.0.86
from source code.
Here is my configuration and core dump:
/applications/dovecot-mail/sbin/dovecot --version
1.2.5
/applications/dovecot-mail/sbin/dovecot -n
# 1.2.5: /applications/dovecot-mail/conf/dovecot.conf
# OS: Linux 2.6.18-164.el5 i686 CentOS release 5.3 (Final) ext3
base_dir: /var/run/dovecot/
log_path: /var/log/dovecot.log
log_timestamp: %Y-%m-%d %H:%M:%S
protocols: imap imaps pop3s
login_dir: /var/run/dovecot/login
login_executable(default):
/applications/dovecot-mail/libexec/dovecot/imap-login
login_executable(imap):
/applications/dovecot-mail/libexec/dovecot/imap-login
login_executable(pop3):
/applications/dovecot-mail/libexec/dovecot/pop3-login
login_greeting: Hi buddy, got an account?
login_processes_count: 4
login_max_processes_count: 64
max_mail_processes: 1024
last_valid_uid: 10005
mail_privileged_group: mail
mail_location: mbox:/srv/mail/vmail/%d/%n
mail_debug: yes
maildir_copy_preserve_filename: yes
mbox_read_locks: dotlock fcntl
mail_drop_priv_before_exec: yes
mail_executable(default): /applications/dovecot-mail/libexec/dovecot/imap
mail_executable(imap): /applications/dovecot-mail/libexec/dovecot/imap
mail_executable(pop3): /applications/dovecot-mail/libexec/dovecot/pop3
mail_plugins(default): quota imap_quota
mail_plugins(imap): quota imap_quota
mail_plugins(pop3): quota
mail_plugin_dir(default): /applications/dovecot-mail/lib/dovecot/imap
mail_plugin_dir(imap): /applications/dovecot-mail/lib/dovecot/imap
mail_plugin_dir(pop3): /applications/dovecot-mail/lib/dovecot/pop3
imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh
tb-extra-mailbox-sep
imap_client_workarounds(pop3):
pop3_client_workarounds(default):
pop3_client_workarounds(imap):
pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh
auth default:
mechanisms: plain login
cache_size: 10240
cache_ttl: 1800
passdb:
driver: pam
args: cache_key=%u%r%l dovecot
passdb:
driver: sql
args: /applications/dovecot-mail/conf/dovecot-mysql.conf
userdb:
driver: sql
args: /applications/dovecot-mail/conf/dovecot-mysql.conf
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 432
user: postfix
group: postfix
master:
path: /var/run/dovecot/auth-master
mode: 432
user: dovecot
group: mail
grep -v '^ *\(#.*\)\?$' /applications/dovecot-mail/conf/dovecot-mysql.conf
driver = mysql
default_pass_scheme = PLAIN-MD5
connect = host=localhost dbname=mail user=mail password=XXX
password_query = SELECT password FROM mailbox WHERE username = '%u'
user_query = SELECT '/srv/mail/vmail/%d/%n' as home,
'maildir:/srv/mail/vmail/%d/%n' as mail, 10005 AS uid, 12 AS gid,
concat('dirsize:storage=',quota) AS quota FROM mailbox WHERE username ='%u'
AND active ='1'
gdb /applications/dovecot-mail/libexec/dovecot/imap `pwd`/core.20557
GNU gdb Fedora (6.8-27.el5)
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type show copying
and show warranty for details.
This GDB was configured as i386-redhat-linux-gnu...
(no debugging symbols found)
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols
found)...done.
Loaded symbols for /lib/ld-linux.so.2
Reading symbols from /lib/libpthread.so.0...(no debugging symbols
found)...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from
/applications/dovecot-mail/lib/dovecot/imap/lib10_quota_plugin.so...
(no debugging symbols found)...done.
Loaded symbols for
/applications/dovecot-mail/lib/dovecot/imap/lib10_quota_plugin.so
Reading symbols from
/applications/dovecot-mail/lib/dovecot/imap/lib11_imap_quota_plugin.so...(no
debugging symbols found)...done.
Loaded symbols for
/applications/dovecot-mail/lib/dovecot/imap/lib11_imap_quota_plugin.so
Reading symbols from /usr/lib/gconv/ISO8859-1.so...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/gconv/ISO8859-1.so
(no debugging symbols found)
Core was generated by `imap'.
Program terminated with signal 11, Segmentation fault.
[New process 20557]
#0 0x in ?? ()
(gdb) backtrace
#0 0x in ??
Re: [Dovecot] Compile dovecot 1.2.5 with managesieve patch 0.11.9?
On Thu, 1 Oct 2009, Seba wrote: is it possible to compile dovecot 1.2.5 with the managesieve patch 0.11.9 which is for dovecot 1.2.4 or is it better to wait if a new managesieve patch is released? Maybe 1.2.5 will work too? I have compiled this set, although finally I have changed the patch to match dovecot sources perfectly without fuzzes (just for having clear build :) Works perfectly, no problems occured (except some wrong configuration I have done :) Best regards, -- Jacek Osiecki jos...@ceti.pl GG:3828944 I don't want something I need. I want something I want.
Re: [Dovecot] imap crashed: (imap) killed with signal 11 in dovecot 1.2.5
On Thu, 1 Oct 2009, Robert Gabriel wrote: Hi, I'm using dovecot 1.2.5 with mysql backend and seems in this new version I have issues when loggin in, especially if there are mails in Inbox folder. NOTE: version 1.2.4 worked perfectly and mysql was updated to version 5.0.86 from source code. Here is my configuration and core dump: [...] Reading symbols from /applications/dovecot-mail/lib/dovecot/imap/lib10_quota_plugin.so... (no debugging symbols found)...done. Loaded symbols for /applications/dovecot-mail/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /applications/dovecot-mail/lib/dovecot/imap/lib11_imap_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /applications/dovecot-mail/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/gconv/ISO8859-1.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/ISO8859-1.so (no debugging symbols found) Core was generated by `imap'. Check the thread Problem with dict-quota, deliver killed by delivery attempt from last tuesday (29 Sep) - and Timo's answer. My dovecot 1.2.5 stopped crashing after applying this patch - which repairs dovecot crashing when using quota other than Maildir++: http://hg.dovecot.org/dovecot-1.2/rev/3132464fbe9c Best regards, -- Jacek Osiecki jos...@ceti.pl GG:3828944 I don't want something I need. I want something I want.
Re: [Dovecot] imap crashed: (imap) killed with signal 11 in dovecot 1.2.5
Sorry, but that patch doesn't do it for me, still is crashing after applying the patch. On Thu, Oct 1, 2009 at 13:13, Jacek Osiecki jos...@hybrid.pl wrote: On Thu, 1 Oct 2009, Robert Gabriel wrote: Hi, I'm using dovecot 1.2.5 with mysql backend and seems in this new version I have issues when loggin in, especially if there are mails in Inbox folder. NOTE: version 1.2.4 worked perfectly and mysql was updated to version 5.0.86 from source code. Here is my configuration and core dump: [...] Reading symbols from /applications/dovecot-mail/lib/dovecot/imap/lib10_quota_plugin.so... (no debugging symbols found)...done. Loaded symbols for /applications/dovecot-mail/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /applications/dovecot-mail/lib/dovecot/imap/lib11_imap_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /applications/dovecot-mail/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/gconv/ISO8859-1.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/ISO8859-1.so (no debugging symbols found) Core was generated by `imap'. Check the thread Problem with dict-quota, deliver killed by delivery attempt from last tuesday (29 Sep) - and Timo's answer. My dovecot 1.2.5 stopped crashing after applying this patch - which repairs dovecot crashing when using quota other than Maildir++: http://hg.dovecot.org/dovecot-1.2/rev/3132464fbe9c Best regards, -- Jacek Osiecki jos...@ceti.pl GG:3828944 I don't want something I need. I want something I want.
[Dovecot] Apple mail troubles
Hello I have an Apple computer user who has great problems using IMAP and Dovecot. Some same messages seems to stay in two or more folders and are impossible to erase from the Apple mail client Anyone has that kind of troubles ? Thanks
Re: [Dovecot] Apple mail troubles
Le 1 oct. 2009 à 13:57, Frank Bonnet a écrit : Hello I have an Apple computer user who has great problems using IMAP and Dovecot. Some same messages seems to stay in two or more folders and are impossible to erase from the Apple mail client Anyone has that kind of troubles ? No. Axel PS: Perhaps could you tell us a bit more (client and server side), so that really helpful answers may be provided. ;-)
Re: [Dovecot] Apple mail troubles
Axel Luttgens wrote: Le 1 oct. 2009 à 13:57, Frank Bonnet a écrit : Hello I have an Apple computer user who has great problems using IMAP and Dovecot. Some same messages seems to stay in two or more folders and are impossible to erase from the Apple mail client Anyone has that kind of troubles ? No. Axel PS: Perhaps could you tell us a bit more (client and server side), so that really helpful answers may be provided. ;-) Well OK If he try to read some messages with apple mail client some messages seems duplicated in several IMAP folders If I read those messages with mutt onto the server everything is clean
Re: [Dovecot] Apple mail troubles
Frank Bonnet schrieb: Axel Luttgens wrote: Le 1 oct. 2009 à 13:57, Frank Bonnet a écrit : Hello I have an Apple computer user who has great problems using IMAP and Dovecot. Some same messages seems to stay in two or more folders and are impossible to erase from the Apple mail client Anyone has that kind of troubles ? No. Axel PS: Perhaps could you tell us a bit more (client and server side), so that really helpful answers may be provided. ;-) Well OK If he try to read some messages with apple mail client some messages seems duplicated in several IMAP folders If I read those messages with mutt onto the server everything is clean apple mail has a long bug list with imap, as well many user dont use it rightly , possible the double, is one mail on imap and the same on a local copy sometime miracle happens when migration i.e a pop3 account to imap with apple mail i would recommend dont use it -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
Please always keep replies on list... On 10/1/2009 7:18 AM, Fredriksson Turbo wrote: But it seems that all mails that was received between 16:52:19 and 11:07:52 (which was the last mail that couldn't be delivered) is lost! Without logs, it is impossible to say what happened to the mails... Were they accepted, then lost? Or were they simply rejected? The error log say: deliver(EMAIL): 2009-09-30 11:07:52 Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted The info log say that everything was a-ok... So the mail was accepted, put in the spool, picked up for local delivery, spamchecked etc and when it was supposed to be put in a file in the mail directory, lost... This may be enough for Timo, but its always better to give the full logs of one of these transactions - not just the dovecot error log, but full system logs, showing the message entering the system, each step of processing, and ending with the final delivery (attempt)... -- Best regards, Charles Marcus I.T. Director Media Brokers International, Inc. 678.514.6200 x224 678.514.6299 fax
Re: [Dovecot] Apple mail troubles
Robert Schetterer wrote: Frank Bonnet schrieb: Axel Luttgens wrote: Le 1 oct. 2009 à 13:57, Frank Bonnet a écrit : Hello I have an Apple computer user who has great problems using IMAP and Dovecot. Some same messages seems to stay in two or more folders and are impossible to erase from the Apple mail client Anyone has that kind of troubles ? No. Axel PS: Perhaps could you tell us a bit more (client and server side), so that really helpful answers may be provided. ;-) Well OK If he try to read some messages with apple mail client some messages seems duplicated in several IMAP folders If I read those messages with mutt onto the server everything is clean apple mail has a long bug list with imap, as well many user dont use it rightly , possible the double, is one mail on imap and the same on a local copy sometime miracle happens when migration i.e a pop3 account to imap with apple mail i would recommend dont use it OK thank you , but Mac users are difficult to convinct ;-)
Re: [Dovecot] Apple mail troubles
On Thu, Oct 01, 2009 at 02:44:53PM +0200, Frank Bonnet wrote: OK thank you , but Mac users are difficult to convinct ;-) I have used it with the 'Mail.app' that came with Leopard and I'm using it with Snow Leopard with no (major) problems nowadays. It has some problems when listing/subscribing to several namespaces, but I did not encounter the problem you describe. Maybe you can provide more details, what Mail.app, 'dovecot -n'? Regards Thomas
Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
On 1 okt 2009, at 14.42, Charles Marcus wrote: Please always keep replies on list... Sorry. A 'Reply' didn't send it where I expected it to... On 10/1/2009 7:18 AM, Fredriksson Turbo wrote: But it seems that all mails that was received between 16:52:19 and 11:07:52 (which was the last mail that couldn't be delivered) is lost! Without logs, it is impossible to say what happened to the mails... Were they accepted, then lost? Or were they simply rejected? The error log say: deliver(EMAIL): 2009-09-30 11:07:52 Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted The info log say that everything was a-ok... So the mail was accepted, put in the spool, picked up for local delivery, spamchecked etc and when it was supposed to be put in a file in the mail directory, lost... This may be enough for Timo, but its always better to give the full logs of one of these transactions - not just the dovecot error log, but full system logs, showing the message entering the system, each step of processing, and ending with the final delivery (attempt)... Fair enough. But I never saved the tail when the problem occured. I can now extract this again from the info log (getting everything between 11:06 to 11:08 which should be within the problem time...). Who should I send it to? It's 181 lines to 'privatize' and I'd prefere not to send a unprivatized file to the list...
[Dovecot] Capability info in hello message not complete?
Hi, one Fedora user complains about not some troubles after update to dovecot 1.2. He suspects wrong capability information given by dovecot 1.2 In dovecot.conf he uses imap_capability= option. While response to 'A CAPABILITY' respects imap_capability value, the capability info in hello message does not. for imap_capability=IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN A CAPABILITY response is: * CAPABILITY IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN but hello message is: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. But it seems even when imap_capability is not used capability in hello message is not complete: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. vs. * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH STARTTLS AUTH=PLAIN is this expected? Do you think capability information in hello message really can befool clients? Regards, Michal Hlavinka
Re: [Dovecot] imap crashed: (imap) killed with signal 11 in dovecot 1.2.5
This will help you: http://hg.dovecot.org/dovecot-1.2/rev/3132464fbe9c 1.2.6 should come out this week.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] imap crashed: (imap) killed with signal 11 in dovecot 1.2.5
Whops, should have read more mails before answering.. On Thu, 2009-10-01 at 13:24 +0200, Robert Gabriel wrote: Sorry, but that patch doesn't do it for me, still is crashing after applying the patch. It really should have fixed it. If not, get a gdb backtrace. http://dovecot.org/bugreport.html signature.asc Description: This is a digitally signed message part
Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
On Thu, 2009-10-01 at 14:58 +0200, Fredriksson Turbo wrote: Who should I send it to? It's 181 lines to 'privatize' and I'd prefere not to send a unprivatized file to the list... I can take a look at it.. Although the most important log line is the one where it calls deliver and shows what deliver replied. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Apple mail troubles
On Oct 1, 2009, at 8:16 AM, Frank Bonnet wrote: Axel Luttgens wrote: Le 1 oct. 2009 à 13:57, Frank Bonnet a écrit : Hello I have an Apple computer user who has great problems using IMAP and Dovecot. Some same messages seems to stay in two or more folders and are impossible to erase from the Apple mail client Anyone has that kind of troubles ? No. Axel PS: Perhaps could you tell us a bit more (client and server side), so that really helpful answers may be provided. ;-) Well OK If he try to read some messages with apple mail client some messages seems duplicated in several IMAP folders If I read those messages with mutt onto the server everything is clean It sounds like your local caches in Mac Mail are confused if everything looks fine in Mutt. Try selecting a folder with duplicate messages and then hit Mailbox Rebuild. That should delete the local cache for that folder and re-download all those messages, which should remove duplicates. Did you recently switch from a different IMAP server to dovecot? The double messages problem usually happens when IMAP UIDs change on the server, and usually happens when you switch to dovecot from something else. We recently migrated from courier to dovecot and had to convert everyone's UIDs from courier to dovecot to ensure people didn't get double messages. Of course, I have seen double messages in Mac Mail happen without a migration and it usually relates to a quota (filesystem, not IMAP quota) problem where clients try to delete a message and there's no room left to move it to the Trash folder. In that case you usually need to up the quota and rebuild that folder's local cache. -David Warden
Re: [Dovecot] Capability info in hello message not complete?
On Thu, 2009-10-01 at 14:59 +0200, Michal Hlavinka wrote: Hi, one Fedora user complains about not some troubles after update to dovecot 1.2. He suspects wrong capability information given by dovecot 1.2 In dovecot.conf he uses imap_capability= option. While response to 'A CAPABILITY' respects imap_capability value, the capability info in hello message does not. for imap_capability=IMAP4 IMAP4rev1 ACL NAMESPACE CHILDREN SORT QUOTA THREAD=ORDEREDSUBJECT UNSELECT IDLE STARTTLS AUTH=PLAIN I suppose he's using Dovecot as a proxy? Because Dovecot doesn't support IMAP4 or THREAD=ORDEREDSUBJECT. but hello message is: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS AUTH=PLAIN] Dovecot ready. Hmm. Yeah.. But it seems even when imap_capability is not used capability in hello message is not complete: .. is this expected? Do you think capability information in hello message really can befool clients? The capability in greeting message is short on purpose. It's only enough capabilities to get client logged in. After login Dovecot sends an updated full capability list to the client. It uses a few different tricks to get most clients understand the change. So the only potential problem I see here is if client understands the greeting capability and permanently remembers that the server supports LITERAL+, ID and ENABLE after login but the destination server actually doesn't. The other capabilities are relevant only before login. I'm not entirely sure what, if anything, I should do about this. I'd anyway like to hear what exactly is the problem and with what client, preferably with IMAP traffic logs showing what's happening wrong. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
On 10/1/2009, Fredriksson Turbo (tu...@bayour.com) wrote: Fair enough. But I never saved the tail when the problem occured. I can now extract this again from the info log (getting everything between 11:06 to 11:08 which should be within the problem time...). Just find the messageID and grep the logs for that, so you only have the lines pertinent to that one transaction. Who should I send it to? The list... It's 181 lines If you grep for the messageID, it won't be. One of mine is about 6 lines... to 'privatize' and I'd prefere not to send a unprivatized file to the list... 6 lines should be simple enough to anonymize - although, I consider security through obscurity to be essentially a waste of time and effort. Of course, if you're logging passwords, those should *certainly* be snipped... -- Best regards, Charles
Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
On 10/1/2009, Timo Sirainen (t...@iki.fi) wrote: Who should I send it to? It's 181 lines to 'privatize' and I'd prefere not to send a unprivatized file to the list... I can take a look at it.. Although the most important log line is the one where it calls deliver and shows what deliver replied. That was in his original (at least I think its what you're asking for): deliver(EMAIL): 2009-09-30 11:07:52 Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted -- Best regards, Charles
Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
On Thu, 2009-10-01 at 09:18 -0400, Charles Marcus wrote: I can take a look at it.. Although the most important log line is the one where it calls deliver and shows what deliver replied. That was in his original (at least I think its what you're asking for): deliver(EMAIL): 2009-09-30 11:07:52 Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted No, I mean in the Postfix log. This should have triggered temporary failure exit code and Postfix should have put it back to queue. If it didn't, I'd guess the Postfix log tells why. Or perhaps if there was something in the middle (spam and virus scanners?) maybe their logs show something and maybe they are the reason mails got lost. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] imap crashed: (imap) killed with signal 11 in dovecot 1.2.5
On Thu, Oct 1, 2009 at 15:03, Timo Sirainen t...@iki.fi wrote: Whops, should have read more mails before answering.. On Thu, 2009-10-01 at 13:24 +0200, Robert Gabriel wrote: Sorry, but that patch doesn't do it for me, still is crashing after applying the patch. It really should have fixed it. If not, get a gdb backtrace. http://dovecot.org/bugreport.html Seems that downloading and setting up the rc version or whatever is called, works http://hg.dovecot.org/dovecot-1.2/rev/3132464fbe9c this one did the job. Thanks!
Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
On 10/1/2009 9:22 AM, Timo Sirainen wrote: deliver(EMAIL): 2009-09-30 11:07:52 Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted No, I mean in the Postfix log. Ack, right, you did say ... where it CALLS deliver... Sorry... -- Best regards, Charles
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
On Thu, 2009-10-01 at 09:28 +0200, Marco Nenciarini wrote: The only thing related I can think of is http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1 - did you have that patch applied? Although I couldn't reproduce the problem even with that reverted. Another day, another failure, now with both patches applied. Oct 1 06:26:14 server dovecot: pop3-login: Panic: Leaked file fd 5: dev 0.12 inode 1005 That's the pty's fd I think, probably from dovecot --exec-mail because normally dovecot master process closes them at startup.. Did you check if two dovecot processes were running when this happened? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote: Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Has this happened to you again? Do you run expire-tool or some other dovecot --exec-mail command? Or was there anything else run in cron just before the first of the above errors happened? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Timo Sirainen ha scritto: On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote: Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Has this happened to you again? Do you run expire-tool or some other dovecot --exec-mail command? Or was there anything else run in cron just before the first of the above errors happened? No, it hasn't happened again. The only errors I found in my logs is like the following one Oct 1 09:20:29 delta01 dovecot: pop3-login: Disconnected (no auth attempts): rip=213.136.170.137, lip=10.68.1.31 Oct 1 09:20:29 delta01 dovecot: pop3-login: Panic: Leaked file fd 5: dev 0.12 inode 1005 Oct 1 09:20:29 delta01 dovecot: dovecot: Temporary failure in creating login processes, slowing down for now Oct 1 09:20:29 delta01 dovecot: pop3-login: Disconnected (no auth attempts): rip=62.94.181.36, lip=10.68.1.31 Oct 1 09:20:29 delta01 dovecot: dovecot: child 12936 (login) killed with signal 6 (core dumps disabled) The only dovecot-related command run by cron daily is expire-tool I've checked the list of running processes but there is only one /usr/sbin/dovecot running with its children Marco -- - |Marco Nenciarini| Debian/GNU Linux Developer - Plug Member | | mnen...@prato.linux.it | http://www.prato.linux.it/~mnencia | - Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Timo Sirainen wrote: On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote: Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Has this happened to you again? Do you run expire-tool or some other dovecot --exec-mail command? Or was there anything else run in cron just before the first of the above errors happened? Hi Timo, No, this hasn't happened again. It is dovecot 2.1.5 with no extra plugins. I don't run any dovecot related crons. The only crons that ran just before it happened were unrelated rotate two unrelated logs 23 minutes before download and update some spamassassin rules 12 minutes before update Mailman archive search indices 9 minutes before All these run daily. The problem occurred after upgrading from 2.1.4 to 2.1.5. 2.1.4 had been running for weeks with no problem. The problem started with 2.1.5 when it had been running about 6 days and 20 hours. and continued until I restarted dovecot a day and a half later. There was a power outage at the server last Friday night when Dovecot had been running only 4 days since the last restart, so at this point, Dovecot has been running continuously for 5 days and 6 hours, so the problem may or may not recur within the next few days. My dovecot -n is at http://dovecot.org/pipermail/dovecot/2009-September/042943.html, and some more detail from my maillog is at http://dovecot.org/pipermail/dovecot/2009-September/042959.html. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
[Dovecot] Password and special caracter
Problem : I have a problem with special character in the password. Character like ! * é are deleted My configuration : - a smtp server with Postfix 2.6 and Dovcot 1.1.11. - a windows 2003 server with active directory for accounts and boxes I use SMTP / SASL on my postfix 2.6 to authenticate my remote laptop users (allow legitimate users to relay mail). To do that, I use SASL Dovecot fonctionnality and ldap request to verify login/password who are declared on a server in Windows 2003 (Active Directory). It works fine with simple password but not with complex password. I have a problem with special character in the password. Character like ! * é are deleted before comparaison. Any idea ? Regards
[Dovecot] Password and special caracter
Problem : I have a problem with special character in the password. Character like ! * é are deleted My configuration : - a smtp server with Postfix 2.6 and Dovcot 1.1.11. - a windows 2003 server with active directory for accounts and boxes I use SMTP / SASL on my postfix 2.6 to authenticate my remote laptop users (allow legitimate users to relay mail). To do that, I use SASL Dovecot fonctionnality and ldap request to verify login/password who are declared on a server in Windows 2003 (Active Directory). It works fine with simple password but not with complex password. I have a problem with special character in the password. Character like ! * é are deleted before comparaison. Any idea ? Regards
Re: [Dovecot] OT: IMAP folder aliases
Timo, * Rob Middleton robm-dove...@centenary.org.au: On 25/09/2009 11:14 PM, Patrick Ben Koetter wrote: It seems that there is no standard for folder names that deal with typical message classes such as drafts, outbox, sent, spam etc. At least there's no common sense on a naming convention that tells how client should handle this. XLIST may deal with this in the future. XLIST seems to be pretty proprietary. Have you had a look at LIST-EXTENDED instead? It's a standard and one would 'simply' need to register the required extensions to get a mapping: IMAP4 LIST Command Extensions http://www.rfc-editor.org/rfc/rfc5258.txt It seems to be capable to map the relations we are dicussion here. Something along these lines: S: * LIST (\Subscribed \NoInferiors) / inbox S: * LIST (\Subscribed \drafts \NoInferiors) / Drafts S: * LIST (\Subscribed \trash \NoInferiors) / Trash S: * LIST (\Subscribed \sent \NoInferiors) / Sent-Mail S: * LIST (\Subscribed \outbox \NoInferiors) / Out S: * LIST (\Subscribed \templates \NoInferiors) / Templates p...@rick
Re: [Dovecot] OT: IMAP folder aliases
On Thu, 2009-10-01 at 16:51 +0200, Patrick Ben Koetter wrote: XLIST seems to be pretty proprietary. Have you had a look at LIST-EXTENDED instead? See http://www.ietf.org/mail-archive/web/morg/current/msg00208.html thread, especially http://www.ietf.org/mail-archive/web/morg/current/msg00212.html signature.asc Description: This is a digitally signed message part
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
On 10/1/2009, Mark Sapiro (m...@msapiro.net) wrote: No, this hasn't happened again. It is dovecot 2.1.5 Ok, at first I thought this was just a silly typo, but... The problem occurred after upgrading from 2.1.4 to 2.1.5. 2.1.4 had been running for weeks with no problem. The problem started with 2.1.5 Mark, you obviously just gave away the fact that you have access to a time machine... Please, if you would, post these future versions somewhere where I can get at them! lol ;)
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Mark Sapiro wrote: Timo Sirainen wrote: On Tue, 2009-09-22 at 20:23 -0700, Mark Sapiro wrote: Sep 22 19:07:15 sbh16 dovecot: pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5): Operation not permitted Has this happened to you again? Do you run expire-tool or some other dovecot --exec-mail command? Or was there anything else run in cron just before the first of the above errors happened? Hi Timo, No, this hasn't happened again. It is dovecot 2.1.5 with no extra plugins. I don't run any dovecot related crons. The only crons that ran just before it happened were unrelated rotate two unrelated logs 23 minutes before download and update some spamassassin rules 12 minutes before update Mailman archive search indices 9 minutes before All these run daily. The problem occurred after upgrading from 2.1.4 to 2.1.5. 2.1.4 had been running for weeks with no problem. The problem started with 2.1.5 when it had been running about 6 days and 20 hours. and continued until I restarted dovecot a day and a half later. There was a power outage at the server last Friday night when Dovecot had been running only 4 days since the last restart, so at this point, Dovecot has been running continuously for 5 days and 6 hours, so the problem may or may not recur within the next few days. My dovecot -n is at http://dovecot.org/pipermail/dovecot/2009-September/042943.html, and some more detail from my maillog is at http://dovecot.org/pipermail/dovecot/2009-September/042959.html. Also, FYI, I do not have the http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1 patch installed. I do have the patch installed to log the fd for this error, but I don't have the fix http://hg.dovecot.org/dovecot-1.2/rev/401e023c8c29 for the logging function installed. Would you prefer that I just let Dovecot run a few days and see if the problem recurs, or should I install the logging function fix now and perhaps wait another 7 or 8 days before there may be another failure. Also, as far as I know, the only dovecot processes running at the time of the failure were a single master and it's auth and pop3 and imap login children. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Re: [Dovecot] OT: IMAP folder aliases
* Timo Sirainen t...@iki.fi: On Thu, 2009-10-01 at 16:51 +0200, Patrick Ben Koetter wrote: XLIST seems to be pretty proprietary. Have you had a look at LIST-EXTENDED instead? See http://www.ietf.org/mail-archive/web/morg/current/msg00208.html thread, especially http://www.ietf.org/mail-archive/web/morg/current/msg00212.html Okay. I'll see if I can catch up on morg. p...@rick signature.asc Description: Digital signature
Re: [Dovecot] Password and special caracter
Sounds more like SASL than Dovecot. I had my Dovecot authenticate against DB in UTF8 encoding, and it can handle Chinese character for password. Can your smtp authentication allows special character? Best, Joseph On 1-Oct-09, at 10:40 AM, Gilles Albusac wrote: Problem : I have a problem with special character in the password. Character like ! * é are deleted My configuration : - a smtp server with Postfix 2.6 and Dovcot 1.1.11. - a windows 2003 server with active directory for accounts and boxes I use SMTP / SASL on my postfix 2.6 to authenticate my remote laptop users (allow legitimate users to relay mail). To do that, I use SASL Dovecot fonctionnality and ldap request to verify login/password who are declared on a server in Windows 2003 (Active Directory). It works fine with simple password but not with complex password. I have a problem with special character in the password. Character like ! * é are deleted before comparaison. Any idea ? Regards
Re: [Dovecot] pop3-login: Fatal: io_loop_handle_add: epoll_ctl(1, 5):
Charles Marcus wrote: On 10/1/2009, Mark Sapiro (m...@msapiro.net) wrote: No, this hasn't happened again. It is dovecot 2.1.5 Ok, at first I thought this was just a silly typo, but... The problem occurred after upgrading from 2.1.4 to 2.1.5. 2.1.4 had been running for weeks with no problem. The problem started with 2.1.5 Mark, you obviously just gave away the fact that you have access to a time machine... Please, if you would, post these future versions somewhere where I can get at them! Sorry, no time machine, no future versions. Just finger dyslexia. As everyone probably knows, I meant 1.2.5 and 1.2.4. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Re: [Dovecot] Password and special caracter
Doubtful it's an smtp issue, as all authenication over smtp uses base64 I'll see if I can cause the issue in my setup though. Quoting Joseph Yee j...@ca.afilias.info: Sounds more like SASL than Dovecot. I had my Dovecot authenticate against DB in UTF8 encoding, and it can handle Chinese character for password. Can your smtp authentication allows special character? Best, Joseph On 1-Oct-09, at 10:40 AM, Gilles Albusac wrote: Problem : I have a problem with special character in the password. Character like ! * é are deleted My configuration : - a smtp server with Postfix 2.6 and Dovcot 1.1.11. - a windows 2003 server with active directory for accounts and boxes I use SMTP / SASL on my postfix 2.6 to authenticate my remote laptop users (allow legitimate users to relay mail). To do that, I use SASL Dovecot fonctionnality and ldap request to verify login/password who are declared on a server in Windows 2003 (Active Directory). It works fine with simple password but not with complex password. I have a problem with special character in the password. Character like ! * é are deleted before comparaison. Any idea ? Regards
Re: [Dovecot] Password and special caracter
On Thu, 2009-10-01 at 16:40 +0200, Gilles Albusac wrote: It works fine with simple password but not with complex password. I have a problem with special character in the password. Character like ! * é are deleted before comparaison. My guess is that it's related to LDAP. Are you using auth_bind=yes? signature.asc Description: This is a digitally signed message part
[Dovecot] Encryption Plugin
Hi, There was a discussion a few months ago about a plugin for encrypting email before it hit the disk on the server, and doing transparent decryption while serving data to the client, see: http://www.dovecot.org/list/dovecot/2009-July/041262.html We have a client/user who is interested in such a plugin, and I was wondering if there has been any progress on it yet. In our particular case, server-side on-the-fly decryption would be acceptable. This service is useful in the case of a somewhat paranoid user who does not want the IT staff to have direct access to their email, without going through some major hoops (http://hushmail.com actually offers both server and client side decryption for these reasons). The way I would imagine the plugin working is public-key encryption being done on the message as it was being delivered (plug in to dovecot's deliver). Then when a client connects, the private key is decrypted with the user's password and used to decrypt the messages on the fly. Depending on performance, it may be an idea to convert messages to use symmetric with rotating keys encrypted with the public key encryption. If this were going to be done, I would think an IMAP protocol extension may be an idea so client-side encryption would be an option as well, so there would be end-to-end security.
Re: [Dovecot] Password and special caracter
Seems to all be working for me. I tested using the password: te...@#$%^*é My first test was using postfix - dovecot - mysql This was to verify if sending email via postfix would make it to dovecot and though dovecot without getting messed up. Test passed. My next test was to setup dovecot to authenicate against win2003 active directory. This was just to test that from dovecot - ad would work without issues. This test also passed. My LDAP config for dovecot: hosts = ip_of_ad_server auth_bind = yes auth_bind_userdn = DOMAIN\%u ldap_version = 3 base = dc=domain, dc=com Quoting Timo Sirainen t...@iki.fi: On Thu, 2009-10-01 at 16:40 +0200, Gilles Albusac wrote: It works fine with simple password but not with complex password. I have a problem with special character in the password. Character like ! * é are deleted before comparaison. My guess is that it's related to LDAP. Are you using auth_bind=yes?
Re: [Dovecot] Encryption Plugin
On Thu, 2009-10-01 at 11:49 -0400, Patrick McLean wrote: There was a discussion a few months ago about a plugin for encrypting email before it hit the disk on the server, and doing transparent decryption while serving data to the client, see: http://www.dovecot.org/list/dovecot/2009-July/041262.html We have a client/user who is interested in such a plugin, and I was wondering if there has been any progress on it yet. Not from my side, no idea if someone else has done anything. My comments about zlib compression also apply to encryption: http://www.dovecot.org/list/dovecot/2009-June/040181.html The way I would imagine the plugin working is public-key encryption being done on the message as it was being delivered (plug in to dovecot's deliver). Then when a client connects, the private key is decrypted with the user's password and used to decrypt the messages on the fly. Depending on performance, it may be an idea to convert messages to use symmetric with rotating keys encrypted with the public key encryption. Easiest way to get started would be to just execute gpg or maybe libgpgme. If this were going to be done, I would think an IMAP protocol extension may be an idea so client-side encryption would be an option as well, so there would be end-to-end security. Maybe the messages could be just encrypted using regular pgp or S/MIME encryption so clients that support those already could open them. Although that wouldn't keep the message headers encrypted. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] I can acces my pop3 account but I can't send an email trough smtp
OK, then. Thank you. === On Thu, 1 Oct 2009 09:15:28 +0200 (CEST) Steffen Kaiser skdove...@smail.inf.fh-brs.de wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 1 Oct 2009, Ricky Tompu Breaky wrote: Sending failed: Your SMTP server does not support The server responded: 5.7.8 Error: authentication failed: generic failure. Choose a different authentication method. The server responded: 5.7.8 Error: authentication failed: generic failure The message will stay in the I'm stucked again. Please help me. Tell me where my mistake. Your mistake is that you believe Dovecot is a MTA. Check your postfix installation. Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSsRXEnWSIuGy1ktrAQItQQgApKE+Xlvv95KgY9rVD/uyJMjNqfyrH/BV fVkkkBhoB6dcbbXkLd2tMMrjBD+2XbcazKkZ/QtibCn7lbodwvEtZO6wePjpOxvB T+GZ57mTCdnU4kmCtHphJJyk0Bsua7RFBQRlotRStWE9Qz9b/isBy8siSL6nHVom 3HH0UNssRDblJzeYM8zfjll/hm7KqgO5w3p4Iyfl/qhiwEuUedAOwVlGtYWRGIKY fZOathZ3PB0hfkL+7MkFiNOFangisfcDeoIhNuWXDJxeSeVMZU3GjCefquLni2lc iCOqvPGud0kApuGVuWHiPoaAg8PpPv/PNAnNJ9/+lIe1mYwC2wGVqg== =XTWC -END PGP SIGNATURE-
Re: [Dovecot] Expire plugin: wrong mailbox separators in database?
Hate to bump this, but is there nobody who uses the expire plugin and can confirm my observations? I'd love to use the expire plugin to delete old messages filed in spam folders but as it is now I can't get it to work with the wrong mailbox separators in the table entries. Andreas -- Andreas Ntaflos GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4 signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Expire plugin: wrong mailbox separators in database?
Andreas Ntaflos wrote: Hate to bump this, but is there nobody who uses the expire plugin and can confirm my observations? I'd love to use the expire plugin to delete old messages filed in spam folders but as it is now I can't get it to work with the wrong mailbox separators in the table entries. Andreas Your observations look reasonable to me. Looks like the expire plugin needs to be fixed so that other separator characters can be used. -- -Eric 'shubes'
