July 2005 - dovecot - dovecot.org

[Dovecot] Thread sorting problem
by Greg Trounson 24 Aug '05

24 Aug '05

I've just installed Dovecot on a Debian Sarge machine and am seeing some very strange thread sorting. In Mozilla Mail and Thunderbird on both Fedora and Debian clients my threads served up by Dovecot look like this (number denotes message time): |-11 | `-12 |-2 |-3 |-4 | `-5 | `-6 | `-7 | `-8 |-1 `-9 `-10 Where the exact same threads served by Sendmail/imap look like this: |-1 |-2 |-3 |-4 | `-5 | `-6 | `-7 | `-8 |-9 | `-10 |-11 | `-12 Squirrelmail shows the threads correctly in both cases too, so I suspect there might be something funny going on with how Thunderbird handles Maildir threads. I notice that Dovecot doesn't support the THREAD=ORDEREDSUBJECT capability, might that have something to do with it? thanks, Greg

3 2

[Dovecot] Dovecot Deliver?
by Marc Perkel 24 Aug '05

24 Aug '05

I guess Dovecot has an LDA called deliver. What is it and how do I use it? Or is it ready to be used. can't find any docs on it. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

9 18

[Dovecot] Well, "Hard filesystem quota can also be problematic"
by Jeroen Scheerder 24 Aug '05

24 Aug '05

