- dovecot - dovecot.org

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

push-notification plugin and imap-metadata permissions
by Giovanni S. Fois 26 Apr '16

26 Apr '16

Ultra short version: Why cant I set the following mailbox metadata key? /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify Let me explain the context: I'm using the Dovecot version 2.23.1, but the same happens for the 2.2.22 The push-notification plugin is supposed to send out a notification whenever a mailbox get a new email message. In order to tell if a mailbox is enabled to send out the notification, the plugin looks out for the following mailbox metadata key: /private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify If the key is set then everything is OK and the notification is sent, otherwise the action is skipped. If I try to setup the metadata key by hand (telnet as the user over the imap port): setmetadata INBOX (/private/vendor/vendor.dovecot/pvt/server/vendor/vendor.dovecot/http-notify "user=myuser(a)mydomain.com") I get the error message: "Internal mailbox attributes cannot be accessed" Digging in the Dovecot 2.2.22 sources i found that: This string is from lib-imap-storage/imap-metadata.c - line 36 - Dovecot 2.2.22 The message is triggered by the following condition - same file - line 125 - Dovecot 2.2.22 if (strncmp(*key_r, MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT, strlen(MAILBOX_ATTRIBUTE_PREFIX_DOVECOT_PVT)) == 0) { So the path pvt/server appears to be forbidden. But, in the file lib-storage/mailbox-attribute.h we can read the following comment: /* User can get/set all non-pvt/ attributes and also pvt/server/ (but not pvt/server/pvt/) attributes. */ And, after said comment there is the definition of the macro MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key) which has the same basic function of the condition in imap-metadata.c , but in this case the same imap key is seen as accessible. Now my questions: Can we use a negated version of MAILBOX_ATTRIBUTE_KEY_IS_USER_ACCESSIBLE(key) in imap-metadata? How can the push-notification plugin work out-of-the-box without changes and recompilation? Thank you for your valuable time and forgive me if I'm posing a dumb question. Best wishes, Giovanni S. Fois

4 6

Kernel panic in dovecot-ee-lmtp on Debian 8
by Tobi 26 Apr '16

26 Apr '16

Hi list I just realized that that I don not receive all mails in my mailbox (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers (running postfix) the queue fills up with mails that cannot be delivered via lmtp to my backend servers. The error message on the frontend is "lost connection with backend while sending data" When I checked the logs on the backend server I found upon every delivery attempt kernel panics Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Panic: epoll_ctl(del, 18) failed: Bad file descriptor Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x85dee) [0x7faa19225dee] -> /usr/lib/dovecot/libdovecot.so.0(+0x85edc) [0x7faa19225edc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7faa191ca5be] -> /usr/lib/dovecot/libdovecot.so.0(+0x9afc1) [0x7faa1923afc1] -> /usr/lib/dovecot/libdovecot.so.0(+0x994af) [0x7faa192394af] -> /usr/lib/dovecot/libdovecot.so.0(+0xa5eda) [0x7faa19245eda] -> /usr/lib/dovecot/libdovecot.so.0(+0xa4566) [0x7faa19244566] -> /usr/lib/dovecot/libdovecot.so.0(o_stream_destroy+0xe) [0x7faa192446ee] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x7e44b) [0x7faa17d3a44b] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x7ea14) [0x7faa17d3aa14] -> /usr/lib/dovecot/libdovecot.so.0(+0xa6d88) [0x7faa19246d88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7faa19239c6c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7faa1923b0d1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7faa19239cf5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7faa19239e98] -> /usr/lib/dovecot/libdovecot-sieve.so.0(program_client_run+0xe8) [0x7faa17d3b308] -> /usr/lib/dovecot/modules/sieve/lib90_sieve_extprograms_plugin.so(+0x45b8) [0x7faa15d855b8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_continue+0x7c) [0x7faa17cfa2ac] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_interpreter_run+0x2b) [0x7faa17cfa4cb] -> /usr/lib/dovecot/libdovecot-sieve.so.0(+0x519e0) [0x7faa17d0d9e0] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x47) [0x7faa17d0e567] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3b6b) [0x7faa17f73b6b] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7faa197e5849] -> dovecot/lmtp() [0x4064b3] -> dovecot/lmtp() [0x406cb4] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7faa19239c6c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7faa1923b0d1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7faa19239cf5] Apr 25 12:33:36 mbox1 dovecot: lmtp(REDACTED): Fatal: master: service(lmtp): child 32081 killed with signal 6 (core dumps disabled) the weird thing is that this is not concerning all incoming mails. From time to time the frontends can deliver messages to my backends. I just tested it with a mail from work. It arrived via a frontend that has other mails in queue that could not be delivered so far. Does anyone have an idea where I could look for the root cause of this panic messages? Thanks a lot tobi

4 5

doveadm-server segfaults when searching or expunging with the -A flag
by Burak Seydioglu 26 Apr '16

26 Apr '16

