July 2008 - dovecot - dovecot.org

[Dovecot] "Errors" in logfile after upgrading to 1.1.1?
by Bjørn T Johansen 20 Jul '08

20 Jul '08

Not sure but I mean I didn't have these in the log file before the upgrade....: auth(default): passwd(user(a)domain.no): unknown user auth(default): prefetch(user(a)domain.no): passdb didn't return userdb entries, trying the next userdb Is there some config that is wrong or? btw, authentiation is working.... Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bjørn T Johansen btj(a)havleik.no ----------------------------------------------------------------------------------------------- Someone wrote: "I understand that if you play a Windows CD backwards you hear strange Satanic messages" To which someone replied: "It's even worse than that; play it forwards and it installs Windows" -----------------------------------------------------------------------------------------------

2 4

[Dovecot] v1.1.rc13 released
by Timo Sirainen 20 Jul '08

20 Jul '08

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc13.tar.gz.sig There's always time for one more release candidate. :) I was planning on releasing v1.1.0 a couple of minutes before summer solstice (23:59 UTC according to Wikipedia). Maybe it'll bring luck to the release. :) - mbox: Fixed a crash when adding a new X-IMAPbase: header with keywords. - Message parser: Fixed assert-crash if cached MIME structure was broken. - Squat: Potential crashfix with mmap_disable=yes.

4 5

Re: [Dovecot] assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq)
by Mark Zealey 20 Jul '08

20 Jul '08