"Hard filesystem quota can also be problematic", quoth <http://www.dovecot.org/>. Since we actually use quota for our userbasg, this merited further investigation. Using 1.0-stable, we enabled quota on /var and /users filesystems, and set very low quota for a test account. Then we had some mail delivered on it, and we moved some messages about. At some point, Thunderbird started to croak about "The current command did not succeed. The mail server responded: Internal error occured. Refer to server log for more information. [<timestamp>].", "The current command did not succeed. The mail server responded: .", "The current command did not succeed. The mail server responded: Out of disk space." This I can live with. Hoever, at some point in our experiments we also found that a mailbox (mbox format) that did contain a few dozen messages suddenly was truncated to 0 bytes. Not so hot. Can anyone tell me whether or not there is, or will be, some way of using dovecot on a system with quota without risk of data loss when quota limits are reached? How do people cope with this? Regards, Jeroen. p.s. That first error message gave rise to the enclosed patch. diff -r -c1 dovecot-1.0-stable-patched/doc/auth-protocol.txt dovecot-1.0-stable/doc/auth-protocol.txt *** dovecot-1.0-stable-patched/doc/auth-protocol.txt Wed Jul 27 08:08:35 2005 --- dovecot-1.0-stable/doc/auth-protocol.txt Mon Jan 31 17:37:54 2005 *************** *** 171,173 **** ! FAIL reply means an internal error occurred. Usually either a configuration mistake or temporary error caused by lost resource (eg. database down). --- 171,173 ---- ! FAIL reply means an internal error occured. Usually either a configuration mistake or temporary error caused by lost resource (eg. database down). diff -r -c1 dovecot-1.0-stable-patched/doc/index.txt dovecot-1.0-stable/doc/index.txt *** dovecot-1.0-stable-patched/doc/index.txt Wed Jul 27 08:08:39 2005 --- dovecot-1.0-stable/doc/index.txt Mon Jan 31 17:37:54 2005 *************** *** 89,91 **** processes has to scan the mailbox, other processes simply check from the ! log file what changes occurred. --- 89,91 ---- processes has to scan the mailbox, other processes simply check from the ! log file what changes occured. diff -r -c1 dovecot-1.0-stable-patched/src/imap/client.h dovecot-1.0-stable/src/imap/client.h *** dovecot-1.0-stable-patched/src/imap/client.h Wed Jul 27 08:08:26 2005 --- dovecot-1.0-stable/src/imap/client.h Mon Jan 31 17:37:54 2005 *************** *** 68,70 **** /* Read a number of arguments. Returns TRUE if everything was read or ! FALSE if either needs more data or error occurred. */ int client_read_args(struct client *client, unsigned int count, --- 68,70 ---- /* Read a number of arguments. Returns TRUE if everything was read or ! FALSE if either needs more data or error occured. */ int client_read_args(struct client *client, unsigned int count, diff -r -c1 dovecot-1.0-stable-patched/src/imap/cmd-idle.c dovecot-1.0-stable/src/imap/cmd-idle.c *** dovecot-1.0-stable-patched/src/imap/cmd-idle.c Wed Jul 27 08:08:30 2005 --- dovecot-1.0-stable/src/imap/cmd-idle.c Mon Jan 31 17:37:54 2005 *************** *** 159,161 **** } else if (ctx->sync_pending) { ! /* more changes occurred while we were sending changes to client */ --- 159,161 ---- } else if (ctx->sync_pending) { ! /* more changes occured while we were sending changes to client */ diff -r -c1 dovecot-1.0-stable-patched/src/lib/file-cache.h dovecot-1.0-stable/src/lib/file-cache.h *** dovecot-1.0-stable-patched/src/lib/file-cache.h Wed Jul 27 08:06:28 2005 --- dovecot-1.0-stable/src/lib/file-cache.h Mon Jan 31 17:37:55 2005 *************** *** 12,14 **** /* Read data from file, returns how many bytes was actually read or -1 if ! error occurred. */ ssize_t file_cache_read(struct file_cache *cache, uoff_t offset, size_t size); --- 12,14 ---- /* Read data from file, returns how many bytes was actually read or -1 if ! error occured. */ ssize_t file_cache_read(struct file_cache *cache, uoff_t offset, size_t size); diff -r -c1 dovecot-1.0-stable-patched/src/lib/istream.h dovecot-1.0-stable/src/lib/istream.h *** dovecot-1.0-stable-patched/src/lib/istream.h Wed Jul 27 08:06:32 2005 --- dovecot-1.0-stable/src/lib/istream.h Mon Jan 31 17:37:54 2005 *************** *** 60,62 **** /* Like i_stream_next_line(), but reads for more data if needed. Returns NULL ! if more data is needed or error occurred. */ char *i_stream_read_next_line(struct istream *stream); --- 60,62 ---- /* Like i_stream_next_line(), but reads for more data if needed. Returns NULL ! if more data is needed or error occured. */ char *i_stream_read_next_line(struct istream *stream); diff -r -c1 dovecot-1.0-stable-patched/src/lib/read-full.h dovecot-1.0-stable/src/lib/read-full.h *** dovecot-1.0-stable-patched/src/lib/read-full.h Wed Jul 27 08:06:38 2005 --- dovecot-1.0-stable/src/lib/read-full.h Mon Jan 31 17:37:54 2005 *************** *** 3,5 **** ! /* Read data from file. Returns -1 if error occurred, or 0 if EOF came before everything was read, or 1 if all was ok. */ --- 3,5 ---- ! /* Read data from file. Returns -1 if error occured, or 0 if EOF came before everything was read, or 1 if all was ok. */ diff -r -c1 dovecot-1.0-stable-patched/src/lib/strfuncs.c dovecot-1.0-stable/src/lib/strfuncs.c *** dovecot-1.0-stable-patched/src/lib/strfuncs.c Wed Jul 27 08:06:47 2005 --- dovecot-1.0-stable/src/lib/strfuncs.c Mon May 16 23:15:10 2005 *************** *** 100,102 **** if (len < 0) { ! /* some error occurred */ len = 0; --- 100,102 ---- if (len < 0) { ! /* some error occured */ len = 0; diff -r -c1 dovecot-1.0-stable-patched/src/lib/write-full.h dovecot-1.0-stable/src/lib/write-full.h *** dovecot-1.0-stable-patched/src/lib/write-full.h Wed Jul 27 08:06:43 2005 --- dovecot-1.0-stable/src/lib/write-full.h Mon Jan 31 17:37:55 2005 *************** *** 3,5 **** ! /* Write data into file. Returns -1 if error occurred, or 0 if all was ok. If there's not enough space in device, -1 with ENOSPC is returned, and --- 3,5 ---- ! /* Write data into file. Returns -1 if error occured, or 0 if all was ok. If there's not enough space in device, -1 with ENOSPC is returned, and diff -r -c1 dovecot-1.0-stable-patched/src/lib-imap/imap-parser.h dovecot-1.0-stable/src/lib-imap/imap-parser.h *** dovecot-1.0-stable-patched/src/lib-imap/imap-parser.h Wed Jul 27 08:07:00 2005 --- dovecot-1.0-stable/src/lib-imap/imap-parser.h Mon Jan 31 17:37:55 2005 *************** *** 88,90 **** need to do that. Returns number of arguments read (may be less than count ! in case of EOL), -2 if more data is needed or -1 if error occurred. --- 88,90 ---- need to do that. Returns number of arguments read (may be less than count ! in case of EOL), -2 if more data is needed or -1 if error occured. diff -r -c1 dovecot-1.0-stable-patched/src/lib-mail/message-parser.h dovecot-1.0-stable/src/lib-mail/message-parser.h *** dovecot-1.0-stable-patched/src/lib-mail/message-parser.h Wed Jul 27 08:06:56 2005 --- dovecot-1.0-stable/src/lib-mail/message-parser.h Mon Jan 31 17:37:55 2005 *************** *** 112,114 **** input stream is non-blocking and more data needs to be read, -1 when all is ! done or error occurred (see stream's error status). */ int message_parse_header_next(struct message_header_parser_ctx *ctx, --- 112,114 ---- input stream is non-blocking and more data needs to be read, -1 when all is ! done or error occured (see stream's error status). */ int message_parse_header_next(struct message_header_parser_ctx *ctx, diff -r -c1 dovecot-1.0-stable-patched/src/lib-sql/sql-api.h dovecot-1.0-stable/src/lib-sql/sql-api.h *** dovecot-1.0-stable-patched/src/lib-sql/sql-api.h Wed Jul 27 08:06:51 2005 --- dovecot-1.0-stable/src/lib-sql/sql-api.h Mon Jan 31 17:37:55 2005 *************** *** 23,25 **** /* Go to next row, returns 1 if ok, 0 if this was the last row or -1 if error ! occurred. This needs to be the first call for result. */ int sql_result_next_row(struct sql_result *result); --- 23,25 ---- /* Go to next row, returns 1 if ok, 0 if this was the last row or -1 if error ! occured. This needs to be the first call for result. */ int sql_result_next_row(struct sql_result *result); diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/index/maildir/maildir-sync.c dovecot-1.0-stable/src/lib-storage/index/maildir/maildir-sync.c *** dovecot-1.0-stable-patched/src/lib-storage/index/maildir/maildir-sync.c Wed Jul 27 08:08:03 2005 --- dovecot-1.0-stable/src/lib-storage/index/maildir/maildir-sync.c Mon Jan 31 17:37:55 2005 *************** *** 7,9 **** We want to be as efficient as we can. The most efficient way to ! check if changes have occurred is to stat() the new/ and cur/ directories and uidlist file - if their mtimes haven't changed, --- 7,9 ---- We want to be as efficient as we can. The most efficient way to ! check if changes have occured is to stat() the new/ and cur/ directories and uidlist file - if their mtimes haven't changed, *************** *** 14,16 **** then make a modification. Such modifications wouldn't get noticed ! until a new modification occurred later. --- 14,16 ---- then make a modification. Such modifications wouldn't get noticed ! until a new modification occured later. diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/mail-storage.c dovecot-1.0-stable/src/lib-storage/mail-storage.c *** dovecot-1.0-stable-patched/src/lib-storage/mail-storage.c Wed Jul 27 08:07:58 2005 --- dovecot-1.0-stable/src/lib-storage/mail-storage.c Mon Jan 31 17:37:55 2005 *************** *** 12,14 **** #define CRITICAL_MSG \ ! "Internal error occurred. Refer to server log for more information." #define CRITICAL_MSG_STAMP CRITICAL_MSG " [%Y-%m-%d %H:%M:%S]" --- 12,14 ---- #define CRITICAL_MSG \ ! "Internal error occured. Refer to server log for more information." #define CRITICAL_MSG_STAMP CRITICAL_MSG " [%Y-%m-%d %H:%M:%S]" diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/mail-storage.h dovecot-1.0-stable/src/lib-storage/mail-storage.h *** dovecot-1.0-stable-patched/src/lib-storage/mail-storage.h Wed Jul 27 08:07:25 2005 --- dovecot-1.0-stable/src/lib-storage/mail-storage.h Mon Jan 31 17:37:55 2005 *************** *** 225,227 **** /* Deinitialize mailbox list request. Returns FALSE if some error ! occurred while listing. */ int mail_storage_mailbox_list_deinit(struct mailbox_list_context *ctx); --- 225,227 ---- /* Deinitialize mailbox list request. Returns FALSE if some error ! occured while listing. */ int mail_storage_mailbox_list_deinit(struct mailbox_list_context *ctx); *************** *** 239,241 **** ! /* Returns the error message of last occurred error. */ const char *mail_storage_get_last_error(struct mail_storage *storage, --- 239,241 ---- ! /* Returns the error message of last occured error. */ const char *mail_storage_get_last_error(struct mail_storage *storage, *************** *** 252,254 **** const char *name, enum mailbox_open_flags flags); ! /* Close the box. Returns FALSE if some cleanup errors occurred, but the mailbox was closed anyway. */ --- 252,254 ---- const char *name, enum mailbox_open_flags flags); ! /* Close the box. Returns FALSE if some cleanup errors occured, but the mailbox was closed anyway. */ *************** *** 373,378 **** /* Get the time message was received (IMAP INTERNALDATE). ! Returns (time_t)-1 if error occurred. */ time_t (*get_received_date)(struct mail *mail); /* Get the Date-header in mail. Timezone is in minutes. ! Returns (time_t)-1 if error occurred, 0 if field wasn't found or couldn't be parsed. */ --- 373,378 ---- /* Get the time message was received (IMAP INTERNALDATE). ! Returns (time_t)-1 if error occured. */ time_t (*get_received_date)(struct mail *mail); /* Get the Date-header in mail. Timezone is in minutes. ! Returns (time_t)-1 if error occured, 0 if field wasn't found or couldn't be parsed. */ *************** *** 380,385 **** /* Get the full virtual size of mail (IMAP RFC822.SIZE). ! Returns (uoff_t)-1 if error occurred */ uoff_t (*get_virtual_size)(struct mail *mail); /* Get the full physical size of mail. ! Returns (uoff_t)-1 if error occurred */ uoff_t (*get_physical_size)(struct mail *mail); --- 380,385 ---- /* Get the full virtual size of mail (IMAP RFC822.SIZE). ! Returns (uoff_t)-1 if error occured */ uoff_t (*get_virtual_size)(struct mail *mail); /* Get the full physical size of mail. ! Returns (uoff_t)-1 if error occured */ uoff_t (*get_physical_size)(struct mail *mail); diff -r -c1 dovecot-1.0-stable-patched/src/lib-storage/subscription-file/subscription-file.h dovecot-1.0-stable/src/lib-storage/subscription-file/subscription-file.h *** dovecot-1.0-stable-patched/src/lib-storage/subscription-file/subscription-file.h Wed Jul 27 08:08:08 2005 --- dovecot-1.0-stable/src/lib-storage/subscription-file/subscription-file.h Mon Jan 31 17:37:55 2005 *************** *** 9,11 **** ! /* Deinitialize subscription file listing. Returns FALSE if some error occurred while listing. */ --- 9,11 ---- ! /* Deinitialize subscription file listing. Returns FALSE if some error occured while listing. */ diff -r -c1 dovecot-1.0-stable-patched/src/login-common/ssl-proxy-gnutls.c dovecot-1.0-stable/src/login-common/ssl-proxy-gnutls.c *** dovecot-1.0-stable-patched/src/login-common/ssl-proxy-gnutls.c Wed Jul 27 08:08:22 2005 --- dovecot-1.0-stable/src/login-common/ssl-proxy-gnutls.c Mon Jan 31 17:37:55 2005 *************** *** 82,84 **** if (verbose_ssl) { ! /* fatal error occurred */ if (error == GNUTLS_E_FATAL_ALERT_RECEIVED) { --- 82,84 ---- if (verbose_ssl) { ! /* fatal error occured */ if (error == GNUTLS_E_FATAL_ALERT_RECEIVED) { diff -r -c1 dovecot-1.0-stable-patched/src/login-common/ssl-proxy.h dovecot-1.0-stable/src/login-common/ssl-proxy.h *** dovecot-1.0-stable-patched/src/login-common/ssl-proxy.h Wed Jul 27 08:08:14 2005 --- dovecot-1.0-stable/src/login-common/ssl-proxy.h Mon Jan 31 17:37:55 2005 *************** *** 9,11 **** /* establish SSL connection with the given fd, returns a new fd which you ! must use from now on, or -1 if error occurred. Unless -1 is returned, the given fd must be simply forgotten. */ --- 9,11 ---- /* establish SSL connection with the given fd, returns a new fd which you ! must use from now on, or -1 if error occured. Unless -1 is returned, the given fd must be simply forgotten. */

