November 2006 - dovecot

[Dovecot] 1.0.rc13 released
by Timo Sirainen 15 Nov '06

15 Nov '06

http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz.sig I'll just keep on making new releases now whenever something important is fixed. Hopefully there shouldn't be many left anymore. Most of the bugs fixed in this release were found by stress testing with my imaptest tool (http://dovecot.org/tools/imaptest.c) If you're interested in knowing how perfectly your Dovecot setup works (especially if you're using NFS), you could try the tool yourself also. I still see one crash with mmap_disable=yes, but it's pretty rare. Will see if I get it fixed before v1.0, but it's not that important. + deliver: If we're executing as a normal system user, get the HOME environment from passwd if it's not set. This makes it possible to run deliver from .forward. - Older compilers caused LDAP authentication to crash - Dying LDAP connections weren't handled exactly correctly in rc11, although it seemed to work usually - Fixed crashes and memory leaks with AUTHENTICATE command - Fixed crashes and leaks with IMAP/POP3 proxying - maildir: Changing a mailbox while another process was saving a message there at the same may have caused the changes to not be made into the maildir, which could have caused other problems later..

4 9

[Dovecot] Dovecot/Postfix SASL problem
by Tomislav Filipčić 15 Nov '06

15 Nov '06

Hi. I'm trying to get Dovecot - Postfix - SASL to work. But I need some help. Dovecot v1.0.rc14 Postfix 2.3.4 dovecot.conf ---------------- auth default { mechanisms = plain login passdb pam { } passdb passwd { } socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } postfix/main.cf ------------------ smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination broken_sasl_auth_clients = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_authenticated_header = yes telnet test session ----------------------- orion:~ tomislav$ telnet ra.mahune.org 25 Trying 63.99.9.80... Connected to ra.mahune.org. Escape character is '^]'. 220 ra.mahune.org ESMTP Postfix EHLO ra.mahune.org 250-ra.mahune.org 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-AUTH PLAIN LOGIN 250-AUTH=PLAIN LOGIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH PLAIN bmFddAc0b2pvAHRvam8= 535 5.7.0 Error: authentication failed: mail logs: ------------- Nov 14 22:21:38 [postfix/smtpd] connect from 83-131-68-11.adsl.net.t-com.hr[83.131.68.11] Nov 14 22:22:24 [dovecot] auth(default): client in: AUTH_1_PLAIN_service=smtp_resp=bmFddAc0b2pvAHRvam8= Nov 14 22:22:24 [dovecot] auth(default): passdb(najt,master): Attempted master login with no master passdbs Nov 14 22:22:25 [dovecot] auth(default): client out: FAIL_1_user=tojo Nov 14 22:22:25 [postfix/smtpd] warning: 83-131-68-11.adsl.net.t-com.hr[83.131.68.11]: SASL PLAIN authentication failed: Any ideas? Thank you

3 2

[Dovecot] 45second delays on log in
by Ben Marsh 14 Nov '06

14 Nov '06

Dear List Members, We have been running Dovecot as an IMAP server for web based access to email for our customers. At the moment, when the server is under load, some users are finding that it takes 45 seconds to log in. I was wondering if any of you guys would have any tips. I would love any information that would help solve or debug this issue. Background information: The server is Debian with kernel 2.4.31. We are running Dovecot 1.0rc6. I have reviewed the change logs and not found any changes pertinent to our situation from rc6 to rc14 (But maybe I am wrong). We have our own auth mechanism. This auth mechanism is the same used across our other products and we haven't had the same delays with the other products. From the information in the various log files the auth mechanism responds almost instantaneously but it still takes a long time for 1 OK Logged in. message to arrive on the screen when using telnet localhost 143 to login. All the mailboxes are stored over NFS. I have taken the step of moving the INDEXES from NFS to a local hard drive using default_mail_env = maildir:%h/mail:INDEX=/spare/%h in the config file. (/spare is a locally attached hard drive). We are using Maildir for our mailboxes so I am told that locking should not be a problem. A mailbox would never be accessed by two machines simultaneously due to the architecture of the system. In order to gain performance increases we also implemented an IMAP proxy between the webmail client and the imap server. This removes delays in all but the first attempt to access webmail. When logging into a user for which login has been verified to take about 45seconds deletion of the large numbers of messages seemed to speed up login for that particular mailbox indicating to me that it was other things that dovecot does after login and before the 1 OK Logged in. message is displayed that takes up all the time. Unfortunately this theory failed when I tried it with other users. I have also analysed the log files. of the 100,000 lines in the log file 49 were messages: Child 12040 (login) returned error 89 54 were messages: imap-login: Master sent reply with unknown tag 18 The actual number at the end of the message changes lots. The frequency of the extended logins would make it extremely unlikely that these messages are the problem. Any help is very much appreciated. Thanks, Ben Marsh