OK I've been struggling to get dumps from the live environment most of the day, but have given up. I've now managed to reproduce this using a fork-bomb type script; here is a backtrace (no debug version installed, but I suspect I could reproduce this in the dev environment if it's not clear what the error is). (gdb) bt #0 0x004ef402 in __kernel_vsyscall () #1 0x00138c00 in raise () from /lib/libc.so.6 #2 0x0013a451 in abort () from /lib/libc.so.6 #3 0x080c413d in default_error_handler () #4 0x080c41cd in i_syslog_fatal_handler () #5 0x080c3a2c in i_panic () #6 0x080a072c in mail_index_transaction_lookup () #7 0x080a39d7 in mail_index_transaction_open_updated_view () #8 0x080b2853 in mail_cache_decision_add () #9 0x0809b884 in mail_cache_add () #10 0x08089910 in index_mail_cache_add_idx () #11 0x08089a03 in index_mail_cache_add () #12 0x08089ec7 in index_mail_close () #13 0x0808ad90 in index_mail_free () #14 0x08092f42 in mail_free () #15 0x0806c63c in maildir_transaction_save_commit_pre () #16 0x08065d62 in maildir_transaction_class_deinit () #17 0x08092cce in index_transaction_commit () #18 0x08094a56 in mailbox_transaction_commit () #19 0x0805a416 in deliver_save () #20 0x0805b99a in main () The way I caused this crash was: [root@mail2 tmp]# cat t.sh #!/bin/bash HOME=/path/to/nfs/Maildir/ export HOME exec /usr/libexec/dovecot/deliver -f foo(a)bar.com Then in bash as root: # i=0; while true; do echo $i; i=$((i+1)); sudo -u exim /tmp/t.sh < /root/t & sudo -u exim /tmp/t.sh < /root/t & sudo -u exim /tmp/t.sh < /root/t & sudo -u exim /tmp/t.sh < /root/t & sudo -u exim /tmp/t.sh < /root/t & sudo -u exim /tmp/t.sh < /root/t & done After about 3 seconds I got 10 crashes and core dumps. A word about our setup; we have the maildirs stored on an nfs mount and deliver could be called on multiple heads at the same time for deliveries - I suspect this is what was causing the problem. Our nfs mount options are rw,noatime,nodiratime,hard,intr,rsize=32768,wsize=32768,tcp,nocto. Running centos 5.1 on the boxes with exim. Thanks, Mark

2 1

[Dovecot] exim, LDA, quota
by Marcin Gryszkalis 20 Jul '08

20 Jul '08

Hi I configured Exim with dovecot LDA and added quota (dict/mysql). It works but it seems that dovecot is not reporting situation back to exim process - it looks like Exim returns OK(accepted) to smtp sender before the message is actually delivered - if the quota is exceeded then LDA drops the mail and sends DSN. Is it possible to change that behavior to report problem immediately (within SMTP session)? regards -- Marcin Gryszkalis, PGP 0x9F183FA3 jabber jid:mg@fork.pl, gg:2532994 http://the.fork.pl

2 2

[Dovecot] group ownership of new shared folders
by Simon Michelson 20 Jul '08

20 Jul '08

Between versions 1.0.4 and 1.0.5 there were some changes to the way dovecot-shared group ownership is propogated into new maildirs. Changing the group of new_dir/{tmp,new,cur} was added, but changing the group of new_dir itself was removed. As far as I can tell, this latter change may have been accidental. This patch puts the functionality back, in the 1.1 tree. ---------------------------------- # HG changeset patch # User Simon Michelson <simon(a)inpher.com> # Date 1214444574 -3600 # Branch HEAD # Node ID 1dae5712e81daacb6923f500c0997aca6853ec3a # Parent 3c06e14c4731ee1ffe6d8c36bbdc711e3190cb2c reinstate code to apply gid of dovecot-shared to new maildir directory diff -r 3c06e14c4731 -r 1dae5712e81d src/lib-storage/index/maildir/maildir-storage.c --- a/src/lib-storage/index/maildir/maildir-storage.c Tue Jun 24 13:37:55 2008 +0300 +++ b/src/lib-storage/index/maildir/maildir-storage.c Thu Jun 26 02:42:54 2008 +0100 @@ -539,6 +539,10 @@ static int maildir_create_shared(struct umask(old_mask); return -1; } + if (chown(dir, (uid_t)-1, gid) < 0) { + mail_storage_set_critical(storage, + "chown(%s) failed: %m", dir); + } for (i = 0; i < N_ELEMENTS(maildir_subdirs); i++) { path = t_strconcat(dir, "/", maildir_subdirs[i], NULL); if (chown(path, (uid_t)-1, gid) < 0) {

2 1

[Dovecot] No log for hitting login_max_processes_count?
by Adam McDougall 20 Jul '08

20 Jul '08

I think today just due to increased use, my mail servers hit login_max_processes_count. It wasn't obvious what was happening, logins just weren't acting like they should and sometimes would get disconnected before given a prompt from the server. Something made me think to check if I had too many of certain dovecot processes and I found I had 128 imap-login processes on both servers, but nothing in the logs seemed to point that out for me. Should there be? It would have been alot easier to debug. Also, this seems to be from general use, doesn't seem like a DoS, so is this just a setting I should keep an eye on and increase it by reasonable amounts as needed? Thanks.

3 2

[Dovecot] 1.1.1, mbox_snarf and duplicate messages
by Laurent.Moineau＠math-info.univ-paris5.fr 20 Jul '08

20 Jul '08

Hello, I recently switched to dovecot 1.1.1 with mbox_snarf from uw-imap with mbox driver enabled. The mail is delivered by procmail in /var/spool/mail/user Most of my users have a file INBOX located in $HOME/mail The mail is transfered from /var/spool/mail/user to $HOME/mail/INBOX every time an imap connection is done. Things are OK with clients like thunderbird or evolution, but with imp or mostly squirrelmail messages are duplicated (some user reported that a single message duplicated 50 times !). Every imap connection (thunderbird or webmail) terminates with a warning : Timeout leak: 0x4534e0 I 've tried to use fcntl in : lock_method, mbox_read_locks and mbox_write_locks but things are worse than traditional dotlocks. My config on my first server : sendmail-8.14.1 procmail dovecot 1.1.1 On the second server : The webmail (imp and squirrelmail, latest versions) is installed on another server but uses server 1 as imap server. I 've tried to use an imap proxy (perdition) but without any improvement as far as this problem is concerned. I previously used another dovecot server on that machine with an NFS mount to get /var/spool/mail from the first server with the duplicate problem too. I enabled mail_log and there where a bunch of Info messages like this : dovecot: Jul 11 18:20:11 Info: IMAP(foo): copy: uid=22, dest=/users/foo/mail/INBOX, msgid=<4877879C.40104(a)math-info.univ-paris5.fr>, size=2223 Any hint ? Is mbox_snarf considered as stable ? dovecot -n : # 1.1.1: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imaps pop3 pop3s listen: * ssl_cert_file: /etc/pki/tls/certs/ipop3d.pem ssl_key_file: /etc/pki/tls/certs/ipop3d.pem 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 mail_privileged_group: mail mail_gid: 12 mail_location: mbox:~/mail:INBOX=/var/spool/mail/%u mbox_lazy_writes: no mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugins(default): mbox_snarf mail_plugins(imap): mbox_snarf mail_plugins(pop3): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 auth default: debug: yes passdb: driver: pam userdb: driver: passwd plugin: mbox_snarf: %h/mail/INBOX /etc/procmailrc : SENDMAIL=/usr/sbin/sendmail MAILDIR=/var/spool/mail SPAM=$HOME/mail/spam DROPPRIVS=yes :0 H *^X-Spam-Status: Yes $SPAM :0 H *^Subject: .**SPAM $SPAM Thanks for your help. Laurent Moineau System Administrator ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

[Dovecot] dovecot-auth assertion failed
by Eric 20 Jul '08

20 Jul '08

Hello, I have been running some tests on a new Dovecot v1.0.13 server and have seen the following message appear in the logs a few times. It appears to occur when there are a lot of requests being sent to the LDAP servers from both Dovecot and Sendmail (I am guessing about this, since I have also seen "Server busy" messages regarding LDAP auth). dovecot: auth(default): file db-ldap.c: line 310 (ldap_conn_retry_requests): assertion failed: (conn->connected) dovecot: auth(default): Raw backtrace: dovecot-auth [0x806daf1] -> dovecot-auth [0x806da0c] -> dovecot-auth [0x8059607] -> dovecot-auth [0x8059b1d] -> dovecot-auth [0x8059b7b] -> dovecot-auth(io_loop_handler_run+0x110) [0x8070c90] -> dovecot-auth(io_loop_run+0x1c) [0x80701cc] -> dovecot-auth(main+0x2fe) [0x805b01e] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x3efdec] -> dovecot-auth [0x8051161] dovecot: child 23178 (auth) killed with signal 6 Dovecot seems to recover from this error and continues to handle auth requests properly. Thanks, Eric

