- dovecot - dovecot.org

issues with doveadm sieve commands
by Michael Grimm 30 Apr '16

30 Apr '16

Hi This is dovecot-pigeonhole 0.4.13 and dovecot 2.2.23 at FBSD 10.3-STABLE. I am used to run doveadm sieve commands for some time now whenever updating a sieve script. Recently those commands fail with a user set explicitly, e.g.: mail> doveadm sieve list -u test doveadm(root): Error: User doesn't exist When asking for all users, I do not run into any error: mail> doveadm sieve list -u '*' user1 default ACTIVE [snip] test default ACTIVE mail> doveadm sieve list -A user1 default ACTIVE [snip] test default ACTIVE That is true for all doveadm sieve commands, but other will work, like: mail> doveadm user -u test userdb: test user : test mail : mdbox:/—path-to-maildir--/test Hmm, any idea what is going on? I do not know when those commands stopped to work, I didn't try to update my sieve scripts for some time now. Thanks and regards, Michael

3 3

Recent update causes segfault in proxy mode
by Ralf Hildebrandt 30 Apr '16

30 Apr '16

I'm using the auto builds (2:2.2.24-1~auto+3) for Ubuntu/Debian. The recent upgrade to 2.2.24 cause the follwoing error to appear: I can log in to a mailbox via dovecot I can delete emails Upon expunge, dovecot crashes: Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142514, msgid=, size=10086 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142519, msgid=, size=1232 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142520, msgid=, size=1232 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142521, msgid=, size=1240 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142522, msgid=, size=1239 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142523, msgid=, size=1239 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142524, msgid=, size=6662 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142525, msgid=, size=5342 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142527, msgid=, size=9718 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142528, msgid=, size=3019 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142529, msgid=, size=7625 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142530, msgid=, size=31900 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142531, msgid=, size=4827 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142532, msgid=, size=4096 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142533, msgid=, size=7100 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142534, msgid=, size=4422 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142535, msgid=, size=10856 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142536, msgid=, size=13305 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142574, msgid=, size=3113 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142575, msgid=, size=4155 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142576, msgid=, size=5114 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142577, msgid=, size=3266 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): Fatal: master: service(imap): child 12393 killed with signal 11 (core dumped) Unfortunately, I'm not getting a backtrace :( -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

3 4

Setting lmtp_user_concurrency_limit causes anvil permission error
by Tom Sommer 30 Apr '16

30 Apr '16

I've set lmtp_user_concurrency_limit to 5 and now LMTP throws this at me for every delivery: Apr 07 13:38:33 lmtp(4434): Error: net_connect_unix(/var/run/dovecot/anvil) failed: Permission denied ls -l /var/run/dovecot/anvil srw------- 1 root root 0 Apr 7 13:32 /var/run/dovecot/anvil If I set lmtp_user_concurrency_limit to 0, the error goes away. -- Tom

3 3

Panic: file message-part-serialize.c: line 90 (part_serialize): assertion failed: (part->children == NULL)
by Andreas Jobs 30 Apr '16

30 Apr '16

Hi, I just found this in my logs: Apr 29 11:05:20 lmtp(joerg.eggenstein(a)ruhr-uni-bochum.de): Panic: file message-part-serialize.c: line 90 (part_serialize): assertion failed: (part->children == NULL) Apr 29 11:05:20 lmtp(joerg.eggenstein(a)ruhr-uni-bochum.de): Error: Raw backtrace: /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x9c7f9) [0x7fa88bfbf7f9] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x9db92) [0x7fa88bfc0b92] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa88bfbfb3f] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x8a1bf) [0x7fa88bfad1bf] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x8a163) [0x7fa88bfad163] -> /usr/local/dovecot/lib/dovecot/libdovecot.so.0(message_part_serialize+0x27) [0x7fa88bfad20c] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(+0xccf29) [0x7fa88c327f29] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(+0xcdd01) [0x7fa88c328d01] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(index_mail_cache_parse_deinit+0xc9) [0x7fa88c32b236] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(dbox_save_end+0x1c4) [0x7fa88c2bed50] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x5a6d5) [0x7fa88c2b56d5] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(mdbox_save_finish+0x18) [0x7fa88c2b5840] -> /usr/local/dovecot/lib/dovecot/lib10_quota_plugin.so(+0xe512) [0x7fa88b751512] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_save_finish+0xb4) [0x7fa88c298dee] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x6c) [0x7fa88c28a757] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(mdbox_copy+0x85) [0x7fa88c2b601e] -> /usr/local/dovecot/lib/dovecot/lib10_quota_plugin.so(+0xe322) [0x7fa88b751322] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0xec) [0x7fa88c2990b4] -> /usr/local/dovecot/lib/dovecot/libdovecot-storage.so.0(mailbox_save_using_mail+0x34) [0x7fa88c29921a] -> /usr/local/dovecot/lib/dovecot/libdovecot-sieve.so.0(+0x51899) [0x7fa88b2b5899] -> /usr/local/dovecot/lib/dovecot/libdovecot-sieve.so.0(+0x45bc5) [0x7fa88b2a9bc5] -> /usr/local/dovecot/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0xbf) [0x7fa88b2aa250] -> /usr/local/dovecot/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x7c) [0x7fa88b2c0597] -> /usr/local/dovecot/lib/dovecot/lib90_sieve_plugin.so(+0x32d8) [0x7fa88b53f2d8] -> /usr/local/dovecot/lib/dovecot/lib90_sieve_plugin.so(+0x40e1) [0x7fa88b5400e1] -> /usr/local/dovecot/lib/dovecot/lib90_sieve_plugin.so(+0x435c) [0x7fa88b54035c] -> /usr/local/dovecot/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x68) [0x7fa88c5db90c] -> dovecot/lmtp [DATA 134.147.53.148 redacted(a)ruhr-uni-bochum.de](+0x92ea) [0x7fa88ca102ea] Apr 29 11:05:20 lmtp(redacted(a)ruhr-uni-bochum.de): Fatal: master: service(lmtp): child 12080 killed with signal 6 (core dumped) It looks like that this may be caused by a mail where there is the blank line after a part header missing: I attach Backtrace and configuration. --Andreas -- ! Andreas Jobs Network Operation Center ! ! Ruhr-Universitaet Bochum ! ! One Day I Will Find This Peer Guy and Then I Will Reset HIS Connection !