4 4

[Dovecot] Problem with image attachment
by Marc Morata 14 Nov '06

14 Nov '06

Hi, I have a litle problem: The image attachment has a one line blank in top. This provokes that the image are corrupt. Only happens with imap acces. With pop3 are visualized correctly. Thank you. -- Marc Morata Fité mmorata(a)gnuine.com Gnuine www.gnuine.com

2 2

[Dovecot] Question regarding bounce messages on quota full.
by Mustafa A. Hashmi 14 Nov '06

14 Nov '06

Hi all, Using dovecot's LDA (debian backports package: 1.0rc2), users who have exceeded their quota when receiving messages see the message get bounced. This works fine for us, however, the sender is sent a message as follows: -- Start bounce text ERROR This is the Postfix program at host foo.domain.com I'm sorry to have to inform you that your message could not be be delivered to one or more recipients. It's attached below. For further assistance, please send mail to <postmaster> If you do so, please include this problem report. You can delete your own text from the attached returned message. The Postfix program <user(a)foo.domain.com>: Command died with status 11: "/usr/lib/dovecot/deliver" -- End bounce text Is it not possible to specify something a bit more civil for the sender? a "User is over quota" message works much better here. We're already running a script which notifies users when they approach a certain specified % that they're about to exceed quota, however, hoping they all comply is another thing entirely. Any assistance would be much appreciated. Regards, -- Mustafa A. Hashmi mahashmi(a)gmail.com mh(a)stderr.net

2 3

[Dovecot] NTLM authentication from Outlook
by Lars Skovgaard 13 Nov '06

13 Nov '06

Hi all I've enabled ntlm authentication in dovecot, and use dovecot sasl in postfix as well. Authentication with ntlm works well from Mac OS X Mail.app, as well as from Outlook Express, but fails with Outlook. Strangely enough, ntml authentication works in Outlook when using smtp (via postfix), but neither from imap or pop3 (both dovecot). As dovecot sasl handles all authentication against a mysql userdb, this strikes me as very strange. I've instructed my clients with Outlook to fetch mail using a ssl- encrypted connection, and to send using ntlm-authentication. This works, but I would like to have ntlm available as an option to all my clients, without forcing them to change mail-clients. I've turned on auth_verbose, auth_debug and auth_debug_passwords, and compared the passwordstring with the one calculated using dovecotpw, and they match. The only odd thing is that the username is returned from Outlook as an all-caps string, so user(a)domain.tld becomes USER(a)DOMAIN.TLD. I don't know if it matters, but I don't think so, as changing the user-login to an all-caps version doesn't solve the problem. Any hints will be most welcome. /Lars

1 0

[Dovecot] MacOS X and quota-plugin
by Lars Skovgaard 13 Nov '06

13 Nov '06

