- dovecot - dovecot.org

[Dovecot] assert with zlib and (maybe) fts
by Matthias Rieber 09 Jan '09

09 Jan '09

Hi, I compressed a folder with the following script: ... for i in *.*.*; do file $i | grep bzip2 >/dev/null 2>&1 if [ $? -ne 0 ]; then echo "Compress: $i" cat "$i" | bzip2 -9 > ../tmp/$i if [ $? -eq 0 ]; then mv ../tmp/$i $i fi else echo "Alread DONE: $i"; fi done ... it works mostly, but there seems to be at leas one messages that cause a problem, during syncing the whole folder or performing a search, I get an assert: @40000000494044a53ae8e4fc dovecot: Info: auth(default): new auth connection: pid=24651 @40000000494044dd09e0bd6c dovecot: Error: IMAP(matthias): read(mail, uid=8235) failed: Invalid argument @40000000494044dd0b155d3c dovecot: Error: IMAP(matthias): *** glibc detected *** imap: free(): invalid next size (normal): 0x099995f8 *** @40000000494044dd0b4f12ac dovecot: Error: IMAP(matthias): ======= Backtrace: ========= @40000000494044dd0b4f1a7c dovecot: Error: IMAP(matthias): /lib/libc.so.6[0xb7eea815] @40000000494044dd0b4f1e64 dovecot: Error: IMAP(matthias): /lib/libc.so.6(cfree+0x9c)[0xb7eec6bc] @40000000494044dd0b4f2634 dovecot: Error: IMAP(matthias): /usr/local/lib/dovecot/imap/lib20_zlib_plugin.so[0xb7fc3e04] @40000000494044dd0b4f2a1c dovecot: Error: IMAP(matthias): imap(io_stream_unref+0x40)[0x80eb290] @40000000494044dd0b4f2e04 dovecot: Error: IMAP(matthias): imap(i_stream_unref+0x1c)[0x80dc2cc] @40000000494044dd0b4f83f4 dovecot: Error: IMAP(matthias): imap(index_mail_close+0x6b)[0x809ad6b] @40000000494044dd0b4f87dc dovecot: Error: IMAP(matthias): imap[0x8098dc8] @40000000494044dd0b4f8bc4 dovecot: Error: IMAP(matthias): imap(index_mail_set_seq+0x40)[0x80991f0] @40000000494044dd0b4f8fac dovecot: Error: IMAP(matthias): imap(index_storage_search_next_nonblock+0xef)[0x809d2ef] @40000000494044dd0b4f9394 dovecot: Error: IMAP(matthias): /usr/local/lib/dovecot/imap/lib20_fts_plugin.so[0xb7e7cd6e] @40000000494044dd0b4fa71c dovecot: Error: IMAP(matthias): imap[0x8060a36] @40000000494044dd0b4fab04 dovecot: Error: IMAP(matthias): imap[0x8060e86] @40000000494044dd0b4faeec dovecot: Error: IMAP(matthias): imap(io_loop_handle_timeouts+0xe9)[0x80de919] @40000000494044dd0b4fb2d4 dovecot: Error: IMAP(matthias): imap(io_loop_handler_run+0x82)[0x80df1d2] @40000000494044dd0b4fd5fc dovecot: Error: IMAP(matthias): imap(io_loop_run+0x20)[0x80de6c0] @40000000494044dd0b4fd9e4 dovecot: Error: IMAP(matthias): imap(main+0x46a)[0x806b67a] @40000000494044dd0b4fddcc dovecot: Error: IMAP(matthias): /lib/libc.so.6(__libc_start_main+0xe5)[0xb7e96455] @40000000494044dd0b4fe59c dovecot: Error: IMAP(matthias): imap[0x805cac1] @40000000494044dd0b4fe984 dovecot: Error: IMAP(matthias): ======= Memory map: ======== @40000000494044dd0b50917c dovecot: Error: IMAP(matthias): 08048000-08101000 r-xp 00000000 fd:0b 1541448 /usr/local/libexec/dovecot/imap @40000000494044dd0b50994c dovecot: Error: IMAP(matthias): 08101000-08107000 rwxp 000b9000 fd:0b 1541448 /usr/local/libexec/dovecot/imap @40000000494044dd0b509d34 dovecot: Error: IMAP(matthias): 08107000-09ae3000 rwxp 08107000 00:00 0 [heap] @40000000494044dd0b50a11c dovecot: Error: IMAP(matthias): b7163000-b7928000 rwxs 00000000 fd:0b 508303 /home/matthias/Maildir/REMOVED/dovecot.index.search.uids @40000000494044dd0b50c05c dovecot: Error: IMAP(matthias): b7928000-b79ea000 rwxp b7928000 00:00 0 @40000000494044dd0b50c444 dovecot: Error: IMAP(matthias): b7a22000-b7a63000 rwxp b7a22000 00:00 0 @40000000494044dd0b50c82c dovecot: Error: IMAP(matthias): b7a63000-b7a81000 r-xs 00000000 fd:0b 508302 /home/matthias/Maildir/REMOVED/dovecot.index.cache @40000000494044dd0b50f324 dovecot: Error: IMAP(matthias): b7c00000-b7c21000 rwxp b7c00000 00:00 0 @40000000494044dd0b50f70c dovecot: Error: IMAP(matthias): b7c21000-b7d00000 ---p b7c21000 00:00 0 @40000000494044dd0b50faf4 dovecot: Error: IMAP(matthias): b7dde000-b7dea000 r-xp 00000000 fd:0b 1655254 /lib/libgcc_s.so.1 @40000000494044dd0b511264 dovecot: Error: IMAP(matthias): b7dea000-b7deb000 rwxp 0000b000 fd:0b 1655254 /lib/libgcc_s.so.1 @40000000494044dd0b511a34 dovecot: Error: IMAP(matthias): b7df0000-b7df7000 r-xs 00000000 fd:0b 1477936 /usr/lib/gconv/gconv-modules.cache @40000000494044dd0b511e1c dovecot: Error: IMAP(matthias): b7df7000-b7e0d000 rwxp 00000000 fd:0b 508359 /home/matthias/Maildir/REMOVED/dovecot.index @40000000494044dd0b513974 dovecot: Error: IMAP(matthias): b7e0d000-b7e16000 r-xp 00000000 fd:0b 1655734 /lib/libnss_files-2.7.so @40000000494044dd0b513d5c dovecot: Error: IMAP(matthias): b7e16000-b7e18000 rwxp 00008000 fd:0b 1655734 /lib/libnss_files-2.7.so @40000000494044dd0b51452c dovecot: Error: IMAP(matthias): b7e18000-b7e20000 r-xp 00000000 fd:0b 1655736 /lib/libnss_nis-2.7.so @40000000494044dd0b516c3c dovecot: Error: IMAP(matthias): b7e20000-b7e22000 rwxp 00007000 fd:0b 1655736 /lib/libnss_nis-2.7.so @40000000494044dd0b517024 dovecot: Error: IMAP(matthias): b7e22000-b7e35000 r-xp 00000000 fd:0b 1655731 /lib/libnsl-2.7.so @40000000494044dd0b51740c dovecot: Error: IMAP(matthias): b7e35000-b7e37000 rwxp 00012000 fd:0b 1655731 /lib/libnsl-2.7.so @40000000494044dd0b517bdc dovecot: Error: IMAP(matthias): b7e37000-b7e39000 rwxp b7e37000 00:00 0 @40000000494044dd0b51934c dovecot: Error: IMAP(matthias): b7e39000-b7e40000 r-xp 00000000 fd:0b 1655732 /lib/libnss_compat-2.7.so @40000000494044dd0b519b1c dovecot: Error: IMAP(matthias): b7e40000-b7e42000 rwxp 00006000 fd:0b 1655732 /lib/libnss_compat-2.7.so @40000000494044dd0b519f04 dovecot: Error: IMAP(matthias): b7e42000-b7e4e000 r-xp 00000000 fd:0b 1541765 /usr/local/lib/dovecot/lib21_fts_squat_plugin.so @40000000494044dd0b51ba5c dovecot: Error: IMAP(matthias): b7e4e000-b7e4f000 rwxp 0000c000 fd:0b 1541765 /usr/local/lib/dovecot/lib21_fts_squat_plugin.so @40000000494044dd0b51be44 dovecot: Error: IMAP(matthias): b7e4f000-b7e5e000 r-xp 00000000 fd:0b 1655094 /lib/libbz2.so.1.0.4 @40000000494044dd0b51c614 dovecot: Error: IMAP(matthias): b7e5e000-b7e5f000 rwxp 0000f000 fd:0b 1655094 /lib/libbz2.so.1.0.4 @40000000494044dd0b51e93c dovecot: Error: IMAP(matthias): b7e5f000-b7e73000 r-xp 00000000 fd:0b 1476476 /usr/lib/libz.so.1.2.3.3 @40000000494044dd0b51f10c dovecot: Error: IMAP(matthias): b7e73000-b7e74000 rwxp 00013000 fd:0b 1476476 /usr/lib/libz.so.1.2.3.3 @40000000494044dd0b51f4f4 dovecot: Error: IMAP(matthias): b7e76000-b7e77000 r-xp 00000000 fd:0b 1487847 /usr/lib/gconv/ISO8859-1.so @40000000494044dd0b524ae4 dovecot: Error: IMAP(matthias): b7e77000-b7e79000 rwxp 00001000 fd:0b 1487847 /usr/lib/gconv/ISO8859-1.so @40000000494044dd0b5252b4 dovecot: Error: IMAP(matthias): b7e79000-b7e7e000 r-xp 00000000 fd:0b 1541764 /usr/local/lib/dovecot/lib20_fts_plugin.so @40000000494044dd0b52569c dovecot: Error: IMAP(matthias): b7e7e000-b7e7f000 rwxp 00004000 fd:0b 1541764 /usr/local/lib/dovecot/lib20_fts_plugin.so @40000000494044dd0b5271f4 dovecot: Error: IMAP(matthias): b7e7f000-b7e80000 rwxp b7e7f000 00:00 0 @40000000494044dd0b5275dc dovecot: Error: IMAP(matthias): b7e80000-b7fb8000 r-xp 00000000 fd:0b 1655725 /lib/libc-2.7.so @40000000494044dd0b5279c4 dovecot: Error: IMAP(matthias): b7fb8000-b7fb9000 r-xp 00138000 fd:0b 1655725 /lib/libc-2.7.so @40000000494044dd0b528194 dovecot: Error: IMAP(matthias): b7fb9000-b7fbb000 rwxp 00139000 fd:0b 1655725 /lib/libc-2.7.so @40000000494044dd0b52a8a4 dovecot: Error: IMAP(matthias): b7fbb000-b7fbe000 rwxp b7fbb000 00:00 0 @40000000494044dd0b52ac8c dovecot: Error: IMAP(matthias): b7fbe000-b7fc0000 r-xp 00000000 fd:0b 1655728 /lib/libdl-2.7.so @40000000494044dd0b52b074 dovecot: Error: IMAP(matthias): b7fc0000-b7fc2000 rwxp 00001000 fd:0b 1655728 /lib/libdl-2.7.so @40000000494044dd0b52b45c dovecot: Error: IMAP(matthias): b7fc3000-b7fc6000 r-xp 00000000 fd:0b 1541911 /usr/local/lib/dovecot/lib20_zlib_plugin.so @40000000494044dd0b52cfb4 dovecot: Error: IMAP(matthias): b7fc6000-b7fc7000 rwxp 00002000 fd:0b 1541911 /usr/local/lib/dovecot/lib20_zlib_plugin.so @40000000494044dd0b52d784 dovecot: Error: IMAP(matthias): b7fc7000-b7fc9000 rwxp b7fc7000 00:00 0 @40000000494044dd0b52db6c dovecot: Error: IMAP(matthias): b7fc9000-b7fca000 r-xp b7fc9000 00:00 0 [vdso] @40000000494044dd0b52f2dc dovecot: Error: IMAP(matthias): b7fca000-b7fe4000 r-xp 00000000 fd:0b 1655345 /lib/ld-2.7.so @40000000494044dd0b52f6c4 dovecot: Error: IMAP(matthias): b7fe4000-b7fe6000 rwxp 0001a000 fd:0b 1655345 /lib/ld-2.7.so @40000000494044dd0b52fe94 dovecot: Error: IMAP(matthias): bf8c0000-bf8d5000 rw-p bf8c0000 00:00 0 [stack] @40000000494044dd0b5321bc dovecot: Error: child 24572 (imap) killed with signal 6 It's dovecot 1.1.7 on Debian Lenny in linux-vserver(x86). If you guys need more information let me know. matthias

