- dovecot - dovecot.org

[Dovecot] Processing sent items
by Bruce Markey 29 Sep '13

29 Sep '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 How does dovecot handle sent items and is it possible to "process" them befor they get saved in the sent item folder? My scenario is that I'm running postifx + dovecot with all incoming and outgoing mail passed to a script that encrypts the mail with the public key of the recipient. The only place now that has unencrypted mail sitting on the server is the sent items, I'd like to fix that. What would be the best way to proceed here? - -- Encrypt everything. Public key: https://www.secryption.com/BruceMarkey.asc I believe that any violation of privacy is nothing good. Lech Walesa -----BEGIN PGP SIGNATURE----- Version: OpenPGP.js v.1.20130420 Comment: http://openpgpjs.org wsFcBAEBCAAQBQJSR+odCRDIVcS4Lgc6WAAAIOYP/AqT3HWNbZZnoRXgeq27 n8id40wWemf+IgXGEe1fCTX7d/x+Zinj7bZw5EVq8WlLDxwpOhJGDNUAfA2+ 2z+6J7H0dAHk8rSJZqZfNaGWQQhY3ZehwJnojGJnM5ORuHHH/9WsY91jq26u 4Bzg54tUo+aIoWJHLWlVdqiDjJsW4n536UaHcKlVQx0JCe1byt4eXAmJP9dh Dc9YkP3lKUdW9oxgusJRLOxGfaN++nIFHSBDV6wGp0gEdCuzkgphdEFMnUX9 mD1dwPrDMlEmqHkiyHFH9RGGFvHRaTmdREW8eX9vnHp2PBXthbqd3RKWs7Q4 FmnfoS18inSbTM9Cp79HgQBMKBu66/qtdI6q5q45An9lmQAGf2ElvApSj8b+ ZI5GklVGSyrkxwRTOSRij57SDcRexNhlHg1jsDwSFvNjW5CzH0cB+mVU98eB TqfbIPKvGuqKzpdgf7SNJhZXmmkRrtsL/pI3xCheaZVh34Jxx6N/mP01pDEv d4IrajaTS+0mv6cM4z5f6k62YypHNB9fSTTjIKIqAvLgWMyQIFdjd9BQ1PQK pPiu+btbhhb4RgKa3LFSTp2xJVZlKXd2bqTaRkv63eUgF9NUIr3RYM98I75z mMnxfR5QDZIS6s5tlmZXF7zvCzXoRj30xEp8IsTMrfA4GzLpfAVsJaSUZlSo j5I3 =5Tw/ -----END PGP SIGNATURE-----

2 2

[Dovecot] How to authenticate against SQL DB with custom-ciphered passwords?
by Nicolay Vizovitin 29 Sep '13

29 Sep '13

