- dovecot - dovecot.org

[Dovecot] v1.3.UNSTABLE branch is now available
by Timo Sirainen 04 Apr '09

04 Apr '09

v1.2.rc1 + config rewrite + multi-dbox: http://hg.dovecot.org/dovecot-1.3/

1 0

[Dovecot] v1.2.rc1 released
by Timo Sirainen 03 Apr '09

03 Apr '09

http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc1.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc1.tar.gz.sig I think it's time to get v1.2.0 out soon. Shared mailbox code is beginning to look like it's working and other features should work fine also. I don't really see any reasons to delay it, so please start testing and let's get the last bugs found and fixed quickly. I'm also going to start v1.3 branch soon with configuration rewrite and multi-dbox support. Changes since beta4: * Renamed THREAD X-REFERENCES2 to THREAD REFS (from INTHREAD draft) + When a process is killed, show the signal code and the sending process's pid and uid. + quota-fs: Added support for NFS group quota. - Several fixes to shared mailboxes and ACLs - Removed umask setting. We're nowadays creating practically all files with proper umasks. - acl: Dropped default ACL cache timeout from 5 minutes to 30 seconds. - fts-solr fixes - virtual mailbox fixes - Write to main index file less often.

2 2

[Dovecot] Missing mail_max_userip_connections setting
by Thomas M Goerger 03 Apr '09

03 Apr '09

Hi, I'm having a problem with a webmail client trying to open multiple IMAP connections with dovecot, and hitting a cap. I see from the error logs from this program that it's hitting the mail_max_userip_connections cap, but I'm not seeing this value as defined in the dovecot.conf file. Would this automatically get set to a certain value by default if it's not present? Thanks, ************************************************************************* * Tom Goerger - Email/Unix System Administrator * * * * University of Minnesota Email: tmg(a)umn.edu * * Operations, Infrastructure and Architecture Phone: 4-5804 * * Internet Services Office: 626J WBOB * * * *************************************************************************

2 1

[Dovecot] Maildir files with mtime in the future
by Holger Weiss 03 Apr '09

03 Apr '09