Hello, I have an openldap backend that contains a large number of users and serves passdb and userdb requests. I was trying to work around the pop3 deletion issue that I had reported earlier (http://www.dovecot.org/list/dovecot/2016-April/103973.html) with the pop3_deleted_flag setting so I updated my configuration and created some background jobs to expunge deleted emails. However, doveadm-server segfaults when running search or expunge commands with the -A flag: doveadm search mailbox INBOX KEYWORD '$Pop3Deleted' -A doveadm expunge mailbox INBOX KEYWORD '$Pop3Deleted' -A ###################################### gdb /usr/libexec/dovecot/doveadm-server /var/crash/core-doveadm-server-11-0-0-2589-1461628665 #0 o_stream_cork (stream=0x0) at ostream.c:141 #1 0x0000000000430193 in server_connection_output (conn=0xfe10e0) at server-connection.c:126 #2 0x00007fcde9fc80c7 in plain_flush_callback (sstream=0xfdacf0) at ostream-openssl.c:180 #3 0x00007fcdeb6f9929 in stream_send_io (fstream=0xfe65e0) at ostream-file.c:482 #4 0x00007fcdeb6ebceb in io_loop_call_io (io=0xfdb110) at ioloop.c:564 #5 0x00007fcdeb6ed2e7 in io_loop_handler_run_internal (ioloop=<value optimized out>) at ioloop-epoll.c:220 #6 0x00007fcdeb6ebd95 in io_loop_handler_run (ioloop=0xfdf4b0) at ioloop.c:612 #7 0x00007fcdeb6ebf38 in io_loop_run (ioloop=0xfdf4b0) at ioloop.c:588 #8 0x000000000041f542 in dsync_connect_tcp (ctx=0xfc7d70, mail_set=<value optimized out>, target=<value optimized out>, ssl=true, error_r=0x7ffde6127020) at doveadm-dsync.c:806 #9 0x000000000041ff95 in parse_location (_ctx=0xfc7d70, service_user=<value optimized out>, error_r=0x7ffde6127020) at doveadm-dsync.c:837 #10 cmd_dsync_prerun (_ctx=0xfc7d70, service_user=<value optimized out>, error_r=0x7ffde6127020) at doveadm-dsync.c:903 #11 0x00000000004205f2 in doveadm_mail_next_user (ctx=0xfc7d70, cctx=<value optimized out>, error_r=0x7ffde6127020) at doveadm-mail.c:383 #12 0x000000000043151f in doveadm_mail_cmd_server_run (conn=0xfc3950) at client-connection.c:183 #13 doveadm_cmd_handle (conn=0xfc3950) at client-connection.c:266 #14 client_handle_command (conn=0xfc3950) at client-connection.c:330 #15 client_connection_input (conn=0xfc3950) at client-connection.c:444 #16 0x00007fcdeb6ebceb in io_loop_call_io (io=0xfc34f0) at ioloop.c:564 #17 0x00007fcdeb6ed2e7 in io_loop_handler_run_internal (ioloop=<value optimized out>) at ioloop-epoll.c:220 #18 0x00007fcdeb6ebd95 in io_loop_handler_run (ioloop=0xf90780) at ioloop.c:612 #19 0x00007fcdeb6ebf38 in io_loop_run (ioloop=0xf90780) at ioloop.c:588 #20 0x00007fcdeb684753 in master_service_run (service=0xf90620, callback=<value optimized out>) at master-service.c:640 #21 0x0000000000433897 in main (argc=1, argv=0xf903a0) at main.c:126 ###################################### Dovecot version ###################################### dovecot --version 2.2.23 (806d709) ###################################### doveconf -n ###################################### # 2.2.23 (806d709): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-573.22.1.el6.x86_64 x86_64 CentOS release 6.7 (Final) auth_debug = yes auth_mechanisms = plain login auth_verbose = yes base_dir = /var/run/dovecot/ disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it first_valid_uid = 89 last_valid_uid = 89 login_greeting = Dovecot ready on mda01.dc1.domain.com. login_trusted_networks = 127.0.0.1 mail_debug = yes mail_gid = 89 mail_plugins = " notify replication" mail_uid = 89 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/conf.d/dovecot-ldap-passdb.conf.ext driver = ldap } plugin { mail_replica = tcps:mdareplica:12345 } pop3_deleted_flag = $POP3Deleted protocols = pop3 lmtp replication_full_sync_interval = 3 hours replication_max_conns = 20 service aggregator { fifo_listener replication-notify-fifo { group = postfix mode = 0640 user = postfix } unix_listener replication-notify { group = postfix mode = 0640 user = postfix } } service auth { unix_listener auth { mode = 0660 } } service doveadm { inet_listener { port = 12345 ssl = yes } } service lmtp { process_min_avail = 10 unix_listener lmtp { group = postfix mode = 0640 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = postfix mode = 0640 user = postfix } } ssl_cert = </etc/pki/tls/certs/dovecot.crt ssl_client_ca_file = /etc/pki/tls/CA/dovecot.bundle ssl_key = </etc/pki/tls/private/dovecot.key ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = " notify replication" } ###################################### LDAP configuration ###################################### cat /etc/dovecot/conf.d/dovecot-ldap-userdb.conf.ext hosts = localhost dn = cn=dovecot,dc=csi,dc=domain,dc=com dnpass = xxx ldap_version = 3 base = ou=instances,dc=csi,dc=domain,dc=com deref = never scope = subtree user_attrs = \ =home=/glide/mail/spool/%{ldap:uid}, \ =mail=maildir:/glide/mail/spool/%{ldap:maildrop} user_filter = (&(objectClass=mailUser)(uid=%n)) iterate_attrs = uid=user iterate_filter = (objectClass=mailUser) cat /etc/dovecot/conf.d/dovecot-ldap-passdb.conf.ext hosts = localhost dn = cn=dovecot,dc=csi,dc=domain,dc=com dnpass = xxx ldap_version = 3 base = ou=instances,dc=csi,dc=domain,dc=com deref = never scope = subtree pass_attrs = uid=user,userPassword=password, \ =userdb_home=/glide/mail/spool/%{ldap:uid}, \ =userdb_mail=maildir:/glide/mail/spool/%{ldap:maildrop} pass_filter = (&(objectClass=inetLocalMailRecipient)(uid=%n)) ###################################### Only interesting thing from the debug logs is a prefetch related entry: ###################################### Apr 25 17:31:22 mda01 dovecot: auth: Debug: master in: USER#01119118#011dev13654#011service=doveadm Apr 25 17:31:22 mda01 dovecot: auth: Debug: prefetch(dev13654): passdb didn't return userdb entries, trying the next userdb Apr 25 17:31:22 mda01 dovecot: auth: Debug: ldap(dev13654): user search: base=ou=instances,dc=csi,dc=domain,dc=com scope=subtree filter=(&(objectClass=mailUser)(uid=dev13654)) fields=uid,maildrop Apr 25 17:31:22 mda01 dovecot: auth: Debug: ldap(dev13654): result: uid=dev13654 maildrop=dev13654/maildir/; maildrop,uid unused Apr 25 17:31:22 mda01 dovecot: auth: Debug: ldap(dev13654): result: uid=dev13654 maildrop=dev13654/maildir/ Apr 25 17:31:22 mda01 dovecot: auth: Debug: userdb out: USER#01119118#011dev13654#011home=/glide/mail/spool/dev13654#011mail=maildir:/glide/mail/spool/dev13654/maildir/ ######################################

1 0

doveadm backup 2.2.23 ignores -u, but reads USER environment?
by Heiko Schlittermann 26 Apr '16

26 Apr '16

Hi, during a migration (cyrus -> dovecot) we ran into trouble¹ using 'doveadm backup' with 2.2.9. So I built 2.2.22 and 2.2.23, but they expose quite different behaviour. 2.2.22 seems to work at least partially, but 2.2.23 complains about a non existing user (root?). The command I'm running is: doveadm -o pop3_uidl_format=%v.%u \ -o imapc_master_user=cyrus -o imapc_password=* -o imapc_host=* \ -o mail_fsync=never \ -o imapc_ssl_verify=no -o imapc_ssl=imaps -o imapc_port=993 \ backup -f -u heiko -R imapc: Using 2.2.9 or 2.2.22 it works, using 2.2.23 "-u …" is ignored and I've to pass the user via the USER environment. But according to the manpage of doveadm-sync -u user/mask Run the command only for the given user. It's also possible to use '*' and '?' wildcards (e.g. -u *(a)example.org) When neither the -A option, nor the -F file option, nor the -u user was specified, the command will be executed with the environment of the currently logged in user. Interestingly enough -u 'heiko*' works fine, even with USER=root. So the environment doesn't seem to override -u … always. Maybe an important side note: the user 'heiko' doesn't exist as a local system user, he is known via LDAP only. And for e.g. 'doveadm quota -u heiko' it works as expected, even with 2.2.23. ¹) solved meanwhile by using -o mail_plugins= as the quota plugin seems to crash 'doveadm backup' 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 ------------ -

1 0

Setting up replication?
by Knute Johnson 25 Apr '16

25 Apr '16

I'm trying to set up replication between two servers and I've hit a snag. I have two users and am using mbox files. If anybody has a sample config file for a simple system like mine I would really be grateful to see it. Thanks, The error I'm getting is: Mar 23 14:07:31 knute2 dovecot: doveadm(192.168.3.100,nobody): Error: user nobody: Initialization failed: Namespace '': mkdir(/nonexistent/mail) failed: Permission denied (euid=65534(nobody) egid=65534(nogroup)) Mar 23 14:07:31 knute2 dovecot: doveadm(192.168.3.100,nobody): Error: dsync-server: User init failed Mar 23 14:07:31 knute2 dovecot: doveadm(nobody): Error: sync: Failed to start dsync-server command: 75 knute@knute2:/etc/dovecot/conf.d $ sudo doveadm user '*' nobody knute penny I don't know why the user 'nobody' shows up here? nobody is in the /etc/passwd file but he has no group. knute@knute2:/ $ cat /etc/passwd | grep nobody nobody:x:65534:65534:nobody:/nonexistent:/usr/sbin/nologin ----------------------- I created a separate config file as suggested in Peer Heinlein's book. knute@knute2:/etc/dovecot/conf.d $ cat 12-replication.conf mail_plugins = $mail_plugins notify replication service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service doveadm { inet_listener { port = 30303 } } #doveadm_port = 30303 doveadm_password = secret plugin { mail_replica = tcp:knute2.frazmtn.com:30303 } replication_dsync_parameters = -d -N -l 30 -U --------------------- knute@knute2:/etc/dovecot/conf.d $ dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 4.1.19-v7+ armv7l Debian 8.0 doveadm_password = secret mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_plugins = " notify replication" namespace { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { auto = subscribe special_use = \Trash name = Trash } prefix = name = inbox } passdb { driver = pam } plugin { mail_replica = tcp:knute3.frazmtn.com:30303 } protocols = " imap" service { fifo_listener { mode = 0666 path = replication-notify-fifo } unix_listener { mode = 0666 path = replication-notify } name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service { inet_listener { port = 30303 name = } name = doveadm } service imap { inet_listener { port = 0 name = imaps } name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service { inet_listener { port = 0 name = pop3 } inet_listener { port = 0 name = pop3s } name = pop3-login } service login/pop3 { name = pop3 } service { process_min_avail = 1 unix_listener { mode = 0600 path = replicator-doveadm } name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } protocol lmtp { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { mail_max_userip_connections = 32 service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service login/imap { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } -- Knute Johnson

5 10

Moving to as new server
by Jerry 25 Apr '16

25 Apr '16

I will shortly have to replace the OS on my machine. For various reasons, I will not be able to use a program like “imapsync” to transfer my documents to a new server. All of the mail folders on my present PC are stored under “/var/mail/vmail”. If I copied all of the folders under “vmail” and moved them to the new PC, would Dovecot be able to access them normally? Dovecot would not be running while I moved the files. Thanks

3 2

expunging messages doesn't update maildirsize
by WJCarpenter 24 Apr '16

24 Apr '16

This might be something that everybody thinks of as a well-known fact, but I've been searching around quite a bit without finding anything definitive. Maybe I just have the wrong idea of what's supposed to be going on. I'm using maildir+ quotas. For arriving mail, it works as I expect: new lines are appended to maildirsize to reflect the size of the new messages. But I also expected that mail that is deleted (and expunged, yes totally gone from the disk drive, verified from the command line) would lead to some kind of update to maildirsize or maybe even a complete recalculation. But that does not happen on my system (dovecot 2.2.9 on a Ubuntu variant). Now, I know that I can run "doveadm" from a cron job or whatever to have the maildirsize info recomputed. I also know that the maildirsize file will be recreated when it gets larger than 4k. That's all fine. But I don't see why I should have to have this out-of-band cron job, and I don't see why my users should have to wait if their maildirsize file doesn't tip over the magical 4k mark (which is a lot of individual messages being recorded). Is it by design that dovecot doesn't update maildirsize immediately when messages are expunged? If yes, why?

1 1

Redirect indicator issue in Maildir flag seems to be an issue [missing?]
by Andrew McGlashan 23 Apr '16

23 Apr '16

Hi, I've got an issue with the latest Thunderbird, although I'm not sure this is when the problem started (version 45.0) it has an add-on "mailredirect (version 0.8.7)". In the past I've been able to redirect mail (bounce them) and I get a nice little green arrow like indicator (in TB) to show that I redirected the particular email. Now, that green arrow appears briefly, then it goes away and I can no longer tell by looking at my email list if the email has, in fact, been bounced or not. I suspect it is dovecot on the Debian server: dovecot-common 1:2.1.7-7+deb7u1 dovecot-core 1:2.1.7-7+deb7u1 dovecot-imapd 1:2.1.7-7+deb7u1 dovecot-pop3d 1:2.1.7-7+deb7u1 It isn't just Thunderbird though, as I just tried to redirect using a Squirrelmail plugin, and it gives me the same problem; so I don't think it is at the MUA end of the deal. It /may/ be that TB is setting the flag and resetting it or dovecot is resetting it.... Any ideas? Nobody else has seen this yet? Thanks AndrewM

2 1

Maildir P flag?
by Andrew McGlashan 23 Apr '16

23 Apr '16

Hi, I use Thunderbird with a mailredirect addon. It used to show me which emails were redirected. I believe it used the "P" Maildiir flag for this status. Now it seems that none of my email store has any file with a flag of P. Is this something that dovecot may have adjusted with my mail store? And if so, why? If not, any ideas where I might look for the next "culprit"? ;-) Thanks AndrewM