4 5

[Dovecot] expire plugin with pgsql not working
by LÉVAI Dániel 09 Jan '09

09 Jan '09

Hi! I've configured dovecot, and created the db/table/trigger according to http://wiki.dovecot.org/Quota/Dict. I'm using dovecot-1.1.7 and pgsql. When moving a message inside the "monitored" directory, the expires table won't get updated because of an error: statement: INSERT INTO expires (expire_stamp, mailbox) VALUES ('1229993423', 'leva/spamassassin.SPAM') INSERT ERROR: null value in column "username" violates not-null constraint Wonder why doesn't dovecot pass the username too. What could be the problem? Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

2 4

[Dovecot] Sudden, large numbers of "Timeout while waiting for lock for transaction log ..."
by Jack Stewart 09 Jan '09

09 Jan '09

Hi, Up until yesterday, our environment which consists an NFS maildir file store with multiple front end servers, was working fine. We've verified that the server clocks and machines clocks are in sync. Starting yesterday afternoon, We are getting ~850 log entries of the form 'Timeout while waiting for lock for transaction log files' or 'Our dotlock file was modified, assuming it wasn't overridden (kept it 180 sec) Based on packet capture, just one of these index files shows 28553 GETATTRs queries in in a one minute. At this happened at exactly the same time on all of our servers, it is pretty clear that the back-end system (or network) is a major factor although nobody will confess that they made any changes. It would be helpful, and very appreciated, to get more information about what this might be so that we can nudge the correct people to undo whatever it is that they didn't do. We are running currently dovecot 1.1.3 an 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/z/zabala/.INBOX/dovecot.index.log Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Our dotlock file /var/spool/maildir/z/zabala/dovecot-uidlist.lock was deleted (kept it 180 secs) Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/z/zabala/.INBOX/dovecot.index.log Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Our dotlock file /var/spool/maildir/z/zabala/dovecot-uidlist.lock was modified (1231233482 vs 1231233662), assuming it wasn't overridden (kept it 180 secs) Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/z/zabala/.INBOX/dovecot.index.log Jan 6 01:21:02 earth-griffen dovecot: IMAP(zabala): Our dotlock file /var/spool/maildir/z/zabala/dovecot-uidlist.lock was modified (1231233482 vs 1231233662), assuming it wasn't overridden (kept it 180 secs) Jan 6 01:21:04 fire-griffen dovecot: IMAP(sukwon): Timeout while waiting for lock for transaction log file /var/spool/dovecot/indexes/s/sukwon/.Trash/dovecot.index.log -- Jack Stewart Academic Computing Services, IMSS, California Institute of Technology jstewart(a)caltech.edu 626-395-4690 office