Hello, I'm about to start developing authentication/password-scheme module for Dovecot. So I would like to get some advice before actually committing to doing things in particular way. Hope somebody will be able to help me :) For the record, I am currently targeting latest stable Dovecot version 2.2.5. I have an SQL DB with mail users' authentication data. Passwords are stored either encrypted via system crypt(3) or ciphered with some custom algorithm (think something symmetrical like AES, so passwords can be decrypted into plain form). I want to use this DB as both userdb and passdb backend. The issue, of course, is with ciphered passwords support. 1) Is it feasible to just implement a new password scheme for ciphered passwords support and still use stock passdb driver in Dovecot for SQL DB access? So that passwords in this scheme would be treated as PLAIN (in a sense that both cleartext and shared secret authentication methods would work). 2) Provided I implement custom password scheme for ciphered passwords, what is the best way to be capable to perform authentication against both ciphered and encrypted passwords? Ciphered and encrypted passwords are stored in different fields of SQL table (one of them is NULL when the other one is set). a) Do I define two passdb clauses with their own default_pass_scheme (equal to my new scheme or CRYPT for encrypted passwords) and use fallback to effectively check both of them? b) Do I modify SQL query so that it prefixes existing password with correct scheme (I'm not sure this will be easy enough to do)? 3) Is it mandatory to provide password generation routine for custom password scheme? When it will be used? 4) Maybe it's better to just implement a plugin that serves as both userdb and passdb driver (in other words a kind of generic authentication module)? What are advantages and disadvantages of each method - custom password scheme + stock SQL driver VS. custom userdb and passdb driver? Fortunately, I already have all the required credentials lookup and verification code. So in any case the question is only in figuring out suitable Dovecot APIs and integrating the existing code. 5) I have previously implemented similar custom authentication module for Courier-IMAP (Courier-Authlib to be precise) to use the same SQL DB. And I will need to support both IMAP servers for some time. So it is only natural to expect some generic solution to be possible. I'd like to remind that I need to be able to supply either encrypted password or deciphered plain password, or just check against them. Is it possible to do so in a common way? If so, what method should I use? I would expect SASL helping me out here, but AFAIK, both Dovecot and Courier-IMAP can only serve as SASL servers (providing authentication services), not clients. 6) I obviously care about providing enhanced security, especially against stealing mail passwords. So any additional advice or related guidelines are welcome. 7) Somewhat unrelated question: what is the best way to test IMAP (and maybe POP3 as well) server performance and compare it to another server? I'm interested in both login performance (the part I will influence) and performance with many mails in mailbox. I heard imaptest is suitable for this task. Are there any recipes or example testing scenarios you might share? ;) I would be grateful for any insight in these issues. If I chose a wrong mailing list to post to, please feel free to correct me. Thanks for your time! :) -- Best regards, Nick

2 2

[Dovecot] Conditional jump or move depends on uninitialised value(s)
by Tamsy 28 Sep '13

28 Sep '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Timo, Dovecot 2.2.6 compiled on Ubuntu 10.04 fails on "make check" with the following errors. "make install" is finishing just fine and Dovecot itself works flawlessly so far. - ----- 8< ----- http header invalid [0]: parse failure ............................... : ok: Expected ':' after header field name 'Server', but found ' ' http header invalid [0] .............................................. : ok http header invalid [1]: parse failure ............................... : ok: Expected ':' after header field name 'X', but found ' ' http header invalid [1] .............................................. : ok http header invalid [2]: parse failure ............................... : ok: Expected LF after CR at end of header, but found 'A' http header invalid [2] .............................................. : ok http header invalid [3]: parse failure ............................... : ok: Expected line end after header field 'Accept', but found 0x7f http header invalid [3] .............................................. : ok http header invalid [4]: parse failure ............................... : ok: Expected ':' after header field name 'Suhosin-Patch', but found ' ' http header invalid [4] .............................................. : ok http header invalid [5]: parse failure ............................... : ok: Excessive header size http header invalid [5] .............................................. : ok http header invalid [6]: parse failure ............................... : ok: Excessive header field size http header invalid [6] .............................................. : ok http header invalid [7]: parse failure ............................... : ok: Excessive number of header fields http header invalid [7] .............................................. : ok 0 / 66 tests failed ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F987: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F98D: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B0: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804FC92: http_header_parse_next_field (http-header-parser.c:320) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B2: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F361: test_http_header_parse_valid (test-http-header-parser.c:181) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F987: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F98D: http_header_parse_next_field (http-header-parser.c:294) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B0: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804FC92: http_header_parse_next_field (http-header-parser.c:320) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804F9B2: http_header_parse_next_field (http-header-parser.c:296) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== ==15579== Conditional jump or move depends on uninitialised value(s) ==15579== at 0x804FCDF: http_header_parse_next_field (http-header-parser.c:320) ==15579== by 0x804F225: test_http_header_parse_invalid (test-http-header-parser.c:325) ==15579== by 0x8050251: test_run_funcs (test-common.c:228) ==15579== by 0x80503D1: test_run (test-common.c:236) ==15579== by 0x804F164: main (test-http-header-parser.c:343) ==15579== make[2]: *** [check-test] Error 1 make[2]: Leaving directory `/usr/local/src/dovecot-2.2.6/src/lib-http' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/usr/local/src/dovecot-2.2.6/src' make: *** [check-recursive] Error 1 - ----- >8 ----- Is it just me? Cheers, Tamsy -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (MingW32) iQEcBAEBAgAGBQJSQ9FeAAoJEKYXVM1dyOfZVsoIAOM1z1aULWvVqGJScmd8uNXz EG1gRnG6vlrjdUa+8mYQq7RPZZbZ2Cvxd73rkWtptPFAQX+gKsHsh53HS2GKohle W6dJWnEdR7cvUk1UC7FHK3KR5+Z2pdbxhwGB0G26jHKf2OM7dyNcrmtXgkvb3Mwp 4AHrRHVYnPDkcF4Mc9mCnlGdHGsG1bA2BMtI6eR1vbAMKlUy9v11EfunDJHwqkwf 9A5vWAqCnNT9QewJctrHubnN+Rzz5ZLA0cc5ngTL+hsSknIKzH/bj1R99Orca7VN AzBYkWRQ2GqKWxdSBs8RSGv/bVojW1SLjp04xEea+zUeV6sg3RMGkou/pK+lfj4= =o8pw -----END PGP SIGNATURE-----