1 0

Progress messages
by Joel Roth 23 Apr '16

23 Apr '16

Hi Dovecot maintainers, I'm maintainer of Net::IMAP::Client, a perl IMAP client library.[1] I've had two bug reports related to Dovecot's in-progress messages.[2,3] While patches have been submitted to resolve both of these bugs, I would like to minimize the possibilty of future breakage. Hence the following questions: 1. Which parts of the RFC are relevant to the in-progress messages? 2. Do you have a list of all of Dovecot's in-progress messages? 3. If, in future, other in-progress messages may be added, can you provide a standard syntax that I may use to strip them from the reply stream. Finally, please CC replies to me, as I am not joined to the list. Thank you for your attention. Joel 1. https://metacpan.org/pod/Net::IMAP::Client 2. https://rt.cpan.org/Public/Bug/Display.html?id=84623 3. https://rt.cpan.org/Public/Bug/Display.html?id=113489 -- Joel Roth

2 1

UTF-8 encoded folders on filesystem
by Pavel Volkovitskiy 22 Apr '16

22 Apr '16

Hello! I wonder if that possible to have utf-8 encoded folders on filesystem with dovecot? May be this feature planned already? -- Pavel

3 5

Aborted login (auth failed)
by Christof Bodner 22 Apr '16

22 Apr '16