12 19

[Dovecot] Assertion failure in mail-index-transaction.c
by Todd Burroughs 15 Aug '05

15 Aug '05

This just started happening with the current CVS version (2005-07-23). The "user" is a monitoring tool that we use called Sitescope. It has been monitoring dovecot for a long time and I've never seen an error before this. Deleting the .imap directory seems to have resolved the problem. This did not start until several hours into running the new version. dovecot: Jul 25 19:45:38 Error: 16590 IMAP(sitescope): file mail-index-transaction.c: line 588 (mail_index_update_flags_range): assertion failed: (seq1 <= seq2 && seq1 > 0) dovecot: Jul 25 19:45:39 Error: child 16590 (imap) killed with signal 6 (gdb) bt full #0 0xffffe410 in ?? () No symbol table info available. #1 0xbffff2c8 in ?? () No symbol table info available. #2 0x00000006 in ?? () No symbol table info available. #3 0x00004207 in ?? () No symbol table info available. #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 No symbol table info available. #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 No symbol table info available. #6 0x0809acca in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x4207 <Address 0x4207 out of bounds>) at failures.c:374 No locals. #7 0x0809b0e4 in i_panic ( format=0x80a7a8c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 No locals. #8 0x08083411 in mail_index_update_flags_range (t=0x80d2320, seq1=0, seq2=0, modify_type=MODIFY_ADD, flags=128) at array.h:99 rec = Variable "rec" is not available. (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff2c8 in ?? () #2 0x00000006 in ?? () #3 0x00004207 in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809acca in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x4207 <Address 0x4207 out of bounds>) at failures.c:374 #7 0x0809b0e4 in i_panic ( format=0x80a7a8c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x08083411 in mail_index_update_flags_range (t=0x80d2320, seq1=0, seq2=0, modify_type=MODIFY_ADD, flags=128) at array.h:99 #9 0x0806e262 in mbox_sync_read_index_syncs (sync_ctx=0xbffff710, uid=1, sync_expunge_r=0xbffff58c) at mbox-sync.c:213 #10 0x0806ec1e in mbox_sync_loop (sync_ctx=0xbffff710, mail_ctx=0xbffff680, partial=Variable "partial" is not available. ) at mbox-sync.c:1070 #11 0x080704c0 in mbox_sync (mbox=0x80c4bc0, flags=Variable "flags" is not available. ) at mbox-sync.c:1441 #12 0x08071379 in mbox_storage_sync_init (box=0x80c4bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mbox-sync.c:1766 #13 0x0808f221 in mailbox_sync_init (box=0x0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mail-storage.c:334 #14 0x0805ed08 in imap_sync_nonselected (box=0x80c4bc0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at imap-sync.c:171 #15 0x08058166 in _cmd_select_full (cmd=0x80beba8, readonly=0) at cmd-select.c:39 #16 0x080582f1 in cmd_select (cmd=0x80beba8) at cmd-select.c:92 #17 0x0805997b in _client_input (context=0x80beb68) at client.c:334 #18 0x080a029a in io_loop_handler_run (ioloop=0x80bd9b0) at ioloop-poll.c:184 #19 0x0809f8c9 in io_loop_run (ioloop=0x80bd9b0) at ioloop.c:218 #20 0x08060847 in main (argc=1, argv=0xbffffa24, envp=0xbffffa2c) at main.c:229 (gdb) p seq1 $1 = 0 (gdb) p seq2 $2 = 0 (gdb) p *t $3 = {refcount = 1, view = 0x80d0120, appends = {buffer = 0x0, element_size = 0}, first_new_seq = 466, last_new_seq = 0, expunges = { buffer = 0x0, element_size = 0}, updates = {buffer = 0x0, element_size = 0}, last_update_idx = 0, pre_hdr_change = '\0' <repeats 119 times>, pre_hdr_mask = '\0' <repeats 119 times>, post_hdr_change = '\0' <repeats 119 times>, post_hdr_mask = '\0' <repeats 119 times>, ext_rec_updates = {buffer = 0x0, element_size = 0}, ext_resizes = {buffer = 0x0, element_size = 0}, ext_resets = {buffer = 0x0, element_size = 0}, keyword_updates = { buffer = 0x0, element_size = 0}, keyword_resets = {buffer = 0x0, element_size = 0}, cache_trans_ctx = 0x0, hide_transaction = 0, no_appends = 0, external = 1, pre_hdr_changed = 0, post_hdr_changed = 0, log_updates = 1}