2 3

Re: [Dovecot] New install not working.
by Joseph Tam 28 Sep '13

28 Sep '13

"Rhorer, Leslie" <Leslie.Rhorer(a)twtelecom.com> writes: > At first things were looking much better, except that most of my > folders, other than the Inbox, were not showing up. I started changing > both the dovecot configuration and the folder structure of my mail > files, but now I can't even get the Inbox to populate. Outlooks says > it is there, along with any folders I create new in Outlook, plus the > Trash folder, which is the only non-local folder with anything in it. > Try what I might, I can't get my Inbox to populate or any of the > existing folders to show up at all. Here is the current output from > dovecot -n: > .... > mail_location = mbox:/RAID/home/%u/mail Maybe try mail_location = mbox:/RAID/home/%n/mail:INBOX=/RAID/home/%n/mail/inbox (%n does not include the domain part, but it might be the same as %u). Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] service anvil and ssl-params not starts with dovecot started
by Dewey Du 28 Sep '13

28 Sep '13

Hi My dovecot started with the error below. What's the most possible reason for the error? “2013-08-28 11:41:40 ”master: Info: Dovecot v2.2.5 starting up (core dumps disabled) “2013-08-28 11:42:00 ”anvil: Fatal: Error reading configuration: Timeout reading config from /var/run/dovecot/config “2013-08-28 11:42:00 ”master: Error: service(anvil): command startup failed, throttling for 2 secs “2013-08-28 11:42:00 ”ssl-params: Fatal: Error reading configuration: Timeout reading config from /var/run/dovecot/config “2013-08-28 11:42:00 ”master: Error: service(ssl-params): command startup failed, throttling for 2 secs Actually, After dovecot starts, I can telnet 110, but it takes 30seconds or so to get through the authentication. I suspect whether the error above cause the issue or not. Other information: dovecot version v2.2.5 use posfix, dovecot sasl, and mysql Attached my dovecot.conf: #auth_debug = yes auth_mechanisms = plain login #debug_log_path = /var/log/dovecot.debug default_internal_user = postfix default_login_user = postfix disable_plaintext_auth = no first_valid_uid = 1000 last_valid_uid = 1000 mail_gid = 1000 mail_uid = 1000 log_path = /var/log/dovecot.log mail_location = maildir:/var/vmail/%d/%u mail_privileged_group = vmail protocols = imap pop3 listen = * base_dir = /var/run/dovecot/ service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } user = root } ssl = no userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol pop3 { pop3_uidl_format = %08Xu%08Xv }

2 2

Re: [Dovecot] recipient_delimiter
by voytek＠sbt.net.au 28 Sep '13

28 Sep '13