If Maildir storage is used, the mtime of a given Maildir file is set to the message's INTERNALDATE. Now, when a client APPENDs a message to an IMAP mailbox, the client may optionally specify the INTERNALDATE: | If a date-time is specified, the internal date SHOULD be set in the | resulting message; otherwise, the internal date of the resulting | message is set to the current date and time by default. [ ftp://ftp.fu-berlin.de/doc/rfc/rfc3501.txt (6.3.11. APPEND Command) ] However, if the client does so, Dovecot will set the mtime of the Maildir file in question to the date specified by the client even if it's in the future. Since files with an mtime in the future can cause all sorts of trouble (e.g., they might get backed up repeatedly by incremental backups), it would be nice if Dovecot would (optionally?) use the current time if the client specifies a time in the future. For example, we use the following patch: ---------- 8< ---------------------------------------- 8< ---------- diff --git a/src/imap/cmd-append.c b/src/imap/cmd-append.c index 0b22fd5..b7e42b9 100644 --- a/src/imap/cmd-append.c +++ b/src/imap/cmd-append.c @@ -319,6 +319,12 @@ static bool cmd_append_continue_parsing(struct client_command_context *cmd) return cmd_append_cancel(ctx, nonsync); } + if (internal_date != (time_t)-1 && internal_date > time(NULL)) { + /* the client specified a time in the future, set it to now. */ + internal_date = (time_t)-1; + timezone_offset = 0; + } + if (ctx->msg_size == 0) { /* no message data, abort */ client_send_tagline(cmd, "NO Can't save a zero byte message."); ---------- 8< ---------------------------------------- 8< ---------- Holger

3 8

[Dovecot] 1.2 beta4, crash with ACL
by Oli Schacher 03 Apr '09

03 Apr '09

Hi I'm betatesting the new acl features in dovecot 1.2. System: Centos 5.2, dovecot 1.2beta4 built with the spec file from http://dl.atrpms.net/all/dovecot.spec I set up two accounts (sales@domain, oli@domain), I could access them both without problems (testing with Thunderbird) Then I tried to share the sales INBOX as descibed in http://wiki.dovecot.org/SharedMailboxes/Shared: 1 setacl INBOX oli(a)domain.ch lrs 1 OK Setacl complete. 1 logout * BYE Logging out 1 OK Logout completed. Connection closed by foreign host. After that, I could not login to oli's box anymore, thunderbird would just reconnect and imap crashes over and over again server log: Apr 3 12:17:23 testbox dovecot: child 5695 (imap) killed with signal 11 (core dumped) Apr 3 12:17:23 testbox dovecot: imap-login: Login: user=<oli(a)domain.ch>, method=PLAIN, rip=<removed>, lip=<removed> backtrace (not sure if I've done this correctly): This GDB was configured as "i386-redhat-linux-gnu"... (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". Attaching to program: /usr/libexec/dovecot/imap, process 2140 ptrace: No such process. 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/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 /usr/lib/dovecot/imap/lib01_acl_plugin.so...done. Loaded symbols for /usr/lib/dovecot/imap/lib01_acl_plugin.so Reading symbols from /usr/lib/dovecot/imap/lib02_imap_acl_plugin.so...done. Loaded symbols for /usr/lib/dovecot/imap/lib02_imap_acl_plugin.so Reading symbols from /usr/lib/dovecot/imap/lib10_quota_plugin.so...done. Loaded symbols for /usr/lib/dovecot/imap/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/imap/lib11_imap_quota_plugin.so...done. Loaded symbols for /usr/lib/dovecot/imap/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/dovecot/imap/lib20_expire_plugin.so...done. Loaded symbols for /usr/lib/dovecot/imap/lib20_expire_plugin.so Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x0011a664 in acl_shared_namespaces_add (ns=0x97cc720) at acl-shared-storage.c:52 52 acl-shared-storage.c: No such file or directory. in acl-shared-storage.c dovecot -n # 1.2.beta4: /etc/dovecot.conf # OS: Linux 2.6.18-92.1.22.el5 i686 CentOS release 5.2 (Final) protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/dovecot.pem ssl_key_file: /etc/dovecot.pem disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Fumail Dovecot ready. mail_privileged_group: mail mail_drop_priv_before_exec: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): acl imap_acl quota imap_quota expire mail_plugins(imap): acl imap_acl quota imap_quota expire mail_plugins(pop3): quota expire mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle imap_client_workarounds(imap): outlook-idle imap_client_workarounds(pop3): namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: shared/%%d/%%n location: maildir:/%%h/Maildir/shared/%%u list: children subscriptions: yes auth default: mechanisms: plain login passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot-sql.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: fumail group: fumail plugin: quota: dict:::proxy::quotadict quota_rule: *:storage=10M:messages=1000 quota_warning: storage=95%% /usr/local/bin/quotawarning.py 95 quota_warning2: storage=75%% /usr/local/bin/quotawarning.py 75 acl: vfile:/etc/dovecot-acls acl_shared_dict: file:/etc/dovecot/dovecot-shared.db expire: Trash 30 Trash/* 30 Spam 14 expire_dict: proxy::expire dict: quotadict: mysql:/etc/dovecot/dovecot-dict-quota.conf expire: mysql:/etc/dovecot/dovecot-dict-expire.conf Is this a dovecot bug or did I something wrong? Thanks Oli

2 1

[Dovecot] ACL changes not respected by already loged in clients
by Sascha Wilde 03 Apr '09

03 Apr '09

Hi *, and yet another ACL problem. ;-) User A allows User B to access his mailbox foobar: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. l login userA secret l OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH ACL RIGHTS=texk ANNOTATEMORE] Logged in s setacl "INBOX/foobar" "B(a)example.com" eilprwtsd s OK Setacl complete. g getacl INBOX/foobar * ACL "INBOX/foobar" "B(a)example.com" eilprwtsd "A(a)example.com" lrwstipekxacd User B logs in to dovecot and sees the newly accessible mailbox: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. l login zwei 2 l OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH ACL RIGHTS=texk ANNOTATEMORE] Logged in l list "" "*" * LIST (\Noselect \HasChildren) "/" "user" * LIST (\Noselect \HasChildren) "/" "user/A(a)example.com" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "INBOX/Gesendet" * LIST (\HasChildren) "/" "user/A(a)example.com/foobar" l OK List completed. se select "user/A(a)example.com/foobar" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UIDVALIDITY 1236104897] UIDs valid * OK [UIDNEXT 2] Predicted next UID * OK [HIGHESTMODSEQ 1] Now User A changes his mind: s setacl "INBOX/foobar" "B(a)example.com" "" s OK Setacl complete. g getacl INBOX/foobar * ACL "INBOX/foobar" "A(a)example.com" lrwstipekxacd g OK Getacl completed. but as long as User B stays loged in, he is not affected, in fact he still can read A's mails: se select "user/A(a)example.com/foobar" * OK [CLOSED] * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 0 RECENT * OK [UIDVALIDITY 1236104897] UIDs valid * OK [UIDNEXT 2] Predicted next UID * OK [HIGHESTMODSEQ 1] se OK [READ-WRITE] Select completed. f101 fetch 1 FAST * 1 FETCH (FLAGS (\Seen) INTERNALDATE "04-Mar-2009 13:11:06 +0100" RFC822.SIZE 3652) f101 OK Fetch completed. I think ACL changes should take immediate effect, or at least should be re-checked in reasonable intervals (which imo shouldn't exceed a few seconds). cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