2 2

Unable to get mail?
by Jason Pruim 30 Apr '16

30 Apr '16

Hey everyone, I'm not sure I'm on the right list for this one... I have a postfix/dovecot install that was running fine on amazon web services that all of a sudden stopped receiving mail... In my mail log all I get is this: Apr 30 03:16:26 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Connection closed in=595 out=1459 Apr 30 03:16:31 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=31865, TLS, session=<cbidL6sxXQBEaap5> Apr 30 03:16:33 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=31867, TLS, session=<frXBL6sxYQBEaap5> Apr 30 03:16:34 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=97 out=440 Apr 30 03:16:38 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=31869, TLS, session=<mvQGMKsxaABEaap5> Apr 30 03:19:14 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=408 out=1385 Apr 30 03:19:14 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=847 out=3067 Apr 30 03:20:25 ip-172-31-28-46 postfix/postfix-script[3891]: stopping the Postfix mail system Apr 30 03:20:25 ip-172-31-28-46 postfix/master[31225]: terminating on signal 15 Apr 30 03:20:25 ip-172-31-28-46 postfix/postfix-script[3963]: starting the Postfix mail system Apr 30 03:20:25 ip-172-31-28-46 postfix/master[3964]: daemon started -- version 2.6.6, configuration /etc/postfix Apr 30 03:20:44 ip-172-31-28-46 dovecot: master: Warning: Killed with signal 15 (by pid=3977 uid=0 code=kill) Apr 30 03:20:44 ip-172-31-28-46 dovecot: imap: Server shutting down. in=472 out=1366 Apr 30 03:20:45 ip-172-31-28-46 dovecot: master: Dovecot v2.2.10 starting up for imap, pop3, lmtp (core dumps disabled) Apr 30 03:21:17 ip-172-31-28-46 dovecot: imap-login: Aborted login (no auth attempts in 9 secs): user=<>, rip=68.105.170.121, lip=172.31.28.46, session=<Ar2lQKsxnQBEaap5> Apr 30 03:24:30 ip-172-31-28-46 postfix/postfix-script[4141]: stopping the Postfix mail system Apr 30 03:24:30 ip-172-31-28-46 postfix/master[3964]: terminating on signal 15 Apr 30 03:24:30 ip-172-31-28-46 dovecot: master: Warning: Killed with signal 15 (by pid=4147 uid=0 code=kill) Apr 30 03:25:28 ip-172-31-28-46 postfix/postfix-script[2761]: starting the Postfix mail system Apr 30 03:25:28 ip-172-31-28-46 postfix/master[2762]: daemon started -- version 2.6.6, configuration /etc/postfix Apr 30 03:26:22 ip-172-31-28-46 dovecot: master: Dovecot v2.2.10 starting up for imap, pop3, lmtp (core dumps disabled) Apr 30 03:27:03 ip-172-31-28-46 dovecot: imap-login: Aborted login (no auth attempts in 6 secs): user=<>, rip=68.105.170.121, lip=172.31.28.46, session=<eOVMVasxbQBEaap5> Apr 30 03:27:36 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=68.105.170.121, lip=172.31.28.46, mpid=3001, TLS, session=<g49GV6sxiABEaap5> Apr 30 03:27:54 ip-172-31-28-46 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 2 secs): user=<beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=<y6EuWKsxoAB/AAAB> Apr 30 03:28:06 ip-172-31-28-46 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 6 secs): user=<beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured, session=</4W0WKsxogB/AAAB> Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3008, secured, session=<zwtFWasxpAB/AAAB> Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=29 out=466 Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3011, secured, session=<jLBHWasxpgB/AAAB> Apr 30 03:28:10 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=44 out=538 Apr 30 03:28:11 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3014, secured, session=<CulYWasxqAB/AAAB> Apr 30 03:28:11 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=314 out=6899 Apr 30 03:28:12 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3017, secured, session=<CH9iWasxqgB/AAAB> Apr 30 03:28:12 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=209 out=816 Apr 30 03:29:12 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3024, secured, session=<lErzXKsxrgB/AAAB> Apr 30 03:29:12 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:30:12 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3027, secured, session=<9r6GYKsxsAB/AAAB> Apr 30 03:30:12 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:31:13 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3037, secured, session=<QogvZKsxsgB/AAAB> Apr 30 03:31:13 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:32:14 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3043, secured, session=<Zp7SZ6sxtAB/AAAB> Apr 30 03:32:14 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:33:17 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3051, secured, session=<djmLa6sxtgB/AAAB> Apr 30 03:33:17 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:34:17 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3057, secured, session=<hSAhb6sxuAB/AAAB> Apr 30 03:34:17 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:35:18 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3063, secured, session=<QerDcqsxugB/AAAB> Apr 30 03:35:18 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=91 out=872 Apr 30 03:35:29 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3066, secured, session=<X8ttc6sxvAB/AAAB> Apr 30 03:35:29 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=32 out=449 Apr 30 03:35:29 ip-172-31-28-46 dovecot: imap-login: Login: user=< beth(a)primelashdiva.info>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=3069, secured, session=<rpVwc6sxvgB/AAAB> Apr 30 03:35:29 ip-172-31-28-46 dovecot: imap(beth(a)primelashdiva.info): Disconnected: Logged out in=44 out=538 Apr 30 03:36:41 ip-172-31-28-46 postfix/postfix-script[3424]: stopping the Postfix mail system Apr 30 03:36:41 ip-172-31-28-46 postfix/master[2762]: terminating on signal 15 Apr 30 03:36:42 ip-172-31-28-46 postfix/postfix-script[3496]: starting the Postfix mail system Apr 30 03:36:42 ip-172-31-28-46 postfix/master[3497]: daemon started -- version 2.6.6, configuration /etc/postfix Apr 30 03:36:48 ip-172-31-28-46 dovecot: master: Warning: Killed with signal 15 (by pid=3509 uid=0 code=kill) Apr 30 03:36:48 ip-172-31-28-46 dovecot: imap: Server shutting down. in=586 out=1464 Apr 30 03:36:49 ip-172-31-28-46 dovecot: master: Dovecot v2.2.10 starting up for imap, pop3, lmtp (core dumps disabled) Apr 30 03:37:05 ip-172-31-28-46 dovecot: imap-login: Aborted login (no auth attempts in 6 secs): user=<>, rip=52.37.99.183, lip=172.31.28.46, session=<9D4ueasxaAA0JWO3> Apr 30 03:37:35 ip-172-31-28-46 dovecot: imap-login: Aborted login (no auth attempts in 8 secs): user=<>, rip=68.105.170.121, lip=172.31.28.46, session=<PN3weqsxwgBEaap5> Apr 30 03:41:46 ip-172-31-28-46 dovecot: imap-login: Aborted login (tried to use disallowed plaintext auth): user=<>, rip=68.105.170.121, lip=172.31.28.46, session=<xC7oiasxUwBEaap5> [ec2-user@ip-172-31-28-46 log]$ I'm not even sure where to go to start looking... Any pointers? Thanks Everyone!

