- dovecot - dovecot.org

[Dovecot] Dovecot-1.1.2 segfaults in mail_cache_header_fields_get_offset
by Mike Abbott 03 Sep '08

03 Sep '08

Dovecot 1.1.2 crashes reliably for me now on a Mac OS X machine. Here's some info: --- Telnet session --- $ telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user1 password a OK Logged in. b select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1218731580] UIDs valid * OK [UIDNEXT 2] Predicted next UID b OK [READ-WRITE] Select completed. c fetch 1 rfc822.size Connection closed by foreign host. --- Error log --- dovecot: Aug 29 11:24:30 Info: imap-login: Login: user=<user1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Aug 29 11:24:33 Error: IMAP(user1): Corrupted transaction log file /Volumes/Spool/spool/user1/mail/dovecot.index.log: hdr.size too large (75497472) dovecot: Aug 29 11:24:33 Warning: IMAP(user1): fscking index file / Volumes/Spool/spool/user1/mail/dovecot.index dovecot: Aug 29 11:24:48 Error: child 66917 (imap) killed with signal 11 --- Backtrace --- mail_cache_header_fields_get_offset + 214 mail_cache_header_fields_read + 37 mail_cache_open_and_verify + 167 mail_cache_field_exists + 77 index_mail_set_seq + 306 index_storage_search_next_nonblock + 464 mailbox_search_next + 52 imap_fetch + 345 cmd_fetch + 639 client_command_input + 33 client_command_input + 463 client_handle_input + 242 client_input + 151 io_loop_handler_run + 272 io_loop_run + 39 main + 1671 start + 52 If I do the exact same telnet all over again, the imap process crashes in the same place, but without reporting the "fscking index file" error first. Attached are all the post-fsck dovecot* files from the user's inbox maildir. For other users I see this error before imap crashes: dovecot: Aug 29 11:45:23 Error: IMAP(user2): Rebuilding index file / Volumes/Spool/spool/user2/mail/dovecot.index: CPU architecture changed Attached are pre- and post-rebuild copies of that user's dovecot* files, and also a copy from after a second telnet session which also crashed. It's possible this is a 32/64-bit incompatibility issue (imap is a 64- bit program for me; mail might have been delivered by a 32-bit deliver or previously read by a 32-bit imap) but more likely the dovecot* files are just hosed in some way. I can provide more information if you ask soon, but I can't keep this server broken for too long.

2 3

[Dovecot] Authentication problems
by Rodti MacLeary 02 Sep '08

02 Sep '08

Hi there, I'm in a bit of a dilemma and wonder if anyone can help. Over the weekend I bought a new dedicated server and moved my mail/web over to it. I'd used the Sarge[1] tutorial at workaround.org for the old server and as I'd wanted to move to Dovecot for a while I decided to use their Etch[2] tutorial for the new one. For the most part everything's working nicely, but I seem to be having problems with (mostly non-SSL) SMTP authentication. In this install Postfix passes SASL authentication to Dovecot. For most clients using SSL this works fine, but as soon as SSL is off it fails. This is despite having disable_plaintext_auth set to 'no'. Furthermore it appears that some clients w/SSL are also failing. Outlook being the major culprit. I'm completely stumped. I've pasted a copy of the output from dovecot -n below. Thanks in advance! Rodti [1] http://workaround.org/articles/ispmail-sarge [2] http://workaround.org/articles/ispmail-etch --------------------------------------------- # 1.0.13: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: mechanisms: plain login cram-md5 passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail

3 5

[Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
by Andreas M. Kirchwitz 02 Sep '08

02 Sep '08

Hi folks, after about 3 weeks without any problems, I've found this crash in yesterday's logfile (again related to index_mailbox_set_recent_seq): Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] -> imap(mbox_sync+0x105d) [0x80823fd] -> imap [0x807a454] -> imap(index_transaction_commit+0x4e) [0x809ddfe] -> imap(cmd_copy+0x35f) [0x805b26f] -> imap(cmd_uid+0x59) [0x805f3d9] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] I don't know what IMAP operation caused that crash. The client (Thunderbird 2.0.0.16) silently reconnected without any notification. No obvious problems since yesterday. Dovecot 1.1.2 is running on Fedora 8 Linux 32 Bit with all patches and custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.2: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd userdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd Greetings, Andreas