2 1

[Dovecot] Problems with dovecot deliver.
by Dpoke 20 Jul '08

20 Jul '08

Hello all. I am using dovecot 1.1.rc4. Some of my mail deliver without errors. Other mail during its deliver give next errors in logs: Postfix log Jun 16 18:34:17 postfix/local[2730]: A394E292002: to=<dpoke(a)localhost.mail.com>, orig_to=<dpoke@localhost>, relay=local, delay=3013, delays=3008/1.3/0/2.9, dsn=4.3.0, status=deferred (temporary failure) Jun 16 18:34:17 postfix/local[2731]: B5FE7292004: to=<dpoke(a)localhost.mail.com>, orig_to=<dpoke@localhost>, relay=local, delay=2998, delays=2994/0.98/0/2.6, dsn=4.3.0, status=deferred (temporary failure) Jun 16 18:34:18 postfix/local[2731]: 28723292003: to=<dpoke(a)localhost.mail.com>, orig_to=<dpoke@localhost>, relay=local, delay=2993, delays=2989/3.5/0/0.72, dsn=4.3.0, status=deferred (temporary failure) ................................................ Deliver log. (Also I found no other useful information relaying this problem in other dovecot logs.) deliver(dpoke): Jun 16 18:34:15 Info: maildir: data=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:15 Info: maildir++: root=/opt/home/dpoke//Maildir, index=, control=, inbox=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:15 Info: maildir: data=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:15 Info: maildir++: root=/opt/home/dpoke//Maildir, index=, control=, inbox=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:16 Error: open(/tmp/dovecot.deliver..1213626856.2732.ad657cfa5dccbc61) failed: Permission denied deliver(dpoke): Jun 16 18:34:16 Error: copy: i_stream_read() failed: Permission denied deliver(dpoke): Jun 16 18:34:16 Info: msgid=: save failed to INBOX: Internal error occurred. Refer to server log for more information. [2008-06-16 18:34:14] deliver(dpoke): Jun 16 18:34:16 Error: open(/tmp/dovecot.deliver..1213626856.2733.ad657cfa5dccbc61) failed: Permission denied deliver(dpoke): Jun 16 18:34:16 Error: copy: i_stream_read() failed: Permission denied deliver(dpoke): Jun 16 18:34:16 Info: msgid=: save failed to INBOX: Internal error occurred. Refer to server log for more information. [2008-06-16 18:34:14] deliver(dpoke): Jun 16 18:34:17 Info: maildir: data=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:17 Info: maildir++: root=/opt/home/dpoke//Maildir, index=, control=, inbox=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:17 Info: maildir: data=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:17 Info: maildir++: root=/opt/home/dpoke//Maildir, index=, control=, inbox=/opt/home/dpoke//Maildir deliver(dpoke): Jun 16 18:34:17 Error: open(/tmp/dovecot.deliver..1213626857.2737.712b51aaca368d64) failed: Permission denied deliver(dpoke): Jun 16 18:34:17 Error: copy: i_stream_read() failed: Permission denied deliver(dpoke): Jun 16 18:34:17 Info: msgid=: save failed to INBOX: Internal error occurred. Refer to server log for more information. [2008-06-16 18:34:17] deliver(dpoke): Jun 16 18:34:17 Error: open(/tmp/dovecot.deliver..1213626857.2736.712b51aaca368d64) failed: Permission denied deliver(dpoke): Jun 16 18:34:18 Error: copy: i_stream_read() failed: Permission denied deliver(dpoke): Jun 16 18:34:18 Info: msgid=: save failed to INBOX: Internal error occurred. Refer to server log for more information. [2008-06-16 18:34:17] ..................................................... This is my dovecot configuration: # 1.0.3: /opt/etc/dovecot.conf protocols: imap listen: 192.168.1.1 ssl_disable: yes disable_plaintext_auth: no login_dir: /opt/var/run/dovecot/login login_executable: /opt/libexec/dovecot/imap-login login_user: nobody login_processes_count: 1 auth default: verbose: yes debug: yes passdb: driver: passwd-file args: /opt/etc/passwd.imap userdb: driver: passwd-file args: /etc/passwd How can I fix this mail delivering problem? Thanks in advance for any ideas/suggestions/answers. And sorry for my bad English ;) -- Ilya Galanin