1 0

segfault in imap "Warning: Timeout leak: 0x7fd584e8e050 (line 399)"
by Ralf Hildebrandt 29 Apr '16

29 Apr '16

Corresponding log entry: Apr 29 17:14:07 mproxy dovecot: imap(v******d): copy from INBOX: box=Trash, uid=512, msgid=, size=error Apr 29 17:14:07 mproxy dovecot: imap(v******d): expunge: box=INBOX, uid=3322, msgid=, size=22485 Apr 29 17:14:19 mproxy dovecot: imap(v******d): copy from INBOX: box=Trash, uid=513, msgid=, size=error Apr 29 17:14:19 mproxy dovecot: imap(v******d): expunge: box=INBOX, uid=3288, msgid=, size=60236 Apr 29 17:14:19 mproxy dovecot: imap(v******d): Warning: Timeout leak: 0x7fd584e8e050 (line 399) Apr 29 17:14:19 mproxy dovecot: imap(v******d): Connection closed (IDLE running for 0.043 + waiting input for 6654.979 secs, 2 B in + 10+10 B out, state=wait-input) in=7582 out=5928297 Apr 29 17:14:19 mproxy dovecot: imap(v******d): Fatal: master: service(imap): child 30554 killed with signal 11 (core dumped) Backtrace: Reading symbols from /usr/lib/dovecot/imap...Reading symbols from /usr/lib/debug/.build-id/5a/15dc6951744d026af424747e7b72a4fb550c6b.debug...done. done. [New LWP 30554] Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fd584b8daa7 in timeout_remove (_timeout=0x7fd5875b5048) at ioloop.c:307 #0 0x00007fd584b8daa7 in timeout_remove (_timeout=0x7fd5875b5048) at ioloop.c:307 timeout = 0x7fd5875b8720 ioloop = 0x0 #1 0x00007fd584e8df0b in imapc_client_mailbox_close ( _box=_box@entry=0x7fd5875b3b38) at imapc-client.c:362 box = 0x7fd5875b5030 connp = <optimized out> #2 0x00007fd584e8c3af in imapc_mailbox_close (box=0x7fd5875b3850) at imapc-storage.c:651 mbox = 0x7fd5875b3850 #3 0x00007fd584e411aa in mailbox_close (box=0x7fd5875b5048) at mail-storage.c:1242 No locals. #4 0x00007fd584e41233 in mailbox_free (_box=_box@entry=0x7fd5875a3f00) at mail-storage.c:1262 box = 0x7fd5875b3850 #5 0x00007fd585584f74 in client_default_destroy (client=0x7fd5875a3e60, reason=<optimized out>) at imap-client.c:367 cmd = 0x0 #6 0x00007fd584b8e06c in io_loop_call_io (io=0x7fd5875a18d0) at ioloop.c:564 ioloop = 0x7fd587563740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #7 0x00007fd584b8f4d1 in io_loop_handler_run_internal ( ioloop=ioloop@entry=0x7fd587563740) at ioloop-epoll.c:220 ctx = 0x7fd587565250 io = <optimized out> tv = {tv_sec = 4, tv_usec = 738842} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #8 0x00007fd584b8e0f5 in io_loop_handler_run ( ioloop=ioloop@entry=0x7fd587563740) at ioloop.c:612 No locals. #9 0x00007fd584b8e298 in io_loop_run (ioloop=0x7fd587563740) at ioloop.c:588 __FUNCTION__ = "io_loop_run" #10 0x00007fd584b23e63 in master_service_run (service=0x7fd5875635e0, callback=<optimized out>) at master-service.c:640 No locals. #11 0x00007fd585577b32 in main (argc=1, argv=0x7fd587563390) at main.c:460 set_roots = {0x7fd5857a1700 <imap_setting_parser_info>, 0x7fd585340400 <lda_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x7fd58755b048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x7fd5855919d0 <login_client_connected>, failure_callback = 0x7fd5855912e0 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 auth_socket_path = 0x7fd58559a34e "auth-master" c = <optimized out> -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