2 1

[Dovecot] Dovecot hangs randomly
by Jacob Elder 15 Aug '05

15 Aug '05

I have been run into a weird problem with dovecot. We have 4 identical servers running dovecot, serving both IMAP and POP3 clients. Every few hours, clients start timing out after the PASS command. Here is what the process tree looks like at that time: 6718 ? Ss 0:00 /usr/sbin/dovecot 6719 ? S 0:00 \_ dovecot-auth 6881 ? S 0:00 | \_ dovecot-auth 6883 ? S 0:00 | \_ dovecot-auth 6890 ? S 0:00 | \_ dovecot-auth 6928 ? S 0:00 | \_ dovecot-auth 6929 ? S 0:00 | \_ dovecot-auth 6934 ? S 0:00 | \_ dovecot-auth 6936 ? S 0:00 | \_ dovecot-auth 6939 ? S 0:00 | \_ dovecot-auth 6720 ? S 0:00 \_ imap-login 6721 ? S 0:00 \_ imap-login 6722 ? S 0:00 \_ imap-login 6782 ? S 0:00 \_ pop3-login 6808 ? S 0:00 \_ pop3-login 6884 ? S 0:00 \_ pop3-login 6885 ? S 0:00 \_ pop3-login 6886 ? S 0:00 \_ pop3-login 6887 ? S 0:00 \_ pop3-login 6888 ? S 0:00 \_ pop3-login 6889 ? S 0:00 \_ pop3-login 6931 ? S 0:00 \_ pop3-login 6937 ? S 0:00 \_ pop3-login 6940 ? S 0:00 \_ pop3-login After running invoke-rc.d dovecot stop, the process tree looks like this: 6782 ? S 0:00 pop3-login 6808 ? S 0:00 pop3-login 6881 ? S 0:00 dovecot-auth 6883 ? S 0:00 dovecot-auth 6884 ? S 0:00 pop3-login 6885 ? S 0:00 pop3-login 6886 ? S 0:00 pop3-login 6887 ? S 0:00 pop3-login 6889 ? S 0:00 pop3-login 6890 ? S 0:00 dovecot-auth 6928 ? S 0:00 dovecot-auth 6929 ? S 0:00 dovecot-auth 6931 ? S 0:00 pop3-login 6934 ? S 0:00 dovecot-auth 6936 ? S 0:00 dovecot-auth 6939 ? S 0:00 dovecot-auth If I run "killall -9 dovecot-auth pop3-login; invoke-rc.d dovecot start", service resumes for a few hours. This happens both on 2.6.8 and 2.4.27. This is Debian testing, 512 MB RAM, about 20 users per server. We use libnss-ldap and libpam-ldap for all users other than root. Samba, SSH, saslauthd (for Postfix), login, etc all work as expected. There is a 5th server that is identical to the other 4 except is NOT using libpam-ldap, and dovecot does not hang on this machine. Any ideas? -- Jacob Elder