>> $recipient_delimiter = ‘+’ ahem, dumb question coming: //I often read various threads here, and, look at my own setup, with a view of optimizing or understanding things I should...// I have working dovecot 2.1.1 with postfix, only have virtual domains, all users in mysql; '+' delimiter is enabled in postfix, and, works OK postfix]# grep _delimiter main.cf # The recipient_delimiter parameter specifies the separator between recipient_delimiter = + BUT, I seem to have nothing in dovecot.conf: postfix]# cd /etc/dovecot dovecot]# grep delimiter * dovecot]# cd conf.d conf.d]# grep delimiter * 15-lda.conf:#recipient_delimiter = + 20-lmtp.conf:# the mail to the detail mailbox. See also recipient_delimiter and 20-lmtp.c_org:# the mail to the detail mailbox. See also recipient_delimiter and should I also enter $recipient_delimiter = ‘+’ in my /etc/dovecot/dovecot.conf ? what will it add to this working setup, what am I missing? thanks for all pointers

6 10

[Dovecot] Truncated emails
by David LEROUX 27 Sep '13

27 Sep '13

Hi, I'm running Dovecot IMAP and some times receive truncated emails. Don't understand why. Here are my settings: /dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-48-server x86_64 Ubuntu 10.04.4 LTS log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot.log log_timestamp: Â« %Y-%m-%d %H:%M:%S Â» login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_max_userip_connections: 11 mail_location: maildir:~/Maildir mbox_write_locks: fcntl dotlock imap_client_workarounds: tb-extra-mailbox-sep auth default: passdb: driver: pam userdb: driver: passwd/ Hop you can help. Thanks, David

2 3

[Dovecot] v2.2.6 released
by Timo Sirainen 27 Sep '13

27 Sep '13

http://dovecot.org/releases/2.2/dovecot-2.2.6.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.6.tar.gz.sig I didn't have time to look into the latest reported dsync replication bugs, but this release should have been done a long time ago already and I'm busy for next few days, so no more waiting. Things seem to be working quite well in general though. * acl: If public/shared namespace has a shared subscriptions file for all users, don't list subscription entries that are not visible to the user accessing it. + doveadm: Added "auth lookup" command for doing passdb lookup. + login_log_format_elements: Added %{orig_user}, %{orig_username} and %{orig_domain} expanding to the username exactly as sent by the client (before any changes auth process made). + Added ssl_prefer_server_ciphers setting. + auth_verbose_passwords: Log the password also for unknown users. + Linux: Added optional support for SO_REUSEPORT with inet_listener { reuse_port=yes } - director: v2.2.5 changes caused "SYNC lost" errors - dsync: Many fixes and error handling improvements - doveadm -A: Don't waste CPU by doing a separate config lookup for each user - Long-running ssl-params process no longer prevents Dovecot restart - mbox: Fixed mailbox_list_index=yes to work correctly

3 3

[Dovecot] Index error copying compressed message
by Richard Platel 27 Sep '13

27 Sep '13