1 0

Password database extra fields and SQL
by Dave 29 Apr '16

29 Apr '16

Hi everyone, first post to the list, be gentle with me! Perhaps I'm missing something here, but it appears to me that many password database extra fields currently aren't much use inside SQL queries? All boolean fields like nologin/nodelay/nopassword are set if the column is present in the returned query, regardless of value (including NULL) For example, say you have a query like: password_query = SELECT hash AS password, NULLIF(active = 1, 'y') AS nologin FROM users WHERE name = '%u' Then nologin will always be set for this account, there's no realistic way to toggle the flag. Has anyone come across any workarounds for this problem that don't sacrifice efficiency by performing multiple lookups? I was considering what would happen if dovecot treated NULL fields as not present, but that immediately conflicts with advice to set password to NULL to satisfy the field requirement on nopassword. Any thoughts? -- Dave

3 3

Backtrace:dovecot/imap
by Ralf Hildebrandt 29 Apr '16

29 Apr '16

Config: # 2.2.devel (2dc8e2d): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (850d80b) # OS: Linux 3.13.0-77-generic x86_64 Ubuntu 16.04 LTS auth_mechanisms = plain login default_vsz_limit = 1 G imapc_host = email.charite.de imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no listen = *,:: mail_gid = imapproxy mail_home = /home/imapproxy/%u mail_location = imapc:~/imapc mail_plugins = mail_log notify mail_uid = imapproxy passdb { args = host=email.charite.de port=993 ssl=imaps default_fields = userdb_imapc_user=%u userdb_imapc_password=%w userdb_imapc_host=email.charite.de userdb_imapc_ssl=imaps userdb_imapc_port=993 driver = imap } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap service auth { inet_listener { address = 127.0.0.1 port = 12345 } } ssl = required ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_cert = </etc/dovecot/dovecot.pem ssl_cipher_list = DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = prefetch } verbose_proctitle = yes Reading symbols from /usr/lib/dovecot/imap...Reading symbols from /usr/lib/debug/.build-id/5a/15dc6951744d026af424747e7b72a4fb550c6b.debug...done. done. [New LWP 21869] Core was generated by `dovecot/imap'. Program terminated with signal SIGSEGV, Segmentation fault. #0 buffer_delete (_buf=0x0, pos=0, size=0) at buffer.c:213 #0 buffer_delete (_buf=0x0, pos=0, size=0) at buffer.c:213 buf = 0x0 end_size = <optimized out> #1 0x00007f5729a7507e in array_delete_i (count=1, idx=125, array=0x7f572c12bbb8) at ../../../../src/lib/array.h:200 No locals. #2 imapc_untagged_expunge (reply=<optimized out>, mbox=0x7f572c12b840) at imapc-mailbox.c:473 msgmap = 0x7f572c146ed0 lseq = 739349904 uid = 51497 rseq = 126 #3 0x00007f5729a77632 in imapc_storage_client_untagged_cb ( reply=0x7ffdc857e400, context=0x7f572c0f7080) at imapc-storage.c:204 mcb__foreach_end = 0x7f572c12bf98 client = 0x7f572c0f7080 mbox = 0x7f572c12b840 cb = <optimized out> mcb = 0x7f572c12bf78 #4 0x00007f5729a7d90a in imapc_connection_input_untagged ( conn=conn@entry=0x7f572c119590) at imapc-connection.c:1144 imap_args = 0x7f572c11db38 data = <optimized out> size = 140012378250296 name = 0x7f572c11dc38 "EXPUNGE" value = <optimized out> parser = 0x7f572c119710 reply = {name = 0x7f572c11dc38 "EXPUNGE", num = 126, args = 0x7f572c11db38, file_args = 0x7f572c11b4c0, file_args_count = 0, resp_text_key = 0x0, resp_text_value = 0x0, untagged_box_context = 0x7f572c12b840} ret = <optimized out> #5 0x00007f5729a7f7d9 in imapc_connection_input_one (conn=0x7f572c119590) at imapc-connection.c:1398 tag = 0x7f572c11dc28 "*" ret = -1 #6 imapc_connection_input_pending (conn=0x7f572c119590) at imapc-connection.c:1766 _data_stack_cur_id = 6 ret = 1 conn = 0x7f572c119590 #7 0x00007f5729a7f82a in imapc_connection_input (conn=0x7f572c119590) at imapc-connection.c:1438 errstr = <optimized out> str = <optimized out> ret = <optimized out> #8 0x00007f572977a05c in io_loop_call_io (io=0x7f572c132740) at ioloop.c:564 ioloop = 0x7f572c136c10 t_id = 5 __FUNCTION__ = "io_loop_call_io" #9 0x00007f572977b4c1 in io_loop_handler_run_internal ( ioloop=ioloop@entry=0x7f572c136c10) at ioloop-epoll.c:220 ctx = 0x7f572c138dd0 io = <optimized out> tv = {tv_sec = 299, tv_usec = 999778} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #10 0x00007f572977a0e5 in io_loop_handler_run ( ioloop=ioloop@entry=0x7f572c136c10) at ioloop.c:612 No locals. #11 0x00007f572977a288 in io_loop_run (ioloop=0x7f572c136c10) at ioloop.c:588 __FUNCTION__ = "io_loop_run" #12 0x00007f5729a7ab7a in imapc_client_run_pre (client=0x7f572c0f7250, client=0x7f572c0f7250) at imapc-client.c:173 connp = 0x7f572c0f73e8 prev_ioloop = 0x7f572c0db740 #13 imapc_client_run (client=0x7f572c0f7250) at imapc-client.c:192 No locals. #14 0x00007f5729a785e0 in imapc_mailbox_run_nofetch ( mbox=mbox@entry=0x7f572c12b840) at imapc-storage.c:143 No locals. #15 0x00007f5729a78612 in imapc_mailbox_run (mbox=mbox@entry=0x7f572c12b840) at imapc-storage.c:137 No locals. #16 0x00007f5729a7a178 in imapc_sync_index (ctx=0x7f572c132140) at imapc-sync.c:405 mbox = 0x7f572c12b840 sync_rec = {uid1 = 51497, uid2 = 51497, type = MAIL_INDEX_SYNC_TYPE_EXPUNGE, add_flags = 4 '\004', remove_flags = 0 '\000', keyword_idx = 6315, guid_128 = "^kK\r2U\277\357\225`\030\220\257\330\a\t"} seq1 = 126 seq2 = 126 #17 imapc_sync_begin (force=<optimized out>, ctx_r=<synthetic pointer>, mbox=0x7f572c12b840) at imapc-sync.c:481 ctx = <optimized out> sync_flags = <optimized out> ret = <optimized out> #18 imapc_sync (mbox=0x7f572c12b840) at imapc-sync.c:537 sync_ctx = <optimized out> force = <optimized out> #19 imapc_mailbox_sync_init (box=0x7f572c12b840, flags=MAILBOX_SYNC_FLAG_EXPUNGE) at imapc-sync.c:590 mbox = 0x7f572c12b840 list = <optimized out> changes = false ret = <optimized out> #20 0x00007f5729a2ea7b in mailbox_sync_init (box=box@entry=0x7f572c12b840, flags=flags@entry=MAILBOX_SYNC_FLAG_EXPUNGE) at mail-storage.c:1672 _data_stack_cur_id = 4 ctx = <optimized out> #21 0x00007f572a17e102 in imap_sync_init (client=client@entry=0x7f572c11be50, box=<optimized out>, imap_flags=IMAP_SYNC_FLAG_SAFE, flags=MAILBOX_SYNC_FLAG_EXPUNGE) at imap-sync.c:229 __FUNCTION__ = "imap_sync_init" #22 0x00007f572a17ef97 in cmd_sync_client (sync_cmd=0x7f572c127a90) at imap-sync.c:737 ctx = <optimized out> flags = <optimized out> client = 0x7f572c11be50 imap_flags = <optimized out> no_newmail = <optimized out> #23 cmd_sync_delayed_real (client=0x7f572c11be50) at imap-sync.c:856 cmd = <optimized out> first_expunge = <optimized out> first_nonexpunge = <optimized out> #24 cmd_sync_delayed (client=client@entry=0x7f572c11be50) at imap-sync.c:864 _data_stack_cur_id = 3 #25 0x00007f572a1726d8 in client_handle_input (client=0x7f572c11be50) at imap-client.c:1088 remove_io = <optimized out> handled_commands = <optimized out> client = 0x7f572c11be50 #26 0x00007f572a172b65 in client_input (client=0x7f572c11be50) at imap-client.c:1119 cmd = 0x27284 output = 0x7f572c11d080 bytes = 153 __FUNCTION__ = "client_input" #27 0x00007f572977a05c in io_loop_call_io (io=0x7f572c1198c0) at ioloop.c:564 ioloop = 0x7f572c0db740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #28 0x00007f572977b4c1 in io_loop_handler_run_internal ( ioloop=ioloop@entry=0x7f572c0db740) at ioloop-epoll.c:220 ctx = 0x7f572c0dd250 io = <optimized out> tv = {tv_sec = 1739, tv_usec = 992115} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #29 0x00007f572977a0e5 in io_loop_handler_run ( ioloop=ioloop@entry=0x7f572c0db740) at ioloop.c:612 No locals. #30 0x00007f572977a288 in io_loop_run (ioloop=0x7f572c0db740) at ioloop.c:588 __FUNCTION__ = "io_loop_run" #31 0x00007f572970fe63 in master_service_run (service=0x7f572c0db5e0, callback=<optimized out>) at master-service.c:640 No locals. #32 0x00007f572a165b32 in main (argc=1, argv=0x7f572c0db390) at main.c:460 set_roots = {0x7f572a38f700 <imap_setting_parser_info>, 0x7f5729f2e400 <lda_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x7f572c0d3048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x7f572a17f9d0 <login_client_connected>, failure_callback = 0x7f572a17f2e0 <login_client_failed>, request_auth_token = 1} service_flags = <optimized out> storage_service_flags = <optimized out> username = 0x0 auth_socket_path = 0x7f572a18834e "auth-master" c = <optimized out> ----- End forwarded message ----- -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 2