2 2

[Dovecot] Documentation
by Enrique 15 Aug '05

15 Aug '05

Hello, I have added a few questions and answers to the wiki, about stuff that caused me long hunts when trying to set up dovecot with maildir storage. Some of it I have gleaned from the source. Some of it is actually already documented, but I had not been able to spot it when I needed it. At the time of writing I had a particular advantage: I did not know, or had mostly forgotten, the peculiarities of the imap protocol. I say 'advantage', because I think that when writing documentation it is important, yet difficult, to see things from the perspective of a user that is quite ignorant, although not stupid. These need the documentation most, and they are in majority. (Some will say the "stupid" ones are in majority, but writing for them is almost futile anyway. Anyway, I doubt they are a majority; average intelligence is adequate for all normal tasks. What we often judge and condemn as "stupidity" is most often the result of a different perspective that _we_ are too limited to understand.) Since I am not yet too spoiled, and yet recently had my hands (or rather my eyes) in the source, this may be a golden opportunity to produce some more documentation. I therefore urge you to suggest what I should look at and write about. Do you have any ideas about how the documentation should be organized? some questions are not strictly dovecot or even imap questions, yet they arise quite naturally for an administrator that is migrating to dovecot or to imap in general. The existing migration documentation was not as usefull to me as it could have been because I was both migrating to imap from a non-imap solutions, and from mbox to maildir, both at the same time. That placed me in a particularly "ignorant" position. It is quite likely that much of what I write is not exactly true. I have suggested procmail as a delivery agent for maildir stores, because it is the only one I know about at the moment. I just occurred to me that I have not even checked if /bin/mail (on GNU/Linux systems) can do it. Any ideas? I have not (yet) found out anything about the CONTROL= part of the mail environment. Should I write something about it? Is it usefull for system administrators to know about it? What is it? Regards -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