4 5

[Dovecot] v 1.1.13 / GSSAPI / Timeout waiting for handshake from auth server
by Jahnke-Zumbusch, Dirk 03 Apr '09

03 Apr '09

Dear all, I am trying to setup Dovecot with GSSAPI support. For testing purposes gssapi is the only method allowed for login. As I cannot login to my mailbox, I'vo got two questions about the following log entries: dovecot: Info: auth-worker(default): passwd-file /dovecot/store/db/test-userdb: Read 3 users dovecot: Info: auth(default): new auth connection: pid=3915 dovecot: Info: auth(default): client in: AUTH 1 GSSAPI service=imap lip=131.169.*.* rip=131.169.*.* lport=143 rport=35779 dovecot: Info: auth(default): gssapi(?,131.169.40.218): Obtaining credentials for imap(a)my.host.name dovecot: Error: imap-login: Timeout waiting for handshake from auth server. my pid=3918, input bytes=0 1. I am puzzled about the credentials "imap(a)my.host.name" being obtained; shouldn't this be something like "imap/my.host.name(a)MY.REALM" ? 2. what does "Timeout waiting for handshake from auth server." mean? Who is trying to handshake with whom? Any ideas? Best regards, Dirk -- Dirk Jahnke-Zumbusch Deutsches Elektronen-Synchrotron DESY IT Information Fabrics Member of the Helmholtz Association D-22603 Hamburg Notkestrasse 85 / 22607 Hamburg T: +49-40-899.81760 F: +49-40-899.41760 dirk.jahnke-zumbusch(a)desy.de

3 2

[Dovecot] Time moved backwards errors
by Bloke 03 Apr '09

03 Apr '09

Hello, I am experiencing a number of 'Time moved backwards errors' such as: Mar 27 11:38:20 host-78-129-239-60 dovecot: imap-login: Time just moved backwards by 729 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards Mar 27 15:20:10 host-78-129-239-60 dovecot: Time just moved backwards by 4214 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards Mar 29 11:08:59 host-78-129-239-60 dovecot: imap-login: Time just moved backwards by 4341 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards on my Centos 5.2 openvz - based VPS I have raised the issue with my VPS provider, who are responding that 'the jury is still out' as to whether this is a system, or Dovecot problem. Reading the TimeMovedBackwards article on the Dovecot wiki, and the kernel mailing list thread referred to on it, it would seem quite apparent that this is caused by a failure of the gettimeofday() function to reliably return the correct value. If anyone has any advice as to how I could proceed to fix this (I currently have a watch on the Dovecot service which restarts it after any failures) or how I should best phrase this to get it resolved 'upstream' by the VPS provider, I would be very grateful. Thank you, Patrick Vale

7 12

[Dovecot] dbox benchmarks
by Timo Sirainen 03 Apr '09

03 Apr '09