3 2

[Dovecot] file ioloop-iolist.c: line 25 (ioloop_iolist_add): assertion failed: (list->ios[idx] == NULL)
by Dirk H 20 Jul '08

20 Jul '08

Hi, I am using dovcot on a Fritz!Box (Linux fritz 2.6.19.2 #1 Fri Apr 18 16:00:34 CEST 2008 mips unknown) And after upgrading from 1.0.9 to 1.0.15 I am getting above assertion, when I do some action like moving or deleting on the IMAP mail box using MailDir on ext2 fs. I use --with-ioloop=epoll and --with-mem-align=4 as build configuration. For dovecof configuration see below details. Thanks for your help, DHU # 1.0.15: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log listen: *:xx143 ssl_listen: *:xx993 ssl_cert_file: /var/MailRoot/server.cert ssl_key_file: /var/MailRoot/server.key ssl_parameters_regenerate: 0 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_process_size: 32 login_processes_count: 2 login_max_connections: 5 mail_location: maildir:/var/MailRoot/domains/%d/%n//Maildir imap_client_workarounds: outlook-idle delay-newmail netscape-eoh tb-extra-mailbox-sep auth default: default_realm: fritz.homeip.net user: xmail username_format: %Lu passdb: driver: passwd-file args: /var/MailRoot/dovecotusers.tab userdb: driver: static args: uid=504 gid=504 home=/var/MailRoot/domains/%d/%n/Maildir

2 1