9 21

[Dovecot] Binc IMAP "IMAPdir" style layout
by Martin Lucina 15 Aug '05

15 Aug '05

Hi, I'm in the process of migrating several years worth of mail to be accessible via an IMAP server. Some time ago, I evaluated both Binc IMAP and Dovecot and found Dovecot to be much faster on large folders, which is quite important to me. One thing I did not however manage to determine from the documentation on namespaces is whether or not it is possible to implement what Binc IMAP calls an "IMAPdir" style layout. IMAPdir lets me layout mailboxes in the filesystem like so: $HOME/ Maildir/ <---- users mail goes here Mail/ <---- IMAP root INBOX -> ../Maildir/ <---- (symlink) folder/ <---- some other mailbox in Maildir format folder.subfolder/ <---- '.' is the hierarchy separator folder.subfolder-2/ other-folder/ So IMAP clients subscribe to 'INBOX' and 'folder' and 'folder/subfolder' respectively. This gives me two features that I want: 1) The ability to easily access all my mail using a command line Maildir capable client such as nail, for when I'm connection over a super-slow SSH over GPRS connection. Also, I can actually see my folders (and their subfolders) without having to look for Maildir++ style names with 'ls -a' (e.g. Maildir/.subfolder/). 2) Mail folders are organized logically, unlike the standard Maildir++ layout where everything is a subfolder of 'INBOX', which strikes me as stupid. Is such a thing possible with Dovecot? Any help would be much appreciated. Thanks, -mato