3 6

[Dovecot] tcp-wrapper patch for managesieve
by Edgar Fuß 02 Sep '08

02 Sep '08

Is there a place to store unofficial patches to ManageSieve? The attached patch is supposed to make ManageSieve (more precisely, managesieve-login) co-operate with a libwrapped (http://www.dovecot.org/patches/1.1/tcp-wrappers.patch) dovecot.

1 0

[Dovecot] "pam_start() failed: system error" with dovecot 1.1.2, cause unknown
by Adam McDougall 02 Sep '08

02 Sep '08

I would guess this is unlikely to be dovecot's fault, but I'm wondering if anyone has any ideas of what might have happened based on the evidence. My best guess is some kind of resource limit was reached but I don't see any evidence in the logs, and the condition is now gone. Suddenly this morning, one (and only one) of my dovecot servers decided to start failing all logins since 08:25:04 until we restarted dovecot, at which point they were working fine. The number of imap-login processes was under the limit, but there were some obvious PAM errors at the time. My account could still ssh to the system so I don't think it was a problem general authentication, and NIS on other systems was working fine. No one was logged into that server at the time the problems occurred, and I don't think anything happened to the actual pam libraries to make them missing since dovecot worked after a restart. I should have used other means to prevent people from using that dovecot instance rather than stopping it, and I'll do so if it happens again in hopes of further debugging. /var/log/maillog: Sep 2 08:25:01 hill dovecot: imap-login: Login: user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:01 hill dovecot: IMAP(userA): Disconnected: Logged out bytes=127/568 Sep 2 08:25:01 hill dovecot: imap-login: Login: user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:01 hill dovecot: IMAP(userA): Disconnected: Logged out bytes=282/9641 Sep 2 08:25:04 hill dovecot: imap-login: Login: user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:04 hill dovecot: IMAP(userA): Disconnected: Logged out bytes=46/543 ***problem started here Sep 2 08:25:04 hill dovecot: auth-worker(default): pam(userA,127.0.0.1): pam_start() failed: system error Sep 2 08:25:04 hill dovecot: auth-worker(default): pam(userB,35.9.37.164): pam_start() failed: system error Sep 2 08:25:05 hill dovecot: auth-worker(default): pam(userC,35.9.37.164): pam_start() failed: system error Sep 2 08:25:06 hill dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<userB>, method=PLAIN, rip=35.9.37.164, lip=35.9.37.190, TLS Sep 2 08:25:06 hill dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:07 hill dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<userC>, method=PLAIN, rip=35.9.37.164, lip=35.9.37.190, TLS ..... /var/log/messages: Sep 2 08:25:04 hill dovecot-auth: in openpam_load_module(): no pam_permit.so found Sep 2 08:25:04 hill dovecot-auth: in openpam_load_module(): no pam_login_access.so found Sep 2 08:25:05 hill dovecot-auth: in openpam_load_module(): no pam_nologin.so found Sep 2 08:25:10 hill dovecot-auth: in openpam_load_module(): no pam_unix.so found Sep 2 08:25:11 hill dovecot-auth: in openpam_load_module(): no pam_unix.so found Sep 2 08:25:20 hill dovecot-auth: in openpam_load_module(): no pam_opieaccess.so found Sep 2 08:25:20 hill dovecot-auth: in openpam_load_module(): no pam_opie.so found Sep 2 08:25:51 hill kernel: Sep 2 08:25:51 hill last message repeated 12 times Sep 2 08:27:52 hill kernel: Sep 2 08:27:52 hill last message repeated 37 times Sep 2 08:38:01 hill kernel: Sep 2 08:38:01 hill last message repeated 144 times Sep 2 08:48:06 hill kernel: Sep 2 08:48:06 hill last message repeated 129 times Sep 2 08:53:36 hill kernel: Sep 2 08:52:51 hill last message repeated 51 times

2 1

[Dovecot] Bad file descriptor with maildir and bzip2 files
by Chris Burton 02 Sep '08

02 Sep '08

Hi, I'm using the zlib plugin with dovecot 1.1.2 (on Centos 4.5, x86, ext3) and some bzip2 (version 1.0.2) compressed mail files are causing the following error to show in the logs when I click on the folder in outlook express. Aug 27 11:39:15 server-2 dovecot: IMAP(marchive): fstat(maildir) failed: Bad file descriptor Aug 27 11:39:17 Info: IMAP(marchive): Loading modules from directory: /usr/local/lib/dovecot/imap/ Aug 27 11:39:17 Info: IMAP(marchive): Module loaded: /usr/local/lib/dovecot/imap//lib20_zlib_plugin.so Aug 27 11:39:17 Info: IMAP(marchive): Effective uid=606, gid=609, home=/home/marchive Aug 27 11:39:17 Info: IMAP(marchive): maildir: data=/var/spool/maildir/marchive Aug 27 11:39:17 Info: IMAP(marchive): maildir++: root=/var/spool/maildir/marchive, index=, control=, inbox=/var/spool/maildir/marchive Aug 27 11:39:18 Info: IMAP(marchive): Disconnected: Internal error occurred. Refer to server log for more information. [20 08-08-27 11:39:18] bytes=246/1040 I attached strace to it and got the following: 11:39:18.193667 open("/var/spool/maildir/marchive/.2003.INBOX.Charlie.Old.OldInbox.2004/cur/1169027932.P30745Q17M499928.server-2:2,S=103418,Z", O_RDONLY|O_LARGEFILE) = 11 11:39:18.194130 fstat64(11, {st_mode=S_IFREG|0644, st_size=47637, ...}) = 0 11:39:18.194494 pread64(11, "BZh91AY&SY\231\206Z\257\0S\360\377\200\177\3746,U\357\377\377\377\377\377\360\277"..., 4096, 0) = 4096 11:39:18.200204 dup(11) = 12 11:39:18.200557 close(11) = 0 11:39:18.200916 fcntl64(12, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE) 11:39:18.200971 fstat64(12, {st_mode=S_IFREG|0644, st_size=47637, ...}) = 0 11:39:18.201104 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7ff2000 11:39:18.201216 _llseek(12, 0, [0], SEEK_CUR) = 0 11:39:18.201355 fstat64(12, {st_mode=S_IFREG|0644, st_size=47637, ...}) = 0 11:39:18.201478 brk(0x9e61000) = 0x9e61000 11:39:18.201612 read(12, "BZh91AY&SY\231\206Z\257\0S\360\377\200\177\3746,U\357\377\377\377\377\377\360\277"..., 4096) = 4096 11:39:18.201694 read(12, "\277\217\261\0g!\273\')/3\343V\336\276}\273/\210I\26^\255\304\323\r\275Wts\3773"..., 4096) = 4096 11:39:18.201793 mmap2(NULL, 3600384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7c68000 11:39:18.205993 read(12, "~\214\261E*@[\200\245\302\232\201\334\331\272\225NQ\244\260\371\3473cc\312\255\326\246\17\'\222"..., 4096) = 4096 < continues reading from the file > 11:39:18.225970 read(12, "+:E\225\7\217W\264\367\27\226\262i9\34\227=\350\250BcmF\306\'\231m\265\233\337\343\237"..., 4096) = 2581 11:39:18.226040 read(12, "", 4096) = 0 < 26x more of this read > 11:39:18.233913 munmap(0xb7c68000, 3600384) = 0 11:39:18.234070 close(12) = 0 11:39:18.234120 munmap(0xb7ff2000, 4096) = 0 11:39:18.234184 fcntl64(12, F_GETFL) = -1 EBADF (Bad file descriptor) 11:39:18.234255 fstat64(12, 0xbff0a9a0) = -1 EBADF (Bad file descriptor) 11:39:18.234347 write(2, "\1Efstat(maildir) failed: Bad fil"..., 45) = 45 To me it looks like its trying to call fcntl on the handle its just closed? I've since decompressed these files and recompressed with "gzip -9" and they seem to be opening OK. dovecot -n gives: # 1.1.2: /usr/local/etc/dovecot.conf info_log_path: /var/log/dovecot.log protocols: imap imaps pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login mail_location: maildir:/var/spool/maildir/%u mail_debug: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins: zlib mail_plugin_dir(default): /usr/local/lib/dovecot/imap/ mail_plugin_dir(imap): /usr/local/lib/dovecot/imap/ mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3/ imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls auth default: passdb: driver: pam userdb: driver: passwd ChrisB.

3 6

[Dovecot] sieve plugin
by Андрей 02 Sep '08

02 Sep '08

I try to cinfigure dovecot run sieve scripts on incoming mail. In my dovecot.conf: <...> protocol lda { # Address to use when sending rejection mails. postmaster_address = root(a)vpcit.ru # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. hostname = vpcit.ru # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = mail_plugin_dir = /usr/lib/dovecot/modules/lda # Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail # UNIX socket path to master authentication server to find users. auth_socket_path = /var/run/dovecot/auth-master # Enabling Sieve plugin for server-side mail filtering mail_plugins = cmusieve } <...> plugin { sieve = /var/mail/%d/%1n/%n/.dovecot.sieve } Then i set experiments on my maildir. In /var/mail/vpcit.ru/d/dukenukem i created script .dovecot.sieve: require "fileinto"; if header :comparator "i;ascii-casemap" :contains "Subject" "sieve check" { fileinto "Trash"; stop; } Permissions on /var/mail/vpcit.ru/d/dukenukem are: drwx------ 5000 mail So script should put every message that has "sieve check" subject into Trash folder. 1) Trash folder isn't created, should i create it manually? 2) Even when i create Trash folder and make 777 permissions to maildir, nothing happens (message is dropped into inbox dir) 3) Should i configure my Kontact (KMail) e-mail client some way? 4) What i've done incorrect? The mail system works fine at the moment for receive and send, trouble only with sieve scripting. Yours faithfully, Andrey.

3 4

[Dovecot] question about OpenSSL with DC
by Stewart Dean 02 Sep '08

02 Sep '08

IBM recently changed both its delivery package for OpenSSL and the locations it put things. Luckily, I have a second machine other than my mail server that I can test things on and DC 1.0.15 seems to be be running OK (thus I got all the configure/compilation tweaks right), but.....is there anyway to check the DC binaries to determine where it's getting its OpenSSl binaries and libraries (needed at runtime)? -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

3 2

[Dovecot] Virtual users, postfix and dovecot deliver LDA
by Petri Asikainen 02 Sep '08

02 Sep '08

Hi, I have question about how to setup ldap-lookups in dovecot. I have done my homework by googling and reading documention and sample configuration files. But cant resolve this issue. Background: I have setup postfix and dovecot. Postix is configured to ldap alias maps and is delivering mails to /var/spool/vmail/username/Maildir correctly . Username is ldap attribute sAMAccountName from active directory. Goal: To use dovecots sieve plugin I have to setup postfix to use dovecots deliver. Changed postfix main.cf to virtual_transport = dovecot and master.cf to include lines: dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/lda/deliver -d ${recipient} Problem is that mail get delivered to /var/spool/vmail/users.email@address , not folder named as ldap attribute sAMAccountNameas it should. The question is: How I can configure deliver to do map email address to ldap attribute sAMAccountName? Second question is can I use ldap groups as distribution lists whit deliver? Dovecot version is 1.1.2 and postfix 2.5.1 Cheers, Petri

2 11

[Dovecot] Read-only FS
by Radomir Zoltowski 01 Sep '08

01 Sep '08

Hi all, Imagine an NFS mounted read-only file system containing directories full of plain mboxes. Any recommendations on how to approach the access with dovecot? I believe all NFS recommended options apply, how about index/cache files though? Can I switch them off deliberately for good? Performance degradation is not an issue. Thanks, R. -- _________________________________________________________ Radomir Zoltowski <Radomir.Zoltowski(a)s3group.com> Applications Engineer Silicon & Software Systems Ltd., IT Department South County Business Park, Leopardstown, Dublin 18, IRELAND Tel.: +353 1 291 1224, Fax: +353 1 291 1001 _________________________________________________________ The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s). Please direct any additional queries to: communications(a)s3group.com. Thank You. Silicon and Software Systems Limited. Registered in Ireland no. 378073. Registered Office: South County Business Park, Leopardstown, Dublin 18

2 2