http://hg.dovecot.org/dovecot-dbox-redesign/ Looks like multi-dbox scales pretty nicely. Even after 100k messages the peak saved msgs/sec is the same as the initial saved msgs/sec, even if the average slows down somewhat. I tested this by first deleting mailbox, then running "imaptest" for a second to get saving to start writing several fields to dovecot.index.cache file. Then ran imaptest for 60 seconds that did nothing but save messages using IMAP APPEND commands. The summary is that multi-dbox is almost 10x as fast as maildir when fsync is disabled and 2,5 faster with fsyncing: fsync_disable=yes: multi-dbox : ~1700 -> ~1500 msgs/sec, 90842 msgs/60 sec single-dbox: ~1700 -> ~1400 msgs/sec, 86149 msgs/60 sec maildir : ~330 -> ~110 msgs/sec, 9789 msgs/60 sec fsync_disable=no: multi-dbox : ~220 -> ~170 msgs/sec, 10113 msgs/60 sec maildir : ~100 -> ~70 msgs/sec, 4123 msgs/60 sec Also I just noticed that saving messages with two clients gets a peak of 2200 msgs/sec, most likely because two CPU cores can be used then. Hmm. I guess if there were no locking it should have reached 3400 msgs/sec, but it's better than no performance increase. And the raw data: multi-dbox, fsync_disable=yes imaptest clients=1 secs=1;imaptest clients=1 msgs=1000000 - logout=0 append=100,0 secs=60 Logi Sele Appe 100% 100% 100% 1 1 1759 1/ 1 0 0 1424 1/ 1 0 0 1734 1/ 1 ... 0 0 1701 1/ 1 0 0 1640 1/ 1 0 0 778 1/ 1 0 0 1305 1/ 1 0 0 1598 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 1 1 90842 multi-dbox, fsync_disable=no imaptest clients=1 secs=1;imaptest clients=1 msgs=1000000 - logout=0 append=100,0 secs=60 Logi Sele Appe 100% 100% 100% 1 1 209 1/ 1 0 0 227 1/ 1 0 0 208 1/ 1 ... 0 0 203 1/ 1 0 0 145 1/ 1 0 0 156 1/ 1 0 0 180 1/ 1 0 0 162 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 1 1 10113 maildir, fsync_disable=yes Logi Sele Appe 100% 100% 100% 1 1 331 1/ 1 0 0 311 1/ 1 0 0 288 1/ 1 ... 0 0 96 1/ 1 0 0 119 1/ 1 0 0 111 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 1 1 9789 maildir, fsync_disable=no Logi Sele Appe 100% 100% 100% 1 1 77 1/ 1 0 0 101 1/ 1 0 0 45 1/ 1 ... 0 0 52 1/ 1 0 0 67 1/ 1 0 0 89 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 1 1 4123 single-dbox, fsync_disable=yes imaptest clients=1 secs=1;imaptest clients=1 msgs=1000000 - logout=0 append=100,0 secs=60 Logi Sele Appe 100% 100% 100% 1 1 1765 1/ 1 0 0 1715 1/ 1 0 0 1764 1/ 1 ... 0 0 1722 1/ 1 0 0 1679 1/ 1 0 0 1678 1/ 1 0 0 828 1/ 1 0 0 1467 1/ 1 0 0 1469 1/ 1 0 0 1149 1/ 1 0 0 1135 1/ 1 Totals: Logi Sele Appe 100% 100% 100% 1 1 86149

3 4

[Dovecot] An issue of I login my mail server from webmail client
by Alan Zheng 03 Apr '09

03 Apr '09

Dear all: I have a really strange issue, that is when I login my mail server from webmail client (I used SquirrelMail, by the way, I have modified squirrelmail's timeout value, that means not since squirrelmail timeout), I will got timeout issue when I login about 5PM ~ 10PM everyday (it works fine on other time, I also check my cron, that looks no problem), and during this time, I also cannot connect my 993 port with openssl like this: openssl s_client -connect myDomainName:993 But when I use mail client (such as outlook) to access dovecot, that works fine, and during 5PM ~ 10PM, my web site also works fine, and once I restart computer if I can not login during 5PM ~ 10PM from webmail client. that will work fine. can you try to help me? below is my configure of dovecot. *dovecot -n # 1.0.7: /etc/dovecot.conf log_path: /var/run/dovecot/maillog info_log_path: /var/run/dovecot/maillog protocols: imaps ssl_parameters_regenerate: 0 verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/Maildir mail_debug: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: convert_mail: mbox:~/Mail:INBOX=/var/mail/%u* -- Best Regards Alan Zheng

1 0