Re: WP8/Windows 10 mail app can't login, tries double auth
by Joseph Tam 29 Apr '16

29 Apr '16

Attila Nagy writes: > Are there anybody who could make WP8 (and W10 desktop clients it seems) > devices working with Dovecot's POP3 server? > > The conversation looks like this: > S +OK ready > C CAPA > S +OK > S CAPA > S TOP > S UIDL > S RESP-CODES > S PIPELINING > S AUTH-RESP-CODE > S USER > S SASL PLAIN > S . > C AUTH > S +OK > S PLAIN > S . > C AUTH PLAIN > S + > C <base64 auth string) > S +OK[space] > C USER username > S -ERR unimplemented > > First I thought the extra space after that OK causes this, but removing > it changed nothing. > > So these devices try to log in with AUTH PLAIN, then even after a > successful login they want to log in again with USER, which gets rejected. I dimly remember some Windows clients preferring either "LOGIN" or "PLAIN" style mechanism. Have you tried allowing "LOGIN" style authentication? auth_mechanisms = plain login Joseph Tam <jtam.home(a)gmail.com>

2 1

Doveadm Replicator problem with PAM passdb
by Adam Joesbury 28 Apr '16

28 Apr '16

Hi Everyone, We are running two CentOS 7.2 servers with Sendmail 8.14.7 V10 and Dovecot 2.2.10 installed on both and are trying to configure Master-Master Replication using doveadm replicator. We are using system users with PAM authentication but are receiving the following fatal error when dsync tries to run: doveadm(user): Fatal: /var/run/dovecot/auth-userdb: Configured passdbs don't support crentials lookups (to see if user is proxied, because doveadm_port is set). Please could someone confirm whether it is possible to configure replication using PAM passdb as the above error seems to suggest it isn't but we have come across various people online who seem to have it working. I don't know whether we need to create a master user or whether we need to create a separate password file with a directory of all of our user's passwords? We do have all the user passwords as they are only internal accounts that we are servicing. Thanks in advance Output of dovecot -n: # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.13.1.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_mechanisms = plain login auth_socket_path = /var/run/dovecot/auth-userdb doveadm_password = secret doveadm_port = 12345 login_greeting = POP3-IMAP server ready. mail_location = maildir:~/Maildir mail_plugins = " notify replication" mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox "Deleted Items" { auto = subscribe special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox "Junk E-mail" { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } prefix = } passdb { args = session=yes setcred=yes failure_show_msg=yes dovecot driver = pam } plugin { mail_replica = tcp:VMAILSERVER1:12345 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener auth-userdb { mode = 0777 } } service doveadm { inet_listener { port = 12345 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_ca = </etc/pki/tls/certs/chain.crt ssl_cert = </etc/pki/tls/certs/ca.crt ssl_key = </etc/pki/dovecot/private/dovecot.pem ssl_verify_client_cert = yes userdb { driver = passwd } verbose_ssl = yes