Hi. Dovecot 2.2, with the zlib plugin, I think we're getting bad index entries on IMAP COPY. On copying a message to an empty folder, in the dovecot error log I see: Sep 19 20:34:25 imap01 dovecot: imap(grain(a)rp-auth-test.com): Error: Cached message size smaller than expected (615 < 971) Sep 19 20:34:25 imap01 dovecot: imap(grain(a)rp-auth-test.com): Error: Corrupted index cache file /mail/index01/434/860/grain(a)rp-auth-test.com/.Bup/dovecot.index.cache: Broken physical size for mail UID 0 Sep 19 20:34:25 imap01 dovecot: imap(grain(a)rp-auth-test.com): Error: read() failed: Invalid argument (uid=0) (Note this happens from the copy operation, not a subsequent access. Also note the UID is always 0). The filename for the message is: -rw------- 2862 mail mail 615 Aug 29 15:38 1379622865.M228140P11548.imap01,S=971,W=988:2,S S= size looks correct: $ zcat 1379622865.M228140P11548.imap01\,S\=971\,W\=988\:2\,S |wc 17 51 971 doveadm dump says: $ sudo -u mail doveadm -c /he/dovecot/conf/dovecot.conf dump /mail/index01/434/860/grain(a)rp-auth-test.com/.Bup/ Detected file type: index -- INDEX: /mail/index01/434/860/grain(a)rp-auth-test.com/.Bup//dovecot.index version .................. = 7.3 base header size ......... = 120 header size .............. = 208 record size .............. = 12 compat flags ............. = 1 index id ................. = 1379605150 (2013-09-19 15:39:10) flags .................... = 0 uid validity ............. = 1377629137 (2013-08-27 18:45:37) next uid ................. = 14309 messages count ........... = 1 seen messages count ...... = 1 deleted messages count ... = 0 first recent uid ......... = 14308 first unseen uid lowwater = 14309 first deleted uid lowwater = 14308 log file seq ............. = 6 log file tail offset ..... = 204 log file head offset ..... = 204 day stamp ................ = 1379548800 (2013-09-19 00:00:00) day first uid[0] ......... = 1 day first uid[1] ......... = 0 day first uid[2] ......... = 0 day first uid[3] ......... = 0 day first uid[4] ......... = 0 day first uid[5] ......... = 0 day first uid[6] ......... = 0 day first uid[7] ......... = 0 -- Extension 0 -- name ........ = maildir hdr_size .... = 36 reset_id .... = 0 record_offset = 0 record_size . = 0 record_align = 0 header - new_check_time .... = 2013-09-19 20:34:10 - new_mtime ......... = 2013-09-19 20:08:51 - new_mtime_nsecs ... = 792530000 - cur_check_time .... = 2013-09-19 20:35:38 - cur_mtime ......... = 2013-09-19 20:35:38 - cur_mtime_nsecs.... = 227710000 - uidlist_mtime ..... = 2013-09-19 20:35:38 - uidlist_mtime_nsecs = 254613000 - uidlist_size ...... = 1025178 -- Extension 1 -- name ........ = cache hdr_size .... = 0 reset_id .... = 1379605174 record_offset = 8 record_size . = 4 record_align = 4 -- Keywords -- -- CACHE: /mail/index01/434/860/grain(a)rp-auth-test.com/.Bup//dovecot.index.cache major version ........ = 1 minor version ........ = 1 indexid .............. = 1379605150 (2013-09-19 15:39:10) file_seq ............. = 1379605174 (2013-09-19 15:39:34) (24 compressions) continued_record_count = 0 record_count ......... = 0 used_file_size (old) . = 108 deleted_record_count . = 0 field_header_offset .. = 32 (0x88808080 nontranslated) -- Cache fields -- # Name Type Size Dec Last used 0: flags bit 4 tmp 2013-09-19 20:07 1: hdr.Message-ID hdr - tmp 2013-09-19 20:07 2: hdr.X-HE-Tag hdr - tmp 2013-09-19 20:07 -- RECORDS: 1 RECORD: seq=1, uid=14308, flags=0x08 (Seen) - ext 3 cache : 0 (00000000) $ sudo -u mail dovecot -c /he/dovecot/conf/dovecot.conf -n # 2.2.4.3 (12e60e803a54+): /he/dovecot/conf/dovecot.conf # OS: Linux 3.4.46-dom0-2.0.0 x86_64 Debian 7.0 debug_log_path = syslog disable_plaintext_auth = no first_valid_uid = 8 info_log_path = syslog lock_method = dotlock log_path = /var/run/dovecot/log-fifo log_timestamp = mail_fsync = always mail_gid = mail mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = zlib quota tc_mail_log notify tc_proc stats mail_uid = mail maildir_very_dirty_syncs = yes mmap_disable = yes namespace inbox { inbox = yes location = prefix = } passdb { args = host=localhost port=1143 username=%L{user}::%L{service}::%L{rip}::%L{session} driver = imap } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_fields = uid box msgid flags hetag memcached_servers = 10.5.47.223,10.5.47.222 quota = dict:User quota::proxy:/var/run/auth_proxy_dovecot/quotasocket:quota stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 16 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 service anvil { unix_listener anvil-auth-penalty { mode = 00 } } service imap-login { inet_listener imap { address = 0 } inet_listener imaps { port = 0 } process_limit = 29 process_min_avail = 14 service_count = 0 } service imap-postlogin { executable = script-login -d /he/dovecot/utils/post_login.sh } service imap { executable = imap imap-postlogin process_limit = 1270 vsz_limit = 0 } service pop3-login { inet_listener pop3 { address = 0 } inet_listener pop3s { port = 0 } process_limit = 29 process_min_avail = 14 service_count = 0 } service pop3-postlogin { executable = script-login -d /he/dovecot/utils/post_login.sh } service pop3 { executable = pop3 pop3-postlogin process_limit = 206 vsz_limit = 512 M } service stats { fifo_listener stats-mail { mode = 0600 user = mail } } ssl = no userdb { args = /he/dovecot/conf/dovecot-tc-dict-auth.conf driver = dict } verbose_proctitle = yes protocol imap { mail_plugins = zlib quota tc_mail_log notify tc_proc stats imap_stats imap_quota }