2 5

[Dovecot] Enforcing TLS
by Ed Schouten 09 Jan '09

09 Jan '09

Hello all, I've happily been using Dovecot for a couple of years now, but only a couple of days ago I configured it to speak both TLS and SSL for both POP3 and IMAP. Ideally I want users to use TLS, but I've enabled SSL, because some mailers (at least Apple Mail on OS X Tiger) don't support TLS. Right now I'm in sort of a transitional phase, where I'm asking users to enable TLS in their email clients, if not enabled already. After a couple of weeks/months I want to disable any (non-local) connections that don't use TLS or SSL. I already asked on IRC whether this was possible, because I was unable to find this on the Wiki. It turns out there is a configuration switch called `disable_plaintext_auth', but looking at the description this only prevents people from using plain-text username/password authentication. It does not actually enforce TLS or SSL. My question: is there support to enforce TLS when people connect to non-SSL ports? If someone comes up with a solution, I'll add it to the SSL article on the Wiki. I'm using Dovecot 1.1.7, installed on a FreeBSD 6.4-STABLE system. Thanks! -- Ed Schouten <ed(a)80386.nl> WWW: http://80386.nl/

5 8

[Dovecot] Restoring individual messages from a backup into a Maildir setup?
by Thomas Harold 09 Jan '09

09 Jan '09

We have a user who deleted IMAP folders from his account, so I simply tried to restore the folder ".FolderName" from our backup. I checked that file/folder ownership was the same as the original, but the Dovecot IMAP server is throwing errors at the client. I've tried copying the individual message files from the "cur" folders in the backup directory, but Dovecot immediate goes into panic mode and throws errors at the IMAP client when I do that. Even if the file is owned by the currect UID. I've tried putting those files into "tmp" and "new" as well, with no luck. I looked at the following thread, but it didn't help. http://www.dovecot.org/list/dovecot/2007-August/024971.html The thread from Sep 2008 wasn't much help either: http://www.mail-archive.com/dovecot@dovecot.org/msg12846.html ... Eh, I figured this out before I even posted. Restoration is indeed that simple. The problem is that the files were not labeled with the proper SELinux security context after being restored. When the file was restored, it was assigned a context of "root:object_r:file_t", which is not a context that the Dovecot service has permissions to interact with. I had to re-label the files after restoring them with # chcon -R user_u:object_r:mail_spool_t foldername So the lesson here is to check /var/log/messages and look for sealert indicators when restoring files. ... Hopefully that helps some other people out when dealing with Red Hat / CentOS with SELinux set to enforcing mode.

3 7

[Dovecot] dovecot-auth Temporary But Frequent CPU Spike
by Joe Clark 08 Jan '09

08 Jan '09

Hi.. I am setting up a new server (2GHz CPU, Ubuntu 8.10) and am using dovecot for an IMAP server. I have installed dovecot 1.1.4 and Squirrelmail 1.4.15. sudo dovecot -n shows this: # 1.1.4: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_process_per_connection: no mail_privileged_group: mail auth default: passdb: driver: pam userdb: driver: passwd The problem I'm noticing is that if I do top -d 1 while clicking links in Squirrelmail (e.g., logging in, the Inbox link, opening a message), I see that a "dovecot-auth" process maximizes the CPU for about a second. While this is not a huge amount, it seems like with multiple users it could quickly bog down a server . Are there any recommendations or thoughts on what might cause the one-second CPU spike? -- or is that just normal operation? Thanks for your thoughts. - Joe Clark

2 1

[Dovecot] v1.1.8 released
by Timo Sirainen 08 Jan '09

08 Jan '09

http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz.sig Most importantly mbox bugfixes. v1.1 should finally be as stable with mboxes as it was with v1.0. Hopefully we'll also soon have the first v1.2 beta release and the final v1.2.0 somewhat soon after that. - mbox: Several bugfixes. Fixes "next message unexpectedly lost" errors and perhaps some other problems as well. - deliver: It wasn't possible to override boolean settings in lda section by setting them to "no". - Maildir++ quota didn't correctly check if maildirs had changed during recalculation. - kqueue notify: Fixed assert-crash in some situations - dbox: Several fixes to handling Maildir migrations - Logging/error message improvements

6 13

[Dovecot] cannot delete emails in inbox
by JANE CUA 08 Jan '09

08 Jan '09

I am working on upgrading our current squirrelmail and replace uw-imap with dovecot. I have what looks like a successful installation. My current setup is: Centos 5.2 sendmail 8.13.8 dovecot 1.1.17 (imap) squirrelmail 1.4.17 I can send and receive email fine. However when I try to delete an email in my Inbox, it doesn't get deleted. It only sends a copy to the Trash folder. But the email is still in the Inbox. I can purge and delete the contents in my Trash and Sent folder, no problem. I am not sure if this is a Squirrelmail issue or a Dovecot issue. Please advice. Thank you -- Jane

4 8

[Dovecot] Dovecot-auth timeouts
by Javier Fox 08 Jan '09

08 Jan '09

Hello, I've unfortunately been unable to find anything relating to the problem I'm having specifically, in searching the list or google, and so I now plead to you to assistance. I'm running Dovecot as an LDA and SASL auth for Postfix on a Debian 4 box. Dovecot is version 1.0.rc15 (the official debian pkg version). The problem I'm running into is this. After some time of running (lately it's been as little as 5 minutes), I start to see the following errors in dovecot.log: deliver(user(a)domain.com): "Dec 23 14:38:47 "Error: User request from dovecot-auth timed out deliver(anotheruser(a)domain.com): "Dec 23 14:38:48 "Error: User request from dovecot-auth timed out Postfix responds to these by simply deferring the messages. Dovecot itself, however, begins to return 'Authentication failed' messages after significant lag time (sometimes greater than 30s): Connected to localhost. Escape character is '^]'. +OK Dovecot-POP user username +OK pass mypassword -ERR Authentication failed. Now, for authentication, Dovecot is using LDAP on the local server. The only additional information I can find pertaining to these errors is the following from slapd.log: slapd[22593]: connection_input: conn=6 deferring operation: pending operations These messages correspond 1-to-1 to the above 'deliver' errors, where 'conn' is always the same number. Restarting dovecot and ldap resolves the issue for a few minutes, but sure enough the errors start flowing again. I'm really at the end of my rope on this, as nothing I do seems to help. I have a good 500+ customers being effected by this as well, and they're all none too pleased by it. If this is something that will absolutely be resolved by upgrading from source, that is doable, but we'd prefer to stick with the official package version if possible. Dovecot configs follow Thanks, J. Fox ----- configs follow ----- dovecot.conf ------------ auth_verbose = yes auth_debug = yes auth_debug_passwords = yes mail_debug = no base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s protocol lda { postmaster_address = postmaster(a)spiritone.com auth_socket_path = /var/run/dovecot/auth-master log_path = /var/log/dovecot.log info_log_path = /var/log/mail.info } listen = * shutdown_clients = yes mmap_disable = yes lock_method = dotlock maildir_copy_with_hardlinks = no log_path = /var/log/dovecot.log info_log_path = /var/log/mail.log log_timestamp = "%b %d %H:%M:%S " syslog_facility = mail auth_default_realm = involved.com disable_plaintext_auth = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem login_chroot = yes valid_chroot_dirs = /home/vmail/ login_user = postfix login_process_per_connection = yes login_processes_count = 2 login_max_processes_count = 64 login_max_connections = 128 login_greeting = Involved login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c login_log_format = %$: %s default_mail_env = maildir:/home/vmail/domains/%d/%u first_valid_uid = 103 pop3_uidl_format = %08Xu%08Xv auth_cache_size = 10485760 auth_cache_ttl = 3600 auth_worker_max_count = 10 #auth_worker_max_request_count = 50 auth default { mechanisms = PLAIN LOGIN passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 user = vmail group = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } user = vmail } dovecot-ldap.conf ----------------- hosts = localhost auth_bind = yes auth_bind_userdn = cn=%n,ou=%d,ou=mail,dc=domain,dc=com ldap_version = 3 base = ou=mail,dc=domain,dc=com dn = cn=Manager,dc=domain,dc=com dnpass = secret deref = never scope = subtree pass_attrs = mail=user,userPassword=password user_filter = (&(objectClass=VirtualMailAccount)(accountActive=TRUE)(mail=%u)) pass_filter = (&(objectClass=VirtualMailAccount)(accountActive=TRUE)(mail=%u)) user_global_uid = 1001 user_global_gid = 1001 ---end---

2 1

[Dovecot] Panic in v1.1.8
by Mark Sapiro 08 Jan '09

08 Jan '09

I just tried installing dovecot 1.1.8 as an upgrade to 1.1.7 and encountered Panics like the following with pop3 accesses Jan 8 10:55:31 sbh16 dovecot: Killed with signal 15 Jan 8 10:55:49 sbh16 dovecot: Dovecot v1.1.8 starting up Jan 8 10:57:01 sbh16 dovecot: pop3-login: Login: user=<user2>, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Jan 8 10:57:01 sbh16 dovecot: Panic: POP3(user2): file mbox-transaction.c: line 54 (mbox_transaction_commit): assertion failed: (mbox->ibox.box.transaction_count > 0 || mbox->mbox_lock_type == F_UNLCK) Jan 8 10:57:01 sbh16 dovecot: POP3(user2): Raw backtrace: pop3 [0x80c4400] -> pop3 [0x80c445a] -> pop3 [0x80c3d5c] -> pop3 [0x806e209] -> pop3(index_transaction_commit+0x4e) [0x809251e] -> pop3(mailbox_transaction_commit+0x26) [0x80942a6] -> pop3(client_command_execute+0x3c5) [0x805b1f5] -> pop3 [0x805a152] -> pop3(io_loop_handler_run+0x100) [0x80cc100] -> pop3(io_loop_run+0x28) [0x80cb208] -> pop3(main+0x5d2) [0x805bda2] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x4614cdec] -> pop3 [0x80594d1] Jan 8 10:57:01 sbh16 dovecot: child 32263 (pop3) killed with signal 6 I have a few users who access their mailbox via pop3 every few minutes and they all hit this. I reverted to 1.1.7 and all was OK Here's dovecot -n from 1.1.7. The dovecot.conf for 1.1.8 was the same. # 1.1.7: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) ext3 protocols: pop3 pop3s ssl_cert_file: /etc/postfix/grizz-cert.pem ssl_key_file: /etc/postfix/grizz-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_access_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_lock_session: yes auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 2