Hi, My SSL auth got invalid, so I updated my SSL configuration (Apache works) This ist the log: --- Apr 22 11:01:55 rosi dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Apr 22 11:01:55 rosi dovecot: imap-login: Debug: SSL: elliptic curve secp384r1 will be used for ECDH and ECDHE key exchanges Apr 22 11:01:55 rosi dovecot: auth: Debug: auth client connected (pid=3466) Apr 22 11:01:55 rosi dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011secured#011session=a5AlFA8x3gAAAAAAAAAAAAAAAAAAAAAB#011lip=::1#011rip=::1#011lport=143#011rport=48350#011resp=<hidden> Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1): lookup service=dovecot Apr 22 11:01:55 rosi dovecot: auth-worker(3460): Debug: pam(test,::1): #1/1 style=1 msg=Password: Apr 22 11:01:57 rosi dovecot: auth-worker(3460): pam(test,::1): pam_authenticate() failed: Authentication failure (password mismatch?) Apr 22 11:01:59 rosi dovecot: auth: Debug: client passdb out: FAIL#0111#011user=test Apr 22 11:01:59 rosi dovecot: imap-login: Aborted login (auth failed, 1 attempts in 4 secs): user=<test>, method=PLAIN, rip=::1, lip=::1, secured, session=<a5AlFA8x3gAAAAAAAAAAAAAAAAAAAAAB> --- A login via SSH is working, What could be the reason for the login fail? This is my config: --- # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-85-generic x86_64 Ubuntu 14.04.4 LTS auth_debug = yes auth_verbose = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace { hidden = yes inbox = yes list = no location = mbox:~/mail:INBOX=/var/mail/%u prefix = "#mbox/" separator = / type = private } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } sl_ca = </etc/letsencrypt/live/HOST/chain.pem ssl_cert = </etc/letsencrypt/live/HOST/cert.pem ssl_key = </etc/letsencrypt/live/HOST/privkey.pem userdb { driver = passwd } verbose_ssl = yes protocol imap { mail_max_userip_connections = 400 } --- Thanks in advance for your help! KR, Christof -- --------------------------------------------------------------------- <http://www.oe8.oevsv.at>Landesverband Kärnten Christof Bodner, OE8BCK Bertha-von-Suttnerstraße 6/4 9500 Villach ---------------------------------------------------------------- email: mailto:oe8bck@oevsv.at Tel.: +43-650-7215383 --------------------------------------------------------------------- GnuPG public key: 0x7204CB8C Fingerprint 4065 0716 9A15 E26B 2286 9F04 FD3B 74E9 7204 CB8C ---------------------------------------------------------------------

2 2

Thunderbird version 45 no longer can login via SSL
by CJ Keist 22 Apr '16

22 Apr '16

All, Just ran into issue with the latest Thunderbird release today, version 45.0. This version will no longer login to our dovecot 1.2.17 version. I now this is old version but wanting to know if there is anyone finding a solution to this? Right now our work around is to reinstall Thunderbird version 38.7.2 Thanks... -- C. J. Keist Email: cj.keist(a)colostate.edu Systems Group Manager Solaris 10 OS (SAI) Engineering Network Services Phone: 970-491-0630 College of Engineering, CSU Fax: 970-491-5569 Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness'

3 2

multiple recipient_delimiter
by Jörg Backschues 22 Apr '16

22 Apr '16

Hello, does the recipient_delimiter option accepts multiple delimiter by now? -- Regards Jörg Backschues

3 3

lda_original_recipient_header overrides RCPT TO?
by Gedalya 22 Apr '16

22 Apr '16

Hi all, The example config says: # Header where the original recipient address (SMTP's RCPT TO: address) is taken # from if not available elsewhere. With dovecot-lda -a parameter overrides this. # A commonly used header for this is X-Original-To. #lda_original_recipient_header = I'm using dovecot 2.2.19 The "if not available elsewhere" bit seems to hold true for LDA, but not for LMTP. That is to say, if the value I want used is passed with LDA using the -a option, and another one I want ignored is passed in the header specified in this option, it works correctly and I have the address detail in sieve. However when using LMTP and the desired value is passed as RCPT TO, and this option is defined, and such a header exists -- its value seems to take effect, and is matched by sieve as the envelope address.