2 2

[Dovecot] Released Pigeonhole v0.4.2 for Dovecot v2.2.6 and Pigeonhole v0.3.6 for Dovecot v2.1.17.
by Stephan Bosch 27 Sep '13

27 Sep '13

Hello Dovecot users, Now that Dovecot v2.2.6 is released, I can release a new Pigeonhole. Due to the SO_REUSEPORT changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. I also made a new release for Dovecot v2.1.17 that includes most of these fixes and some older ones. A word of warning for people using doveadm sync in combination with sieve: make sure you update both sides of the replication to avoid problems after upgrade. The attribute sub-tree under which Sieve scripts are replicated has moved to a different root. Since we expect that very few people are affected, there is no facility for backwards compatibility. This is no problem as long as both sides are upgraded. There is one new feature for the Sieve vacation extension. Normally vacation replies are sent with <> sender to prevent mail loops. A setting is provided to override this behavior (doc/extensions/vacation.txt), as requested on the mailing list. This is not a violation of the specification, but use this with care. Changelog v0.4.2: * Incompatible change in Sieve doveadm plugin: the root attribute for Sieve scripts is changed. Make sure that you update both sides of a dsync setup simultaneously when Sieve is involved, otherwise synchronization will likely fail. + Added support for sending Sieve vacation replies with an actual sender, rather than the default <> sender. Check the updated doc/extensions/vacation.txt for more information. - Fixed a binary code read problem in the `set' command of the Sieve variables extension. Using the set command with a modifier and an empty string value would cause code corruption problems while running the script. - Various fixes for doveadm-sieve plugin, mostly crashes. These include a fix for the `Invalid value for default sieve attribute' problem. - Various fixes for compiler and static analyzer warnings, e.g. as reported by CLang and on 32 bit systems. - Fixed the implementation of the new :options flag for the Sieve include extension. - Fixed potential segfault bug at deinitialization of the lda-sieve plugin. - Fixed messed up hex output for sieve-dump tool. Changelog v0.3.6: - Fixed a binary code read problem in the `set' command of the Sieve variables extension. Using the set command with a modifier and an empty string value would cause code corruption problems while running the script. - Various fixes for compiler and static analyzer warnings, as reported by CLang. - ManageSieve: Fixed '[' ']' stupidity for response codes (only happened before login). - Fixed setting name in example-config/conf.d/20-managesieve.conf. - Fixed messed up hex output for sieve-dump tool. The releases are available as follows: http://www.rename-it.nl/dovecot/2.2/dovecot-2.2-pigeonhole-0.4.2.tar.gz http://www.rename-it.nl/dovecot/2.2/dovecot-2.2-pigeonhole-0.4.2.tar.gz.sig http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.6.tar.gz http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.6.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

2 1