1 0

managesieve proxying not working
by Hawk Chen 28 Apr '16

28 Apr '16

Hi, I'm setting up the directors for proxying pop3/imap/lmtp/sieve. pop3/imap/lmtp proxying work fine, but sieve not working. The error messages in maillog look not using proxying but local passdb. Error message: Apr 03 12:09:25 managesieve-login: Info: Aborted login (no auth attempts in 0 secs): user=<>, rip=10.1.1.4, lip=10.1.1.201, session=<+SIcx4wvRQAKAQEE> sql in /etc/dovecot/dovecot-sql.conf.ext: password_query = SELECT NULL as password, host, 'Y' as nopassword, 'Y' as proxy FROM mailbox WHERE username = '%u' AND active='1' doveconf -n output is as follows, # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.10.1.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) director_mail_servers = 10.1.4.5 10.1.4.6 director_servers = 10.1.1.1 10.1.1.2 lmtp_proxy = yes log_path = /var/log/dovecot.log login_greeting = DNT Mail Server managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director service_count = 0 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { executable = managesieve-login director service_count = 0 } service pop3-login { executable = pop3-login director service_count = 0 } ssl = required ssl_cert = </etc/postfix/itsnow.crt ssl_key = </etc/postfix/itsnow.key userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { driver = passwd } protocol lmtp { auth_socket_path = director-userdb } Regards, Hawk

3 6

WP8/Windows 10 mail app can't login, tries double auth
by Nagy, Attila 27 Apr '16

27 Apr '16

Hi, Are there anybody who could make WP8 (and W10 desktop clients it seems) devices working with Dovecot's POP3 server? The conversation looks like this: S +OK ready C CAPA S +OK S CAPA S TOP S UIDL S RESP-CODES S PIPELINING S AUTH-RESP-CODE S USER S SASL PLAIN S . C AUTH S +OK S PLAIN S . C AUTH PLAIN S + C <base64 auth string) S +OK[space] C USER username S -ERR unimplemented First I thought the extra space after that OK causes this, but removing it changed nothing. So these devices try to log in with AUTH PLAIN, then even after a successful login they want to log in again with USER, which gets rejected. The only solution here seems to be giving back -ERR to the client's AUTH command, which makes it try USER instead. I'm not aware of any configuration options which makes this possible. Any other ideas? Thanks,

1 1

Creating Dovecot Master user throws "Username character disallowed by auth_username_chars : 0x2a " error
by David Okwii 27 Apr '16

27 Apr '16

Hello, Am trying to create a master user on dovecot. However, it throws dovecot: auth: plain(?,127.0.0.1): Username character disallowed by auth_username_chars: 0x2a (username: loginuser*master) ". #telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN 1 login loginuser*master mypassword 1 NO [AUTHENTICATIONFAILED] Authentication failed. # log output dovecot: auth: plain(?,127.0.0.1): Username character disallowed by auth_username_chars: 0x64 (username: master) # cat passwd.master master:{SHA}LORtG60Uqg2bPSlOB8PW2cLI0TE= #And here's the output of my dovecot -n # 2.0.16: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-RELEASE amd64 auth_master_user_separator = * disable_plaintext_auth = no mail_location = maildir:~/Maildir namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } passdb { args = /usr/local/etc/dovecot/passwd.master driver = passwd-file master = yes } protocols = imap pop3 service auth { client_limit = 6000 } service imap { process_limit = 2048 vsz_limit = 1256 M } service pop3 { process_limit = 2048 } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } protocol pop3 { pop3_uidl_format = UID%u-%v } I don't know what am doing wrong. Any help would be welcome. Thanks -- Thanks & regards, David Okwii, Mobile(default): +256-791-040-262 Christ in me the Hope of Glory(Col.1:27)