Hi all, I've installed dovecot 1.0 rc12 on a MacOS X client system with only a handful of users – all virtual – and would like to enable quotas. I've tried searching the wiki for information on how to do this, but haven't been able to find anything – which is why I turn to the list in hope there's someone out there who can point me in the right direction. I've compiled dovecot without any other authentication than sql and pam, and have enabled ssl, pop3 and dovecot lda (for use with postfix when I get around to it). The installation went smoothly, and dovecot is working great without quota-support. However, when I enable quota- support, the imap child-process crashes. Here's a few lines from the log, slightly altered to protect user-identities: Nov 8 23:05:09 SD-Server dovecot: imap-login: Login: user=<imapuser>, method=PLAIN, rip=192.168.2.10, lip=192.168.2.2, TLS Nov 8 23:05:09 SD-Server dovecot: child 22662 (imap) killed with signal 11 Nov 8 23:05:09 SD-Server crashdump[22663]: imap crashed Nov 8 23:05:09 SD-Server crashdump[22663]: crash report written to: / Library/Logs/CrashReporter/imap.crash.log Nov 8 23:05:12 SD-Server dovecot: imap-login: Login: user=< imapuser >, method=PLAIN, rip=192.168.2.10, lip=192.168.2.2, TLS Nov 8 23:05:13 SD-Server dovecot: child 22665 (imap) killed with signal 11 Nov 8 23:05:13 SD-Server crashdump[22666]: imap crashed Nov 8 23:05:13 SD-Server crashdump[22666]: crash report written to: / Library/Logs/CrashReporter/imap.crash.log Nov 8 23:05:16 SD-Server dovecot: imap-login: Login: user=< imapuser >, method=PLAIN, rip=192.168.2.10, lip=192.168.2.2, TLS Nov 8 23:05:17 SD-Server dovecot: child 22670 (imap) killed with signal 11 Nov 8 23:05:17 SD-Server crashdump[22671]: imap crashed Nov 8 23:05:17 SD-Server crashdump[22671]: crash report written to: / Library/Logs/CrashReporter/imap.crash.log This is what I have done in dovecot.conf to enable quota: protocol imap { mail_plugins = quota imap_quota mail_plugin_dir = /usr/local/lib/dovecot/imap } plugin { #quota = dict:storage=10240 #quota = dirsize:storage=10240 #quota = maildir:storage=10240 #quota = maildir:storage=10240 mysql:/usr/local/etc/dovecot-sql.conf #quota = fs:storage=10240 #quota = fs } As you might guess from the lines under "plugin", I've tried a lot of different combinations. If I enable ANY of the above lines under plugin, the child-processes die upon login. When all have been commented out, there's no more crashing – until I try to see how much space is available, then it crashes again. I've tried adding an extra "quota" field to my mysql userdb to handle quotas, but with the same result. mysql-query looks like this (as described in the wiki): user_query = SELECT home, uid, gid, 'dirsize:storage=' || quota_kb AS quota FROM users WHERE userid = '%u' As with the settings in dovecot.conf, Ive tried various combinations of dict, dirsize and so on, but without any luck. This is what the entries in my crashdump file looks like: Host Name: SD-Server Date/Time: 2006-11-09 00:06:17.151 +0100 OS Version: 10.4.7 (Build 8J135) Report Version: 4 Command: imap Path: /usr/local/libexec/dovecot/imap Parent: dovecot [8370] Version: ??? (???) PID: 23101 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000044 Thread 0 Crashed: 0 lib01_quota_plugin.so 0x00256ca8 quota_root_iter_next + 32 (array.h:144) 1 lib02_imap_quota_plugin.so 0x00273700 cmd_getquotaroot + 280 (imap-quota-plugin.c:87) 2 imap 0x000076b8 _client_input + 556 (client.c:377) 3 imap 0x0006e9a8 io_loop_handler_run + 424 (ioloop-poll.c:200) 4 imap 0x0005e214 io_loop_run + 40 (ioloop.c: 280) 5 imap 0x0000fd38 main + 1740 (main.c:241) 6 imap 0x00001df4 _start + 348 (crt.c:272) 7 imap 0x00001c94 start + 60 Thread 0 crashed with PPC Thread State 64: srr0: 0x0000000000256ca8 srr1: 0x000000000200f030 vrsave: 0x0000000000000000 cr: 0x48000244 xer: 0x0000000000000004 lr: 0x0000000000256c94 ctr: 0x0000000000256c88 r0: 0x0000000000273700 r1: 0x00000000bffff410 r2: 0x0000000000000000 r3: 0x0000000000501e10 r4: 0x0000000000000010 r5: 0x0000000000000010 r6: 0x0000000000000022 r7: 0x0000000000000000 r8: 0x0000000000000002 r9: 0x0000000000501e20 r10: 0x0000000000000000 r11: 0x0000000000275044 r12: 0x0000000000256c88 r13: 0x0000000000000000 r14: 0x0000000000000000 r15: 0x0000000000000000 r16: 0x0000000000000000 r17: 0x0000000000000000 r18: 0x0000000000000000 r19: 0x0000000000000000 r20: 0x0000000000000000 r21: 0x0000000000000000 r22: 0x0000000000000000 r23: 0x0000000000000000 r24: 0x0000000000000000 r25: 0x000000000007e808 r26: 0x0000000000000000 r27: 0x0000000000500a24 r28: 0x0000000000501e10 r29: 0x0000000000500a24 r30: 0x00000000002492d0 r31: 0x0000000000256c94 Binary Images Description: 0x1000 - 0x7efff imap /usr/local/libexec/dovecot/imap 0x253000 - 0x258fff lib01_quota_plugin.so /usr/local/lib/ dovecot/imap/lib01_quota_plugin.so 0x273000 - 0x274fff lib02_imap_quota_plugin.so /usr/local/lib/ dovecot/imap/lib02_imap_quota_plugin.so 0x8fe00000 - 0x8fe52fff dyld 45.3 /usr/lib/dyld 0x90000000 - 0x901bbfff libSystem.B.dylib /usr/lib/libSystem.B.dylib 0x90213000 - 0x90218fff libmathCommon.A.dylib /usr/lib/system/ libmathCommon.A.dylib 0x92d65000 - 0x92e53fff libiconv.2.dylib /usr/lib/libiconv.2.dylib 0x936e3000 - 0x93703fff libmx.A.dylib /usr/lib/libmx.A.dylib Best regards, Lars

2 2

[Dovecot] my_strncasecmp ignores max_chars
by Ben Winslow 13 Nov '06

13 Nov '06

my_strncasecmp ignores the length parameter, which breaks all sorts of things on platforms where the function actually gets used. Trivial patch attached. -- Ben Winslow <rain(a)bluecherry.net>

2 2

Re: [Dovecot] assertion failed: (need_space == (uoff_t)-mails[idx].space)
by David King 13 Nov '06

13 Nov '06

>> Ah, makes sense, I feel dumb now :) >> Here's a backtrace from imap.core, I can do more with the core if it >> helps >> #0 0x182bc437 in kill () from /lib/libc.so.6 >> #1 0x182bc3d6 in raise () from /lib/libc.so.6 >> #2 0x182baf02 in abort () from /lib/libc.so.6 > .. > Not having debugging information stripped would be helpful :) Well now I feel dumber :) FreeBSD uses the install-strip target in the Makefile to install the binaries, so even if I have -g in COPTS the binaries get stripped. I overwrote the binaries with those from src/ and reproduced the crash (which is as easy and opening the folder in an IMAP client), here's the new backtrace (gdb) bt #0 0x182bc437 in kill () from /lib/libc.so.6 #1 0x182bc3d6 in raise () from /lib/libc.so.6 #2 0x182baf02 in abort () from /lib/libc.so.6 #3 0x080b7355 in i_internal_panic_handler (fmt=0x0, args=0x0) at failures.c:382 #4 0x080b6dc9 in i_panic (format=0x0) at failures.c:180 #5 0x0807c19d in mbox_sync_read_and_move (sync_ctx=0xbfbfe8b0, mail_ctx=0xbfbfe580, mails=0x80fb000, seq=405589544, idx=0, padding=3217024224, move_diff=37, expunged_space=0, end_offset=3333, first_nonexpunged=true) at mbox-sync-rewrite.c:405 #6 0x0807c70e in mbox_sync_rewrite (sync_ctx=0xbfbfe8b0, mail_ctx=0x0, end_offset=3333, move_diff=37, extra_space=63, first_seq=1, last_seq=0) at mbox-sync-rewrite.c:507 #7 0x08076df9 in mbox_sync_handle_missing_space (mail_ctx=0xbfbfe7b0) at mbox-sync.c:854 #8 0x0807756b in mbox_sync_loop (sync_ctx=0xbfbfe8b0, mail_ctx=0xbfbfe7b0, partial=true) at mbox-sync.c:1158 #9 0x08078326 in mbox_sync_do (sync_ctx=0xbfbfe8b0, flags=MBOX_SYNC_REWRITE) at mbox-sync.c:1480 #10 0x08078bea in mbox_sync (mbox=0x80e5840, flags=MBOX_SYNC_REWRITE) at mbox-sync.c:1732 #11 0x08070456 in mbox_storage_close (box=0x80e5840) at mbox- storage.c:1063 #12 0x080a8607 in mailbox_close (_box=0x0) at mail-storage.c:371 #13 0x08058a4d in cmd_logout (cmd=0x80e8044) at cmd-logout.c:18 #14 0x0805b12c in client_handle_input (cmd=0x80e8044) at client.c:377 #15 0x0805b21d in _client_input (context=0x80e8000) at client.c:428 #16 0x080bd39c in io_loop_handler_run (ioloop=0x80e4000) at ioloop- poll.c:199 #17 0x080bccb8 in io_loop_run (ioloop=0x80e4000) at ioloop.c:281 #18 0x08064078 in main (argc=3, argv=0x0, envp=0x0) at main.c:280 >> Sure, you can get it here: > You don't have X-IMAPbase or X-IMAP header in the first mail, so I > guess > you're also reading and modifying the mailbox outside Dovecot? That by > itself shouldn't break it as long as the locking is done correctly. > But > I guess your problem is somehow related to that. I couldn't anyway > cause > a crash using the file. Procmail writes to the folders, but it uses dotlocks, and I don't have logs of it crashing, whereas I do have logs of dovecot crashing :) I'm confused as to what the last sentence says, do you mean that you were able to reproduce the crash?

1 0

[Dovecot] imap - file ioloop.c: line 22 (io_add): assertion failed: (fd >= 0)
by Wolfgang Fischer 12 Nov '06

12 Nov '06

in dovecot 1.0RC13 after "Disconnected in IDLE" I get following Error: Nov 12 19:49:51 mini1 dovecot: IMAP(wolfgang): Disconnected in IDLE Nov 12 19:49:51 mini1 dovecot: IMAP(wolfgang): file ioloop.c: line 22 (io_add): assertion failed: (fd >= 0) Nov 12 19:49:51 mini1 dovecot: child 1301 (imap) killed with signal 6 dovecot is running with Mac OS 10.4.8 (PowerPC), Mailbox Format is mbox. Wolfgang

2 1