- dovecot - dovecot.org

[Dovecot] Debian packages for dovecot 1.1.x
by Seth Mattinen 09 Jan '09

09 Jan '09

Because I'm tired of seeing Debian users look like idiots for using such horribly out of date versions just because they run "stable", I've set up a page with .deb packages of my 1.1.x rebuilds for use under lenny. http://www.rollernet.us/opensource/ Standard disclaimer applies: use at your own risk, no warranty, no support, if it eats your first born or erases your computer I don't want to hear about it. ;) -- Seth Mattinen sethm(a)rollernet.us Roller Network LLC

3 8

[Dovecot] deliver & per user log file
by Marcin Rzepecki 09 Jan '09

09 Jan '09

Hello, is there a way to log Dovecot deliver actions in user home directory like procmail did (e.g. in ~/Mail/deliver.log)? Greetings, -- Marcin Rzepecki m.rzepecki(at)iem.pw.edu.pl

4 8

[Dovecot] apply Sieve filter to existing mails
by Jakob Grießmann 09 Jan '09

09 Jan '09

Hello, is it possible to apply Sieve filter to existing mails, e.g. for testing purposes whether my rules work as expected? Thanks, Jakob

1 0

[Dovecot] Error: dict: Failed to initialize dictionary 'expire'
by LÉVAI Dániel 09 Jan '09

09 Jan '09

Hi! Using dovecot-1.1.17, and BDB-4.6.21. I'm having this error in every two weeks or so. I've running this in a crontab: /usr/local/sbin/dovecot --exec-mail \ ext /usr/local/libexec/dovecot/expire-tool The expire plugin and tool is working fine, the configuration is ok, and I'm using the BDB backend. What happens in every ~two weeks is dovecot starts to give me this error messages: Error: dict: db_env: Unable to allocate memory for transaction detail Error: dict: Failed to initialize dictionary 'expire' Reading thru Oracle's Berkeley DB FAQ: http://www.oracle.com/technology/products/berkeley-db/faq/db_faq.html#28 "This error means the maximum number of active transactions configured for Berkeley DB has been reached [...] When all of the memory available in the database environment for transactions is in use, calls to being a transaction will fail until some active transactions complete. By default, the database environment is configured to support at least 20 active transactions." What could be happening here? Why coudn't it finish its transactions? After a dovecot restart it works fine :\ Thanks in advance for any hints. Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

2 4

[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 09 Jan '09

09 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