1 0

Option to not add "Received" header ?
by Florent B 27 Apr '16

27 Apr '16

Hi everyone, I use Dovecot in lmtp mode to receive mails. I would like an option to tell Dovecot to not add a "Reveived" header on each server (I use a director, so Director also adds this header). Is it possible to do this ? Or could it be a future feature ? Thank you. Florent

5 6

Crash: setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL)
by Heiko Schlittermann 27 Apr '16

27 Apr '16

Hi, Using 2.2.9 (ubuntu 14.04 LTS) and sending the following command, the server crashes when I try to delete an annotation: … login … C: 2 setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" NIL) Apr 27 09:29:16 backend1 dovecot: imap-login: Login: user=<heiko>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=6651, secured Apr 27 09:29:16 backend1 dovecot: imap(heiko): Fatal: master: service(imap): child 6651 killed with signal 11 (core dumped) Sending a real value it works: … login … C: 2 setannotation Trash "/vendor/cmu/cyrus-imapd/expire" ("value.shared" "27") S: 2 OK Completed. Is this a known bug that is fixed in later releases? Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

3 6

apt pinning specific dovecot version
by Regan Jelčić 27 Apr '16

27 Apr '16

I currently have the dovecot-core package from wheezy-backports pinned on one of my servers to version '2.2.9', which has been working great. I now want to upgrade that to the newest version under wheezy-backports which is: dovecot-core (1:2.2.13-11~bpo70+1) but I can't figure out how to get do it. I've tried a few different formats of the name but apt-get update then apt-get dost-upgrade doesn't pick up the new version - it ignores it when trying to do an update. This is what I've got in my apt preferences and pin files... /etc/apt/preferences Explanation: Stop ALL wheezy-backports updating system. Package: * Pin: release a=wheezy-backports,n=wheezy-backports Pin-Priority: 100 /etc/apt/preferences.d/dovecot.pref Explanation: Promote wheezy-backports version of Dovecot only Package: dovecot-core /2\.2\.9/ Pin: release a=wheezy-backports Pin-Priority: 500 Can anyone advise how I get it to pull the newer version?? Thanks,

3 2

Re: dovecot Digest, Vol 156, Issue 44
by Ron Cleven 27 Apr '16

27 Apr '16

> On 26 Apr 2016, at 21:52, Hauke Fath<hf(a)spg.tu-darmstadt.de> wrote: >> > >> >On Tue, 26 Apr 2016 18:20:00 +0300, Timo Sirainen wrote: >>> >>This should be a good release.:) >> > >> >Would this release address the "reappearing emails" issue that 2.2.23 >> >introduced? > I guess you're talking about replication. I'm not aware of any specific change in v2.2.23 that could have even potentially caused it. I also don't know how I could reproduce it. Can you use git bisect to find out the specific change that broke it? > > The only thing I remember even remotely related to this ishttps://github.com/dovecot/core/commit/950a6e61d6c2dac961ce031bdd8b2895bc… but that was supposed to only fix things and I can't think of how it might break things. > > One possibility is that nothing broke this in v2.2.23. I've heard about the same issue for a long time. Maybe you just suddenly started having this problem now and it would have happened even with the old Dovecot version. I was (perhaps one of) the people who reported "reappearing emails" with 2.2.10 in the context of Maildir with replication under CentOS 7. I had spent a great deal of time making it reproducible, difficult because there was a timing element. In that context, 2.2.23 absolutely fixed the problem which was absolutely related to a timing issue with replication. If I remember right, this person was reporting a similar-sounding problem, but it did not involve replication and was not under CentOS 7. Creating a script that reproduces the problem is an important first step. Good luck.

1 0

Released Pigeonhole v0.4.14 for Dovecot v2.2.24.
by Stephan Bosch 27 Apr '16

27 Apr '16

Hello Dovecot users, The most important feature that this new release adds is the IMAPSIEVE capability, which allows executing Sieve scripts at IMAP events. It also adds the ability to obtain trace logs from Sieve execution at actual delivery (or from IMAP), rather than only using the sieve-test command line tool. This release also fixes a bug in the Sieve extprograms plugin that has been bothering a few people for a while now. Changelog v0.4.14: * The address test now allows specifying the X-Original-To header. + Implemented the Sieve imapsieve extension and its IMAP counterpart (RFC 6785) as a set of plugins. This allows running Sieve scripts at IMAP activity, rather than at delivery. There are also facilities for the familiar sieve_before/sieve_after administrator scripts. A user script is defined for a mailbox using an IMAP METADATA entry, whereas administrator scripts are configured using mailbox matching rules defined in the plugin settings. + Adjusted the Sieve ihave extension to allow capability tests to be performed at runtime. This way, scripts can be written that work both at delivery and from IMAP. + Implemented support for runtime trace debugging. This means that detailed information about which commands, actions and tests are performed is written to a file. That file is created in the configured directory, but only if that directory exists. This way, a particular user can be easily singled out for debugging. This works much like the Dovecot rawlog facility. The trace output is identical to what is produced using sieve-test with its "-t" command line option. + Added a "sieve_user_email" setting that configures the user's primary email address. This is mainly useful to have a user email address available in IMAP, where envelope data is unavailable. + Implemented the dovecot-specific "vnd.dovecot.report" extension. This allows sending report messages in the Message Abuse Reporting Format (RFC 5965). - extprograms plugin: Fixed epoll() panic caused by closing the output FD before the output stream. - Made sure that the local part of a mail address is encoded properly using quoted string syntax when it is not a dot-atom. The release is available as follows: http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.14.ta… http://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.14.ta… Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