1 0

Randomly SSL Errors since upgrade to 2.2.23-1 (Enterprise Edition)
by Urban Loesch 21 Apr '16

21 Apr '16

Hi, first of all, many thanks for a great piece of software. Today I updated one of our 2 IMAP/POP3 proxies from version 2.2.15.17-1 to 2.2.23.1-1 (both are enterprise editions). After the update I now see randomly the following errors in the log file on my first proxy: ... Apr 15 10:28:54 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:34:24 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:37:11 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:39:04 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:43:02 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:45:14 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:50:31 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:54:56 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac Apr 15 10:57:44 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 10:59:49 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:00:59 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:13:43 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:14094438:SSL routines:SSL3_READ_BYTES:tlsv1 alert internal error: SSL alert number 80 Apr 15 11:15:21 imap1 dovecot: imap-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:18:33 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:20:12 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:140D00CF:SSL routines:SSL_write:protocol is shutdown Apr 15 11:20:40 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac ... Some more details: OS: Debian wheezy (latest patchlevel) Dovecot: ii dovecot-ee-core 2:2.2.23.1-1 ii dovecot-ee-imapd 2:2.2.23.1-1 ii dovecot-ee-managesieved 2:2.2.23.1-1 ii dovecot-ee-mysql 2:2.2.23.1-1 ii dovecot-ee-pop3d 2:2.2.23.1-1 ii dovecot-ee-sieve 2:2.2.23.1-1 Libssl: ii libssl1.0.0:amd64 1.0.1e-2+deb7u20 One my second proxy there is running also Debian Wheezy with the latest patchlevel but dovecot version 2.2.15.17-1 (not yet updated): ii dovecot-ee-core 1:2.2.15.17-1 ii dovecot-ee-imapd 1:2.2.15.17-1 ii dovecot-ee-managesieved 0.4.6-4 ii dovecot-ee-mysql 1:2.2.15.17-1 ii dovecot-ee-pop3d 1:2.2.15.17-1 ii dovecot-ee-sieve 0.4.6-4 On this box I can't see this strange errors. Until now there was no user that complaints that he can't read his mails. Do you know what could cause this errors (for example: very old clients and so on)? Or are the logging of this errors new in dovecot 2.2.23? Many thanks Urban Loesch

2 2

problem with Sieve Duplicate Extension when used together with fileinto
by Marco Giunta 21 Apr '16

21 Apr '16

Hi at all, I'm trying to figure out a problem with Sieve Duplicate Extension when used together with fileinto. I use a Dovecot 2.2.23 and Pigeonhole v0.4.13 I have a user (user01) with 3 email addresses (mail01(a)example.com, mail02(a)example.com, user01(a)example.com) I want to discard duplicate, and I want to move email in different folder, so I'm using this sieve script: ---------------------------------------------- require ["fileinto", "duplicate", "imap4flags"]; if duplicate { discard; stop; } if address :is :all "to" "mail01(a)example.com" { fileinto "mail01"; } if address :is :all "to" "mail02(a)example.com" { fileinto "mail02"; } ------------------------------------- To make my test, I have a script that send always the same email; this is an example: ----------------------------------------- Delivered-To: user01(a)example.com Received: from smtp-server.example.com ([192.168.1.214]) by lmtp-server.example.com (Dovecot) with LMTP id YSaBBU53GFdhbwAAIDyJFw for <user01(a)example.com>; Thu, 21 Apr 2016 08:48:41 +0200 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: TEST EMAIL From: myself(a)example.com To: mail01(a)example.com, mail02(a)example.com, user01(a)example.com Date: Thu, 21 Apr 2016 08:48:41 +0200 Message-ID: <20160421064841.26889.86769(a)kratos.example.com> This is a test email Please ignore me. -------------------------------------------- The problem is that duplicate extension doesn't ALWAYS work ; I mean, one time it works (sieve discard 2 duplicate mails), one time it doesn't work at all (sieve doesn't discard any mail), another time it works only for one mail (sieve discards only 1 mail) Here my server log: Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): 1dKXOMl3GFdibwAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): 1dKXOMl3GFdibwAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): oSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:07 smtp-server dovecot: lmtp(user01(a)example.com): eY00CY93GFcucgAAIDyJFw: sieve: msgid=<20160421064906.26896.49900(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): dSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): dSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): pSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:13 smtp-server dovecot: lmtp(user01(a)example.com): vZWNOMl3GFcldAAAIDyJFw: sieve: msgid=<20160421064913.26904.88802(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): eSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): qSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): qSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): aSaBBU53GFdhbwAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): aSaBBU53GFdhbwAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:18 smtp-server dovecot: lmtp(user01(a)example.com): eSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064918.26911.55371(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:22 smtp-server dovecot: lmtp(user01(a)example.com): rSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:22 smtp-server dovecot: lmtp(user01(a)example.com): rSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:22 smtp-server dovecot: lmtp(user01(a)example.com): YVCsNPJ3GFd1dgAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:23 smtp-server dovecot: lmtp(user01(a)example.com): bSaBBU53GFdhbwAAIDyJFw: sieve: msgid=<20160421064922.26919.68793(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): fSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): sSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail01' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): sSM3And3GFdFaQAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): fSOyOtV3GFcmdAAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: stored mail into mailbox 'mail02' Apr 21 08:49:27 smtp-server dovecot: lmtp(user01(a)example.com): ZVCsNPJ3GFd1dgAAIDyJFw: sieve: msgid=<20160421064927.26926.28383(a)myhost.example.com>: marked message to be discarded if not explicitly delivered (discard action) As you can see, the message ID of a single sent, is the same, so the duplicate extension should work. If I replace the 'fileinto' rule with, for example, a 'setflag' rule: ----------------------------------------------- require ["fileinto", "duplicate", "imap4flags"]; if duplicate { discard; stop; } if address :is :all "to" "mail01(a)example.com" { setflag "\\seen"; } if address :is :all "to" "mail02(a)example.com" { setflag "\\seen"; } ---------------------------------------------- it works like a charm: for every mail sent, the duplicate extension works. What is it wrong ? someone has any clue ? Cheers, Marco -- Marco Giunta - ITCS SysAdmin Via Bonomea, 265 34136 - Trieste, Italy Tel: +39-040-3787-503 Fax: +39-040-3787-244