6 22

[Dovecot] Plugin development
by Sebastjan Trepca 15 Aug '05

15 Aug '05

Hi, I have a few questions regarding copy and save_finish methods. How can I get a filename or processing mail from the parameters you get in that methods? How could I use the logger you use for dovecot inside my plugin? Thanks, Sebastjan

2 3

[Dovecot] migration from bincimap to dovecot (imaps)
by Andrea Riela 15 Aug '05

15 Aug '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, I've installed dovecot 0.99.14 (last port on my freebsd system), and now I've to migrate from bincimap. My system uses qmail with vpopmail (uid/gid 89) and Maildir format. Well, now the authentication is ok, but when I try to connect to mailbox I receive an error like "IMAP command SELECT failed". My dovecot.conf: protocols = imaps imaps_listen = 192.168.17.10:993 ssl_disable = no ssl_cert_file = /var/qmail/certs/mail.nesys.it_cert.pem ssl_key_file = /var/qmail/certs/mail.nesys.it_key.pem log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log login_user = dovecot first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89 last_valid_gid = 89 ... default_mail_env = maildir:/usr/local/vpopmail/domains/%d/%u/Maildir ... auth_userdb = vpopmail auth_passdb = vpopmail auth_user = root My Maildir directory: elessar# ls -la total 520 drwx------ 5 vpopmail vchkpw 512 Jul 11 12:40 . drwx------ 3 vpopmail vchkpw 512 Feb 7 12:10 .. - -rw------- 1 vpopmail vchkpw 23 Jul 11 10:43 .bincimap-subscribed - -rw------- 1 vpopmail vchkpw 307344 Jul 11 12:40 bincimap-cache - -rw------- 1 vpopmail vchkpw 75 Jul 11 12:39 bincimap-uidvalidity drwx------ 2 vpopmail vchkpw 190464 Jul 11 12:40 cur drwx------ 2 vpopmail vchkpw 512 Jul 11 12:39 new drwx------ 2 vpopmail vchkpw 512 Jul 11 12:18 tmp - -rw------- 1 vpopmail vchkpw 75 Jun 23 15:09 uidvalfilename I've forgotten something? Any advice will be appreciated :) Regards Andrea -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (Darwin) iD8DBQFC0k92MakHrsrHP9wRAgIrAJ9rkNALg2l/ZoJ5+YyChw5SLhXDtACgyA4T VHnceVpLb1VO9Nm5GeyLIN8= =SEHK -----END PGP SIGNATURE-----