help with sieve
by dovecot＠paulkoppen.com 27 Apr '16

27 Apr '16

Dear Dovecot / Pigeonhole community, I have a very specific issue, but trying to solve this for a full day, I am now getting so bold from pulling my hairs out, I thought it was time I asked for help. I hope this is a good place for that. At my hosting provider, who have been extremely helpful by the way but are not specifically skilled in Sieve, I have a catch-all address set up: *(a)domain.org (where * is literal), with a sieve script to control how messages are forwarded. Currently my rules are of the form: if address :localpart :is ["To","Cc","Bcc"] ["name1", "name2", ...] { ... } This works most of the time, but sometimes the messages are not directly addressed to me and so they slip through the filters. I figured that using envelope would solve this, so I require envelope and then do: if envelope :localpart :is "To" ["name1", "name2", ...] { ... } But this fails. After endlessly trying different combinations I figured out that the reason for failure is that the envelope believes the "To" is actually "*(a)domain.org", so it is never going to match any of the names. However, the following test succeeds: if header :contains "Envelope-To" "name1@" { ... } From this I deduce that a previous script has already done the conversion from name1 to *, and at the point where my sieve script is run the envelope picks up the *(a)domain.org address, leaving the Envelope-To header for what it is. But I am new to this. Is that likely to be the case? Is it a common sieve set-up? And most importantly, is there a better way around the issue than testing header :contains? With kind regards, Paul

2 1

v2.2.24 released
by Timo Sirainen 26 Apr '16

26 Apr '16

http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.24.tar.gz.sig This should be a good release. :) * doveconf now warns if it sees a global setting being changed when the same setting was already set inside some filters. (A common mistake has been adding more plugins to a global mail_plugins setting after it was already set inside protocol { .. }, which caused the global setting to be ignored for that protocol.) * LMTP proxy: Increased default timeout 30s -> 125s. This makes it less likely to reach the timeout and cause duplicate deliveries. * LMTP and indexer now append ":suffix" to session IDs to make it unique for the specific user's delivery. (Fixes duplicate session ID warnings in stats process.) + Added dict-ldap for performing read-only LDAP dict lookups. + lazy-expunge: All mails can be saved to a single specified mailbox. + mailbox { autoexpunge } supports now wildcards in mailbox names. + doveadm HTTP API: Added support for proxy commands + imapc: Reconnect when getting disconnected in non-selected state. + imapc: Added imapc_features=modseq to access MODSEQs/HIGHESTMODSEQ. This is especially useful for incremental dsync. + doveadm auth/user: Auth lookup performs debug logging if -o auth_debug=yes is given to doveadm. + Added passdb/userdb { auth_verbose=yes|no } setting. + Cassandra: Added user, password, num_threads, connect_timeout and request_timeout settings. + doveadm user -e <value>: Print <value> with %variables expanded. - Huge header lines could have caused Dovecot to use too much memory (depending on config and used IMAP commands). (Typically this would result in only the single user's process dying with out of memory due to reaching service { vsz_limit } - not a global DoS). - dsync: Detect and handle invalid/stale -s state string better. - dsync: Fixed crash caused by specific mailbox renames - auth: Auth cache is now disabled passwd-file. It was unnecessary and it broke %variables in extra fields. - fts-tika: Don't crash if it returns 500 error - dict-redis: Fixed timeout handling - SEARCH INTHREAD was crashing - stats: Only a single fifo_listeners was supported, making it impossible to use both auth_stats=yes and mail stats plugin. - SSL errors were logged in separate "Stacked error" log lines instead of as part of the disconnection reason. - MIME body parser didn't handle properly when a child MIME part's --boundary had the same prefix as the parent.

2 2

Subject: Re: v2.2.24 released
by Joseph Tam 26 Apr '16

26 Apr '16

Timo Sirainen wrote: > - auth: Auth cache is now disabled passwd-file. It was unnecessary and > it broke %variables in extra fields. So settings like auth_cache_size = 65536 auth_cache_ttl = 86400 auth_cache_negative_ttl = 600 are ignored/useless, and passwd-file auth lookups always results in file read operation? Joseph Tam <jtam.home(a)gmail.com>

2 2

Solr with shared mailboxes
by Ricardo Branco 26 Apr '16

26 Apr '16

We have multiple logins assigned to single mailboxes, so we can give one login to different devices. Does this cause a problem with mailbox guids in solr or is the ID stored within the indexes and not related to username.

2 3

doveadm search when using solr problems
by Ricardo Branco 26 Apr '16

26 Apr '16

Is there a way when using doveadm to search a users mailbox to disable using solr plugin (without changing config file). We have found that solr does not work well with certain search types and reverting to non solr searching works much better.

2 3

Possible to use Doveadm for a time range deletion
by Kenneth Ulrich 26 Apr '16

26 Apr '16

Hello All, I was wondering if it s possible to remove emails between a time range. For example, End Users have emails dating back to Aug 2000. He would like all emails deleted between the time stamp of 07/2014 to 07/2015 yet keep any emails outside of this area. I've ran into some similar examples, but nothing definite.

2 1

Strange search behavior
by Cornelius Charlie 26 Apr '16

26 Apr '16

Hello, I experienced a strange behavior in the way dovecot is performing searches, I only experienced this exact issue with the flag "seen". If I perform this command: UID SORT (SIZE) UTF-8 FLAGGED SEEN Dovecot return every seen messages even if the message is not "flagged'. This is only happening when there is no unseen messages in the mailbox, if there is at least one, this is working properly. Any though ? Thanks.

3 4