1 0

Deliver same E-Mail in same Mailbox only once ?
by Christoph Adomeit 21 Apr '16

21 Apr '16

Hi there, I have a customer with domain a@tld and domain b@tld. b.tld is an alias for a.tld The Server is using virtual users based on mysql, dovecot for delivery and Maildir for Mail-Storage. If someone writes an e-mail to a.tld with a cc: to b.tld the customer receives the E-Mail twice. Is there a way to deliver the same Mail in the same Mailbox only once ? -- Christoph Adomeit GATWORKS GmbH Reststrauch 191 41199 Moenchengladbach Sitz: Moenchengladbach Amtsgericht Moenchengladbach, HRB 6303 Geschaeftsfuehrer: Christoph Adomeit, Hans Wilhelm Terstappen Christoph.Adomeit(a)gatworks.de Internetloesungen vom Feinsten Fon. +49 2166 9149-32 Fax. +49 2166 9149-10

5 5

Module is for different ABI version
by Oliver Riesen-Mallmann 21 Apr '16

21 Apr '16

Hi, I'm using the Dovecot Prebuilt Binary: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main It seems, that the Prebuilt Binary provided at least once the 2.3 version, because doveconf -n shows: # 2.3.devel (5e7036c): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (ef25ce6) # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.10 Now Prebuilt Binary provides the 2.2 version again, but I get some error messages on updates: Preparing to replace dovecot-imapd 2:2.2.23-1~auto+14 (using .../dovecot-imapd_2%3a2.2.23-1~auto+16_amd64.deb) ... doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) and: Preparing to replace dovecot-core 2:2.2.23-1~auto+14 (using .../dovecot-core_2%3a2.2.23-1~auto+16_amd64.deb) ... doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_login_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) doveconf: Error: Couldn't load plugin /usr/lib/dovecot/modules/settings/libmanagesieve_settings.so: Module is for different ABI version 2.2.ABIv20(2.2.devel) (we have 2.3.ABIv0(2.3.devel)) After the update doveconf -n shows: # 2.2.devel (8828071): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (ef25ce6) # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.10 How can I go back to ABI version 2.2? Regards Oliver

1 0

Foreman component
by Aki Tuomi 20 Apr '16

20 Apr '16

Hi! I am planning to add foreman component to dovecot core and I am hoping for some feedback: Foreman - generic per-user worker handling component It is responsible for managing worker pools per protocol, lifecycle management of workers and handing out instances to others, as in, unix socket connections. Each time a request is made to foreman for a worker, the worker is instantiated (if possible) and locked. Then connection is created to the socket of the worker, and the file descriptor is returned to requestor. When the requestor has completed the task, it's responsibility is to close the DATA channel and also ask foreman to unlock the worker. Components can register new workers using lib-foreman's API. Each worker is registered with struct foreman_worker { const char *protocol; const char *path; const char *version; unsigned int max_instances; unsigned int max_requests; /* how many requests one worker can handle */ unsigned int max_idletime_secs; /* how long worker can idle */ unsigned int max_processtime_secs; /* how long worker can process something */ unsigned int max_lifetime_secs; /* how long a worker can live this can be exceeded if the worker has work to do. */ }; /* minimum lifetime of worker: max_idletime_secs */ /* absolute maximum lifetime of worker: max_lifetime_secs + max_processtime_secs */ The unsigned ints are optional. If they are not defined, the workers are kept until foreman exceeds the total number of workers permitted across pools. Pools are per-worker-class pools, and are generated when a worker is registered. Version specifies the protocol version and is going to be "1000" now. Next version will always be 1001, 1002 etc. Any feedback or questions are welcome! Aki

3 2

Reappearing emails (resolved by 2.2.23)
by Ron Cleven 20 Apr '16

20 Apr '16

> ------------------------------ > > Message: 6 > Date: Wed, 16 Mar 2016 16:58:49 +1100 > From: Timo Sirainen<tss(a)iki.fi> > To: Dovecot Mailing List<dovecot(a)dovecot.org> > Subject: Re: Reappearing emails - IMAP trace > Message-ID:<4C26CC22-7C7D-4D91-A767-4E5B3D1F12BA(a)iki.fi> > Content-Type: text/plain; charset=us-ascii > > What mailbox format do you use? Are you able to reproduce this by running doveadm sync commands manually instead of letting replication do it? For example: > > - doveadm sync -s "" -d -u user@domain > state > - Run the UID STORE & UID MOVE > - doveadm sync -s "`cat state`" -d -u user@domain > > There have been some fixes, especially recentlyhttps://github.com/dovecot/core/commit/950a6e61d6c2dac961ce031bdd8b… sounds a bit similar although I don't really see how it would apply here. Would be a good idea to try anyway with v2.2.22.rc1 (which seems to be stable enough that I'll make v2.2.22 release soon). > > Anyway, I attempted a few times to reproduce it with your test but wasn't able to. We had been running 2 replicating servers (Maildir format) using version 2.2.10 under CentOS 7 in production for quite some time. In this forum, I reported a problem that I traced to a timing problem where unread emails being moved to Trash would magically reappear in the INBOX. I have since upgraded our production servers to 2.2.23. The new version resolved the problem. The version upgrade also resolved the occasional, but annoying, dsync maillog entries "Duplicate file entry at line ...". So, I am a very happy camper and appreciate the feedback.

2 1

GSSAPI authentication setup
by Braden McDaniel 20 Apr '16

20 Apr '16