2 5

[Dovecot] corrupted binary tree and index data files
by Gary Sandine 09 Aug '05

09 Aug '05

Hi. I am using dovecot 0.99.14 as an imaps server with mbox folders (in an NFS-mounted directory) in x86 Debian testing. I have searched the archives of this list and have seen other evidence of the problems I am having. I get lots of log messages like these: Jul 29 07:47:09 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/.imap/INBOX/.imap.index.tree: UID to be inserted isn't higher than existing (290 <= 291) ... Jul 29 07:47:13 HOST imap(USER): Corrupted index data file /home/USER/IMAP_MBOX_DIR/.imap/INBOX/.imap.index.data: Field 1 size points outside file (14648 / 14656) for record 290 This is from the midst of a herd of messages starting at 82 <= 144: Jul 28 08:01:31 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (82 <= 144) ... Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (143 <= 144) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (144 <= 144) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (92 <= 154) Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (93 <= 154) ... Jul 28 08:01:32 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (101 <= 154) Jul 28 08:01:34 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/SUBFOLDER_DIR/.imap/MBOX2/.imap.index.tree: UID to be inserted isn't higher than existing (79 <= 80) Jul 28 08:01:34 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/SUBFOLDER_DIR/.imap/MBOX2/.imap.index.tree: UID to be inserted isn't higher than existing (80 <= 80) Jul 28 08:11:27 HOST imap(USER): Corrupted binary tree file /home/USER/IMAP_MBOX_DIR/FOLDER_DIR/.imap/MBOX1/.imap.index.tree: UID to be inserted isn't higher than existing (102 <= 164) ... I don't know how to reproduce this. It happens (repeatedly) for some users and seems to be independent of the number of mboxes, mbox sizes, mail client, .... I have tried deleting .imap directories, and this helps for a while, but the problem always comes back for a few users. The proposed solution for "Corrupted binary tree" or "Corrupted index data file" log messages is usually to change to a different version of dovecot. I will try that, but want to check in here first in case something obvious is happening that I don't understand. Thanks, -- Gary Sandine <gars(a)lanl.gov>

2 2