- dovecot - dovecot.org

Parsing variables in config files
by Eudald Valcàrcel Lacasa 15 Dec '19

15 Dec '19

Hello, I'm trying to set up a mailbox for a bunch of domains. To do so I'm running some docker containers (I know I can use multidomain set up and I'm doing so, but I need to have some domains on different containers for specific reasons). In order to keep it all clean, I want to use different PostgreSQL databases for each container, and I'm running the container with an environment file containing database parameters, such as: DB_USER DB_HOST DB_NAME I've been trying to pass these parameters to dovecot's configuration, but they don't get parsed and I end up with messages like: dovecot: auth: Error: pgsql(%{env:DB_HOST}): Connect failed to database %{env:DB_NAME} I've tried to pass variables alone, using import_environment = DB_HOST DB_NAME DB_USER, but I'm stuck at the same errors. Is there anything I could do to fix this? Thank you! Eudald

2 2

Doveadm HTTP API and CORS
by Peter Chiochetti 13 Dec '19

13 Dec '19

While toying around with Doveadmin HTTP api I noticed, there is not much hype around it. Let's change that. Doveadmin REST API so to speak provides a web server. When doing /ajax/ requests, modern browsers block that, unless the response comes with a specific CORS header. Here how to work around with a proxy: > # /etc/dovecot/local.conf > doveadm_allowed_commands = fetch > doveadm_api_key = secret > service doveadm { > inet_listener http { > port = 8084 > } > } > # secret64 = echo -n secret | base64 > # /etc/apache/.../some-site.conf > ProxyVia Block > <Location /doveadm/v1> > RequestHeader set Authorization "X-Dovecot-API secret64" > ProxyPass http://localhost:8084/doveadm/v1 retry=0 timeout=5 > ProxyPassReverse http://localhost:8084/doveadm/v1 > </Location> Intranet only this might be good enough, TLS with username/password Basic-Authentication passthrough might be used for better security. Shameless plug: taken from https://gist.github.com/hungerburg/00d582bf1a6bf3c622797bf5e759f75b -- peter

2 1

BUG: panic when using fs:posix as dict for acl_shared_dict
by Marco Giunta 13 Dec '19

13 Dec '19

Hi, I'm using Dovecot 2.2.33.2 on a RHEL 7, new installation. When I use fs:posix as dict for acl_shared_dict, like in Dovecot wiki (https://wiki.dovecot.org/SharedMailboxes/ClusterSetup) doveadm-server crash with error: # doveadm acl set -u USERNAME FOLDER user=DEST_USERNAME lookup read write-seen doveadm(USERNAME): Panic: file dict-fs.c: line 127 (fs_dict_iterate_init): assertion failed: ((flags & DICT_ITERATE_FLAG_RECURSE) == 0) doveadm(USERNAME): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x9f3de) [0x7f0e4a4b23de] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f0e4a4b244a] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0e4a44377c] -> /usr/lib64/dovecot/libdovecot.so.0(+0x31688) [0x7f0e4a444688] -> /usr/lib64/dovecot/libdovecot.so.0(dict_iterate_init_multiple+0x4d) [0x7f0e4a47cadd] -> /usr/lib64/dovecot/libdovecot.so.0(dict_iterate_init+0x29) [0x7f0e4a47cb89] -> /usr/lib64/dovecot/lib01_acl_plugin.so(acl_lookup_dict_rebuild+0x3e1) [0x7f0e49a40371] -> /usr/lib64/dovecot/lib01_acl_plugin.so(acl_backend_vfile_acllist_rebuild+0x488) [0x7f0e49a3dd18] -> /usr/lib64/dovecot/lib01_acl_plugin.so(acl_backend_vfile_object_update+0x3c7) [0x7f0e49a3e867] -> /usr/lib64/dovecot/lib01_acl_plugin.so(acl_mailbox_update_acl+0x68) [0x7f0e49a41e28] -> /usr/lib64/dovecot/doveadm/lib10_doveadm_acl_plugin.so(+0x2c11) [0x7f0e48da1c11] -> /usr/lib64/dovecot/doveadm/lib10_doveadm_acl_plugin.so(+0x3060) [0x7f0e48da2060] -> doveadm(+0x2b41c) [0x556f1280b41c] -> doveadm(+0x2c01a) [0x556f1280c01a] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x23b) [0x556f1280ce7b] -> doveadm(doveadm_cmd_run_ver2+0x50c) [0x556f1281c73c] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x556f1281c7d7] -> doveadm(main+0x1e4) [0x556f127fb944] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f0e4a071c05] -> doveadm(+0x1bd35) [0x556f127fbd35] Aborted Attached coredump and configuration. I'm not a programmer, but seems that assert is raised by 'fs_dict_iterate_init' function inside 'src/lib-dict-extra/dict-fs.c': static struct dict_iterate_context * fs_dict_iterate_init(struct dict *_dict, const char *const *paths, enum dict_iterate_flags flags) { ... /* these flags are not supported for now */ i_assert((flags & DICT_ITERATE_FLAG_RECURSE) == 0); ... because it is called by 'acl_lookup_dict_iterate_read' function in file 'src/plugins/acl/acl-lookup-dict.c' static void acl_lookup_dict_iterate_read(struct acl_lookup_dict_iter *iter) { ... dict_iter = dict_iterate_init(iter->dict->dict, prefix, DICT_ITERATE_FLAG_RECURSE); ... with DICT_ITERATE_FLAG_RECURSE set. Same problem also with Dovecot 2.3.0. Thanks, Marco -- Marco Giunta - ITCS SysAdmin Via Bonomea, 265 34136 - Trieste, Italy Tel: +39-040-3787-503 Fax: +39-040-3787-244

4 6

Is is possible to log TLS client versions
by Götz Reinicke 13 Dec '19

13 Dec '19

Hi, is it possible to log the version of TLS a clients is using to connect to dovecot? I’v not found any switch to do that. Thanks and regards . Götz

2 2

CVE-2019-19722: Critical vulnerability in Dovecot
by Aki Tuomi 13 Dec '19

13 Dec '19

Open-Xchange Security Advisory 2019-12-13 Product: Dovecot IMAP/POP3 Server Vendor: OX Software GmbH Internal reference: DOV-3719 Vulnerability type: NULL Pointer Dereference (CWE-476) Vulnerable version: 2.3.9 Vulnerable component: push notification driver Report confidence: Confirmed Solution status: Fixed by Vendor Fixed version: 2.3.9.1 Researcher credits: Frederik Schwan, Michael Stilkerich Vendor notification: 2019-12-10 Solution date: 2019-12-12 Public disclosure: 2019-12-13 CVE reference: CVE-2019-19722 CVSS: 5.3 (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L/E:F/RL:O/RC:C) Vulnerability Details: Mail with group address as sender will cause a signal 11 crash in push notification drivers. Group address as recipient can cause crash in some drivers. Risk: Repeated delivery attempts are made for the problematic mail, causing queueing in MTA. Steps to reproduce: 1. Configure dovecot with push notifications enabled, such as OX push notification driver. This can also be observed with 3rd party plugin XAPS. 2. Send mail a group address as sender Solution: Operators should update to the latest Patch Release.

2 1

Dovecot 2.3.9 - lmtp crashes with Signal 11
by Michael Stilkerich 13 Dec '19

13 Dec '19

Hello, since the upgrade from 2.3.8 to 2.3.9 (using the Ubuntu 18.04 packages from dovecot.org) lmtp crashes for me for some mails. Currently I have three pending mails in my postfix deferred queue since the upgrade a couple of days ago. I did not observe these issues with 2.3.8. The backtrace from one of the coredumps: Reading symbols from /usr/lib/dovecot/lmtp...Reading symbols from /usr/lib/debug/.build-id/f3/3a5089463b1234cbcf90bf10033d1dd5613821.debug...done. done. [New LWP 1554] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/lmtp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 decode_address_header (pool=pool@entry=0x560631ad6d10, hdr=0x560631add4c8 "", address_r=address_r@entry=0x560631ad7090, name_r=name_r@entry=0x560631ad7098) at push-notification-event-message-common.c:20 20 push-notification-event-message-common.c: No such file or directory. (gdb) bt #0 decode_address_header (pool=pool@entry=0x560631ad6d10, hdr=0x560631add4c8 "", address_r=address_r@entry=0x560631ad7090, name_r=name_r@entry=0x560631ad7098) at push-notification-event-message-common.c:20 #1 0x00007f3f37955fbb in decode_address_header (name_r=0x560631ad7098, address_r=0x560631ad7090, hdr=<optimized out>, pool=0x560631ad6d10) at push-notification-event-message-common.c:62 #2 push_notification_message_fill (mail=mail@entry=0x560631adc088, pool=0x560631ad6d10, event_flags=(PUSH_NOTIFICATION_MESSAGE_HDR_FROM | PUSH_NOTIFICATION_MESSAGE_HDR_TO | PUSH_NOTIFICATION_MESSAGE_HDR_SUBJECT | PUSH_NOTIFICATION_MESSAGE_HDR_DATE | PUSH_NOTIFICATION_MESSAGE_BODY_SNIPPE$), from=<optimized out>, to=<optimized out>, subject=<optimized out>, date=0x560631ad7050, date_tz=0x560631ad7058, message_id=0x560631ad7078, flags=0x560631ad706c, flags_set=0x560631ad7068, keywords=0x560631ad7070, snippet=0x560631ad7060, ext=0x560631ad7080) at push-notification-event-message-common.c:62 #3 0x00007f3f37955a41 in push_notification_event_messagenew_event (ptxn=0x560631ad6d38, ec=0x560631ad6fe0, msg=0x560631ad7010, mail=0x560631adc088) at push-notification-event-messagenew.c:83 #4 0x00007f3f379571bd in push_notification_trigger_msg_save_new (txn=0x560631ad6d38, mail=0x560631adc088, msg=0x560631ad7010) at push-notification-triggers.c:138 #5 0x00007f3f383f52f3 in notify_contexts_mail_save (mail=0x560631adc088) at notify-plugin.c:62 #6 0x00007f3f383f65b8 in notify_copy (ctx=0x560631ad7890, mail=0x560631a98b18) at notify-storage.c:104 #7 0x00007f3f3860873d in quota_copy (ctx=0x560631ad7890, mail=0x560631a98b18) at quota-storage.c:302 #8 0x00007f3f39f91e32 in mailbox_copy_int (_ctx=<optimized out>, mail=0x560631a98b18) at mail-storage.c:2759 #9 0x00007f3f3641907f in ?? () from /usr/lib/dovecot/libdovecot-sieve.so.0 #10 0x00007f3f3640e64c in ?? () from /usr/lib/dovecot/libdovecot-sieve.so.0 #11 0x00007f3f3640f11b in sieve_result_implicit_keep () from /usr/lib/dovecot/libdovecot-sieve.so.0 #12 0x00007f3f364226e1 in sieve_multiscript_finish () from /usr/lib/dovecot/libdovecot-sieve.so.0 #13 0x00007f3f3668e488 in ?? () from /usr/lib/dovecot/modules/lib90_sieve_plugin.so #14 0x00007f3f3a2a260d in mail_do_deliver (storage_r=0x7ffedf944b40, ctx=0x7ffedf944c30) at mail-deliver.c:542 #15 mail_deliver (ctx=ctx@entry=0x7ffedf944c30, storage_r=storage_r@entry=0x7ffedf944b40) at mail-deliver.c:592 #16 0x000056063169c0e1 in lmtp_local_default_deliver (client=0x560631a5e898, lrcpt=<optimized out>, cmd=<optimized out>, trans=<optimized out>, lldctx=0x7ffedf944e70) at lmtp-local.c:593 #17 0x000056063169c8cf in lmtp_local_deliver (local=0x560631a849b0, local=0x560631a849b0, session=0x560631a9d748, src_mail=0x560631a98b18, llrcpt=0x560631a7f600, trans=0x560631a7fab8, cmd=0x560631a7f088) at lmtp-local.c:530 #18 lmtp_local_deliver_to_rcpts (session=0x560631a9d748, trans=0x560631a7fab8, cmd=0x560631a7f088, local=0x560631a849b0) at lmtp-local.c:654 #19 lmtp_local_data (client=client@entry=0x560631a5e898, cmd=cmd@entry=0x560631a7f088, trans=trans@entry=0x560631a7fab8, input=<optimized out>) at lmtp-local.c:730 #20 0x000056063169b0cf in client_default_cmd_data (client=0x560631a5e898, cmd=0x560631a7f088, trans=0x560631a7fab8, data_input=0x560631a83c00, data_size=<optimized out>) at lmtp-commands.c:275 #21 0x000056063169ae6f in cmd_data_finish (trans=0x560631a7fab8, cmd=0x560631a7f088, client=0x560631a5e898) at lmtp-commands.c:165 #22 cmd_data_continue (conn_ctx=0x560631a5e898, cmd=0x560631a7f088, trans=0x560631a7fab8) at lmtp-commands.c:213 #23 0x00007f3f39bfa2c7 in cmd_data_do_handle_input (cmd=0x560631a7f088) at smtp-server-cmd-data.c:285 #24 cmd_data_handle_input (cmd=0x560631a7f088) at smtp-server-cmd-data.c:333 #25 0x00007f3f39ca42af in io_loop_call_io (io=0x560631a7d8e0) at ioloop.c:718 #26 0x00007f3f39ca5c8c in io_loop_handler_run_internal (ioloop=ioloop@entry=0x560631a23fd0) at ioloop-epoll.c:222 #27 0x00007f3f39ca43c0 in io_loop_handler_run (ioloop=<optimized out>) at ioloop.c:770 #28 0x00007f3f39ca45e8 in io_loop_run (ioloop=0x560631a23fd0) at ioloop.c:743 #29 0x00007f3f39c124b3 in master_service_run (service=0x560631a23e60, callback=<optimized out>) at master-service.c:809 #30 0x0000560631699b45 in main (argc=<optimized out>, argv=<optimized out>) at main.c:169 I can provide one of the mails causing the crash if helpful (they are all spam). Best regards, Michael

2 7

Dovecot v2.3.9.1 released
by Aki Tuomi 13 Dec '19

13 Dec '19

Hi all! We are pleased to release v2.3.9.1 of Dovecot. Please find it from locations below https://dovecot.org/releases/2.3/dovecot-2.3.9.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.9.1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot --- * CVE-2019-19722: Mails with group addresses in From or To fields caused crash in push notification drivers. --- Aki Tuomi Open-Xchange oy

1 0

Dovecot auth crashing??
by Odhiambo Washington 13 Dec '19

13 Dec '19

Dovecot-2.3.9 I am seeing a lot of the following on my logs: Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 09:16:25 auth: Warning: Event 0x827d6e20 leaked (parent=0x827d4220): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x827d6420 leaked (parent=0x827d4820): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x82780c20 leaked (parent=0x827d6220): auth-request.c:878 Dec 13 09:16:25 auth: Warning: Event 0x827d6c20 leaked (parent=0x827d4220): auth-request.c:115 Dec 13 09:16:25 auth: Warning: Event 0x827d4220 leaked (parent=0x827d6a20): auth-request.c:114 Dec 13 09:16:25 auth: Warning: Event 0x827d6a20 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 09:16:25 auth: Warning: Event 0x827d4c20 leaked (parent=0x827d4820): auth-request.c:115 Dec 13 09:16:25 auth: Warning: Event 0x827d4820 leaked (parent=0x827fe620): auth-request.c:114 Dec 13 09:16:25 auth: Warning: Event 0x827fe620 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 09:16:25 auth: Warning: Event 0x827ff420 leaked (parent=0x827d6220): auth-request.c:115 Dec 13 09:16:25 auth: Warning: Event 0x827d6220 leaked (parent=0x82780e20): auth-request.c:114 Dec 13 09:16:25 auth: Warning: Event 0x82780e20 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 11:27:29 master: Warning: Killed with signal 15 (by pid=9326 uid=0 code=kill) Dec 13 11:27:37 master: Warning: Killed with signal 15 (by pid=16518 uid=0 code=kill) Dec 13 11:27:38 auth: Error: net_connect_unix(auth-worker) failed: No such file or directory Dec 13 11:27:39 auth: Error: net_connect_unix(auth-worker) failed: No such file or directory Dec 13 11:27:59 auth: Error: net_connect_unix(/var/run/dovecot//stats-writer) failed: No such file or directory Dec 13 11:27:59 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 11:27:59 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 11:27:59 auth: Warning: Event 0x82781a20 leaked (parent=0x827d4620): auth-request.c:878 Dec 13 11:27:59 auth: Warning: Event 0x827d4220 leaked (parent=0x827d4820): auth-request.c:878 Dec 13 11:27:59 auth: Warning: Event 0x82780e20 leaked (parent=0x827d4620): auth-request.c:115 Dec 13 11:27:59 auth: Warning: Event 0x827d4620 leaked (parent=0x827d0820): auth-request.c:114 Dec 13 11:27:59 auth: Warning: Event 0x827d0820 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 11:27:59 auth: Warning: Event 0x82781220 leaked (parent=0x827d4820): auth-request.c:115 Dec 13 11:27:59 auth: Warning: Event 0x827d4820 leaked (parent=0x827d0c20): auth-request.c:114 Dec 13 11:27:59 auth: Warning: Event 0x827d0c20 leaked (parent=0x0): auth-client-connection.c:338 Dec 13 11:28:07 auth: Warning: Timeout leak: 0x105fb00 (auth-request-handler.c:584) Dec 13 11:28:07 auth: Warning: Event 0x82780c20 leaked (parent=0x82781c20): auth-request.c:878 Dec 13 11:28:07 auth: Warning: Event 0x82781e20 leaked (parent=0x82781c20): auth-request.c:115 Dec 13 11:28:07 auth: Warning: Event 0x82781c20 leaked (parent=0x82781a20): auth-request.c:114 Dec 13 11:28:07 auth: Warning: Event 0x82781a20 leaked (parent=0x0): auth-client-connection.c:338 -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 "Oh, the cruft.", grep ^[^#] :-)

1 0

dovecot update from 2.1.16 to 2.2.36.4 but I have a trouble.
by iriya＠peach.ocn.ne.jp 13 Dec '19

13 Dec '19

Hi,I have a troble and can not resolve it. Please help me. I updated dovecot from 2.1.16 to 2.2.36.4. As a result, I had a client who could not access via imap. The client showed his logs (- folder not exists:INBOX ) I did not change dovecot config files. So I searched a difference between 2.1.16 and 2.2.36.4, I discovered . Please refer below results. [2.1.16] a03 list "" "*" * LIST (\HasChildren) "." "INBOX" * LIST (\HasNoChildren) "." "INBOX.Drafts" * LIST (\HasNoChildren) "." "INBOX.Sent" * LIST (\HasNoChildren) "." "INBOX.Spam" * LIST (\HasNoChildren) "." "INBOX.Trash" [2.2.36.4] a03 list "" "*" * LIST (\HasChildren) "." INBOX * LIST (\HasNoChildren) "." INBOX.Drafts * LIST (\HasNoChildren) "." INBOX.Sent * LIST (\HasNoChildren) "." INBOX.Spam * LIST (\HasNoChildren) "." INBOX.Trash For example, I noticed INBOX and "INBOX". 2.2.36.4 dovecot is no [""]. What should I do?

2 1

v2.2.36 to v2.3.8 maildirlock bug
by lty＠cndns.com 12 Dec '19

12 Dec '19

Dear all, Dovecot upgraded from v2.2.36 to v2.3.8 There is no problem with the configuration, but the lock directory seems to have an error. [root@spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1 Panic: BUG: No IOs or timeouts set. Not waiting for infinity. 19276[root@spam dovecot]# Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xe227a) [0x7f1cb567a27a] -> /usr/lib64/dovecot/libdovecot.so.0(+0xe2321) [0x7f1cb567a321] -> /usr/lib64/dovecot/libdovecot.so.0(+0x40f31) [0x7f1cb55d8f31] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf93b4) [>xrf1cb56913b4] -> /usr/ Lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x28) [0x7f1cb5693918] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5c) [0x7f1cb5691aac] -> /usr/lib64/dovecot/libdovecot. So.0(io_loop_run+0x38) [0x7f1cb5691cc8] -> /usr/libexec/dovecot/maildirlock(main+0x242) [0x7f1cb5b522c2] -> /lib64/libc.so.6(__libc_start_main+0x100) [0x7f1cb5222d20] -> / Usr/libexec/dovecot/maildirlock(+0xfa9) [0x7f1cb5b51fa9] After google seems to be a bug, this is the address Https://bugs.gentoo.org/682498 If this is not fixed, we are temporarily unable to upgrade to use the new version. Will the next version be fixed? We are looking forward to seeing that we have returned v2.2.36

4 5