I'm setting up dovecot on a new box; and once again I find myself banging my head against GSSAPI authentication. The particularly irritating thing is that I have this working on another box. I've done my best to ape the configuration of that box; but it's been some years since I set it up and somewhere along the line I have failed. My dovecot.conf has: auth_mechanism = plain gssapi passdb { driver = pam } userdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } where /etc/dovecot/dovecot-ldap.conf.ext is: hosts = ldap dn = cn=Manager,dc=endoframe,dc=net dnpass = XXXXXXXX ldap_version = 3 base = ou=people,dc=endoframe,dc=net deref = never scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) I've diff'd the contents of /etc/dovecot on the working vs. non-working servers, and I can see nothing of pertinence (just a few lines about loading the sieve plug-in). Now, logging in with the kerberos password via PAM *is* working. /etc/pam.d/dovecot: #%PAM-1.0 auth sufficient pam_krb5.so account sufficient pam_krb5.so But GSSAPI authentication is not: [ root@hinge ~]# telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=GSSAPI] Dovecot ready. a authenticate GSSAPI a NO [UNAVAILABLE] Temporary authentication failure. [hinge.endoframe.net:2016-04-16 21:33:32] ^] telnet> close Connection closed. Oh... The kerberos server does have an IMAP service key for hinge; and that service key appears in hinge's /etc/krb5.keytab, as well. Any pointers on where I should be looking at this point would be very much appreciated. -- Braden McDaniel <braden(a)endoframe.com>

3 6

sieve vacation: write to the .lda-dupes database without generating a vacation response.
by Bradley M. Kuhn 20 Apr '16

20 Apr '16

I'm using Dovecot's sieve extensions quite happily, they are very good! Thanks for all who worked on them. I have a question that maybe is appropriate for a sieve-specific discussion list, so if there is one I should post to instead, please let me know: I've poked through the sieve vacation RFC and all the documentation I can find and I cannot figure out how to do this. It's more-or-less not the intent of sieve's vacation, so perhaps it's more of a "you can't get there from here" situation, but maybe folks here have an idea: I am (ab)?using sieve vacation to send an automated response at all times to all senders who put me in the To line, every 90 days, which explains my lack of responsiveness and to explain who else might be better contact. (I have hundreds of emails sent to me to which I will never have time to respond, and probably should have been routed to someone else at my organization anyway.) However, I *don't* want my regular correspondents to receive this autoreply. I'd thus like to seed the database with known individuals I'm corresponding with to pretend they've already received the autoresponder. Since I bcc an archive address on all emails, my original thought was to detect people in the To and Cc line of outgoing emails and record them in the .lda-dupes database, as they received a vacation email. I can't figure out how to do this; there is no option on the sieve vacation directive that I can find to do something like this (i.e., I'm looking for a a "do the usual, but *don't* actually send the the email" option on the sieve vacation directive). I do have various other solutions that help in this regard, for example, I never send a vacation email to messages that match: header :contains "In-Reply-To" "@example.org" (where example.org is my domain). This helps, but obviously doesn't handle the situation where the correspondent doesn't reply to one of my emails, or had a stupid MUA. Furthermore, I'd like to implement as many methods as possible for my regular corespondents to limit their receipt of the autoresponder. Any ideas? Thanks in advance for any help or advice you can give! -- -- bkuhn ======================================================================== Become a Conservancy Supporter today: https://sfconservancy.org/supporter

4 4

[Dovecot] Patch: 2.0 support for URLAUTH, BURL, CATENATE
by Mike Abbott 18 Apr '16

18 Apr '16

Thank you Timo for beginning the port of URLAUTH, BURL, and CATENATE from 1.2 to 2.0. Attached please find two patches that finish the port to 2.0. One patch updates the dovecot-2.0-urlauth branch and is based on the tip of that branch. The other patch adds the full support to dovecot-2.0.beta5. The resulting URLAUTH/BURL/CATENATE code is the same. Please let me know if you have any questions about these patches. Thanks.

4 9

stats: Error: FIFO input error: CONNECT: Duplicate session ID
by Urban Loesch 18 Apr '16

18 Apr '16

Hi, yesterday I updatet to Dovecot EE version 2:2.2.23.1-1. Now sometimes I see this errors in my logs: ... Apr 18 09:02:19 dovecot1 dovecot: stats: Error: FIFO input error: CONNECT: Duplicate session ID NjcCDoSAFFd/KQAAFMUCeg for user user(a)domain1.com service lmtp Apr 18 09:04:05 dovecot1 dovecot: stats: Error: FIFO input error: CONNECT: Duplicate session ID rjV1HtCGFFcoogAAFMUCeg for user user(a)domain2.com service lmtp Apr 18 09:04:30 dovecot1 dovecot: stats: Error: FIFO input error: CONNECT: Duplicate session ID Sqi0IMWAFFeRNQAAFMUCeg for user user(a)domain3.com service lmtp ... The error only appears when a mail is sent to 2 ore more recipients concurrently. It's not ciritcal for me, all mails are getting delivered correctly. Thanks and regards Urban Loesch

2 1

AD LDAP auth shows unknown results
by victorpictor＠mailbox.hu 15 Apr '16

15 Apr '16

Hi List! Been struggling with AD LDAP auth, ldapsearch shows everything fine, but when I try to telnet, the log shows unknown attributes. Dovecot 2.0.19 dovecot -n: # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.5.0-23-generic x86_64 Ubuntu 12.04.5 LTS ext4 auth_debug = yes auth_mechanisms = plain login auth_username_format = %n auth_verbose = yes disable_plaintext_auth = no listen = * mail_location = maildir:/var/mail/%u%d/Maildir namespace inbox { inbox = yes location = prefix = } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot/sieve/ } protocols = " imap lmtp pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } ssl = no ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } protocol lmtp { mail_plugins = " sieve" postmaster_address = postmaster(a)domain.hu } Contents of passdb.conf: hosts = 1.2.3.4 auth_bind = yes auth_bind_userdn = DOMAIN\%u ldap_version = 3 base = dc=domain,dc=in scope = subtree deref = never pass_filter = (&(objectClass=person)(sAMAccountName=%u)(mail=*)) Contents of userdb.conf: hosts = 1.2.3.4 dn = DOMAIN\user dnpass = xxx ldap_version = 3 base = dc=domain,dc=in user_attrs = =uid=108,=gid=115,=home=/var/mail/%Lu,=mail=maildir:/var/mail/%Lu/Maildir/ user_filter = (&(objectClass=person)(sAMAccountName=%u)(mail=*)) # Attributes and filter to get a list of all users iterate_attrs = sAMAccountName=user iterate_filter = (objectClass=person) And the log after a test login: Apr 15 18:10:52 ubuntutest2 dovecot: auth: Debug: ldap(user,127.0.0.1): user search: base=dc=domain,dc=in scope=subtree filter=(&(objectClass=person)(sAMAccountName=user)(mail=*)) fields= Apr 15 18:10:52 ubuntutest2 dovecot: auth: Debug: ldap(user,127.0.0.1): result: objectClass(?unknown?)= cn(?unknown?)= instanceType(?unknown?)= whenCreated(?unknown?)= uSNCreated(?unknown?)= name(?unknown?)= objectGUID(?unknown?)= badPwdCount(?unknown?)= codePage(?unknown?)= countryCode(?unknown?)= badPasswordTime(?unknown?)= lastLogoff(?unknown?)= lastLogon(?unknown?)= primaryGroupID(?unknown?)= objectSid(?unknown?)= accountExpires(?unknown?)= logonCount(?unknown?)= sAMAccountName(?unknown?)= sAMAccountType(?unknown?)= userPrincipalName(?unknown?)= objectCategory(?unknown?)= givenName(?unknown?)= initials(?unknown?)= sn(?unknown?)= displayName(?unknown?)= description(?unknown?)= physicalDeliveryOfficeName(?unknown?)= userAccountControl(?unknown?)= msDS-SupportedEncryptionTypes(?unknown?)= pwdLastSet(?unknown?)= homeDrive(?unknown?)= homeDirectory(?unknown?)= memberOf(?unknown?)= mail(?unknown?)= whenChanged(?unknown?)= uSNChanged(?unknown?)= distinguishedName(?unknown?)= Any idea? Thanks for advance! Victorpictor

1 0

Tighten TLS - usage of specific ssl_ec-curve
by Martin 15 Apr '16

15 Apr '16

Hi folks, at first: thanks very much for the great piece of software! I have a proposal to tighten the TLS security: enable the usage of a specific ec-curve in the 10-ssl.conf, e.g. ssl_ec-curve = secp384r1 Reason: I use a 384 bit EC server key, but dovecot uses "only" a prime256v1 curve. Keygen was: f=dovecot; openssl ecparam -name secp384r1 -genkey -out $f.key openssl req -new -x509 -key $f.key -out ${f}.crt -days 2000 -sha512 Server check gives: prio ciphersuite protocols pfs curves 1 ECDHE-ECDSA-AES128-GCM-SHA256 TLSv1.2 ECDH,P-256,256bits prime256v1 2 ECDHE-ECDSA-AES128-SHA256 TLSv1.2 ECDH,P-256,256bits prime256v1 3 ECDHE-ECDSA-AES128-SHA TLSv1.2 ECDH,P-256,256bits prime256v1 4 ECDHE-ECDSA-AES256-GCM-SHA384 TLSv1.2 ECDH,P-256,256bits prime256v1 5 ECDHE-ECDSA-AES256-SHA384 TLSv1.2 ECDH,P-256,256bits prime256v1 6 ECDHE-ECDSA-AES256-SHA TLSv1.2 ECDH,P-256,256bits prime256v1 Certificate: UNTRUSTED, 384 bit, ecdsa-with-SHA512 signature $ sudo nano /etc/dovecot/conf.d/10-ssl.conf ssl = required ssl_protocols = !SSlv2 !SSLv3 TLSv1.2 ssl_cipher_list = EECDH+AES128+AESGCM:EECDH+AES256+AESGCM:EECDH+AES128+SHA256:EECDH+AES256+SHA384:EECDH+AES128+SHA:EECDH+AES256+SHA ssl_prefer_server_ciphers = yes ssl_key = </etc/dovecot/dovecot.key ssl_cert = </etc/dovecot/dovecot.crt OS is arch linux. Thanks very much, Martin

2 1

How to filter spam with same to: and from: adress
by Claude 14 Apr '16

14 Apr '16

Is it possible to create a filter somewhere to delete email that have same to: and from: adress. All these email are forged using my domain name with always different fictif user name. The only common point is that they have the same user name in the from: and to: adress Claude Gelinas agr. Phyto Ressources Inc.

2 1

A few new Pigeonhole features
by Stephan Bosch 14 Apr '16

14 Apr '16

Hi, A few new Pigeonhole features that enthusiasts can experiment with: - Recently, I implemented support for the "imapsieve" extension in Sieve and its IMAP counterpart (https://tools.ietf.org/html/rfc6785) This is now in the Pigeonhole master branch. 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. The documentation is currently only in the sources and not on the wiki: https://raw.githubusercontent.com/dovecot/pigeonhole/master/doc/plugins/ima… - Yesterday, I implemented online trace debugging for Sieve scripts: i.e., directly during delivery rather than only using the sieve-test tool. This is also supported for the IMAPSIEVE feature discussed above. This is documented in the INSTALL file: https://github.com/dovecot/pigeonhole/blob/master/INSTALL#L522 In other news, I started a specification for a new Sieve feature that allows using the IMAP SPECIAL-USE attributes from Sieve scripts: https://tools.ietf.org/html/draft-bosch-sieve-special-use-00 There is no implementation yet. Any comments, suggestions or bug reports are welcome. Regards, Stephan.

2 4

Dovecot and Windows Live Mail 2012?
by David Mehler 14 Apr '16

14 Apr '16

Hello, I hope someone has this working, because I'm pulling my hair out at this one. I'm using well for this it's a win7 x64 machine running Windows Essentials 2012 and using the Windows Live mail component. I am trying to connect to my Dovecot server running 2.23 I believe. I keep getting the error "the imap command could not be sent to the server because of a non-network error" googling showed many with this, but no fix. In this account I'm trying to access port 143 which uses starttls. In Mail I've got the boxes for require a secure connection and authentication checked. I should note of course and with no surprise that Mail works oh just fine with the Hotmail account I've also got configured, it's only with the downloading of folders and sending of email to the dovecot server that mail has the issue. Please let me know if I can provide any additional information. Help appreciated. Thanks. Dave.

3 3

Best way to only replicate specific users
by Max 14 Apr '16

14 Apr '16

Hi, I was wondering about the best way to achieve this. Currently, the users I don't want replicated do not exist on the target system. The source tries to sync them but runs into an error. Technically, that works for me, but it doesn't seem like the right way to do it and clutters the log. Kind Regards, Max

1 0