October 2021 - dovecot

2.3.17 - breaks with fts-xapian.
by Juan Felipe Arjona 01 Nov '21

01 Nov '21

Hello: I just upgraded my Debian server with dovecot 2.3.17, and it breaks when using the plugin fts-xapian. Apparently is a bug in Dovecot, please see: https://github.com/grosjo/fts-xapian/issues/99 Thanks, Juan

3 2

Errors after freebsd upgrade
by Hanns Mattes 01 Nov '21

01 Nov '21

Hi, after upgrading Freebsd from ports dovecot is throwing the following error Oct 30 18:04:15 freebsd dovecot[59232]: doveadm(xxx(a)example.com)<84061><S3CoJf9sfWFdSAEAUmejdw>: Fatal: master: service(doveadm): child 84061 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service doveadm { drop_priv_before_exec=yes }) I (surely) may have missed something while upgrading (I've learned a lot about backup/snapshot-strategies with zfs, but to late to apply). How can I debug the erro? Regards Hanns

2 1

Design Check
by Felix Ingram 31 Oct '21

31 Oct '21

Hello all, I'm building a mail system and would like to check whether my design is feasible. I'm fairly certain that it is but I think I don't have the right words and concepts lined up properly in my head. The end system will provide temporary/disposable email addresses that can be accessed by multiple people. People would be able to send email to addresses that match the following format: user1(a)foobar.mydomain.com user2(a)foobar.mydomain.com user1(a)barbaz.mydomain.com user2(a)barbaz.mydomain.com I would like all emails to the "foobar" subdomain to end up in their own mailbox and all emails to the "barbaz" subdomain to go to their own mailbox. (I think that means I need a foobar and barbaz user on Dovecot). Users of the system should be able to see all of the emails, including the original addresses they were sent to. e.g. user1(a)foobar.mydomain.com and user2(a)foobar.mydomain.com both get delivered to the "foobar" mailbox, and users can see all emails, including that they were sent to "user1" and "user2" The users of the system would be able to access any of the foobar, barbaz, etc mailboxes - I believe that means that they would need to be set as master users. I will be creating a web interface for users to get/set their credentials, so can add those users on an adhoc basis, but I will need to have the "foobar", "barbaz", etc users created whenever an email arrives (we won't know ahead of time). The plan is to have postfix accepting the emails before passing them to Dovecot. I don't believe postfix needs to do much processing but that this would be the place to transform the address into the correct user/mailbox name. So my questions are: 1. Does the above sound reasonable? 2. Can Dovecot auto-create users as needed? 3. Will I be able to preserve the original email? 4. Are master users the right approach? There is no strong requirement for privacy between mailboxes - there is no issue with one user being able to read all email. There is also no requirement to be able to send email but that is a feature request for the future - we would want people to be able to send as the original address when that's implemented. Any pointers gratefully received. Thanks in advance, Felix

4 9

v2.3.17 - dsync says invalid option -- E
by Daniel J. Luke 31 Oct '21

31 Oct '21

Hello, I've got some scripts that archive off mail that stopped working with 2.3.17. Specifically this worksin 2.3.16: sudo -n /usr/local/bin/dsync -u dluke -m Sent -o mail_location=mbox:~/tmp/ mirror maildir:~/Maildir/ but fails on 2.3.17 with the following error message: dsync: invalid option -- E -- Daniel J. Luke

3 5

Re: Dovecot 2.3.17 can not start - too many parameters
by Robert Nowotny 29 Oct '21

29 Oct '21

Michael, it seems the rumors are right. After shortening the file /etc/ssl/ca-certificates.crt to one entry, it works. Of course this is not a solution, so a fix will be needed. I use the "/etc/ssl/certs/ca-certificates.crt" which is included with Ubuntu impish yours sincerely Robert Am 29.10.2021 um 21:09 schrieb Michael Kliewe: Hi, I have heard rumors that this happens when you provide a CA bundle file which is big. If you just provide a single CA file it works. Something has changed there, maybe the developers have more details about this change. King regards Michael Am 29.10.2021 um 19:25 schrieb Robert Nowotny: Dovecot 2.3.17 can not start - too many parameters. but the same config is working on 2.3.16 (and for a long time already ...) started via systemd unit file : ================== [Unit] Description=Dovecot IMAP/POP3 email server Documentation=man:dovecot(1) Documentation=http://wiki2.dovecot.org/ After=local-fs.target network.target dnsmasq.service NetworkManager-wait-online.service network-online.target Requires=network.target network-online.target dnsmasq.service local-fs.target [Service] Type=forking ExecStart=/usr/local/sbin/dovecot -c /etc/dovecot/dovecot.conf PIDFile=/usr/local/var/run/dovecot/master.pid ExecReload=/usr/local/bin/doveadm reload ExecStop=/usr/local/bin/doveadm stop PrivateTmp=true NonBlocking=yes LimitNOFILE=8192 [Install] WantedBy=multi-user.target ================== log: Oct 29 18:48:58 lxc-imap dovecot[1781]: doveconf: Fatal: execvp(/usr/local/sbin/dovecot) failed: Argument list too long Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Control process exited, code=exited, status=89/n/a Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Failed with result 'exit-code'. but when I run doveconf -n, it is working under 2.3.17 I needed to revert to version 2.3.16 to send this email ;-) running on Ubuntu impish yours sincerely Robert Nowotny Rotek GmbH

1 0

Dovecot 2.3.17 can not start - too many parameters
by Robert Nowotny 29 Oct '21

29 Oct '21

Dovecot 2.3.17 can not start - too many parameters. but the same config is working on 2.3.16 (and for a long time already ...) started via systemd unit file : ================== [Unit] Description=Dovecot IMAP/POP3 email server Documentation=man:dovecot(1) Documentation=http://wiki2.dovecot.org/ After=local-fs.target network.target dnsmasq.service NetworkManager-wait-online.service network-online.target Requires=network.target network-online.target dnsmasq.service local-fs.target [Service] Type=forking ExecStart=/usr/local/sbin/dovecot -c /etc/dovecot/dovecot.conf PIDFile=/usr/local/var/run/dovecot/master.pid ExecReload=/usr/local/bin/doveadm reload ExecStop=/usr/local/bin/doveadm stop PrivateTmp=true NonBlocking=yes LimitNOFILE=8192 [Install] WantedBy=multi-user.target ================== log: Oct 29 18:48:58 lxc-imap dovecot[1781]: doveconf: Fatal: execvp(/usr/local/sbin/dovecot) failed: Argument list too long Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Control process exited, code=exited, status=89/n/a Oct 29 18:48:58 lxc-imap systemd[1]: dovecot.service: Failed with result 'exit-code'. but when I run doveconf -n, it is working under 2.3.17 I needed to revert to version 2.3.16 to send this email ;-) running on Ubuntu impish yours sincerely Robert Nowotny Rotek GmbH

2 1

Dovecot version 2.3.17 - dovadm user fail (LDAP)
by Günther J. Niederwimmer 29 Oct '21

29 Oct '21

Hello Oracle 8 (Centos) after Update I have Errors in the log ct 29 13:06:45 mx03.xxxxxxxxx.at dovecot[661311]: doveadm(gjn): Error: User doesn't exist Oct 29 13:06:45 mx03.xxxxxxxxxx.at dovecot[661311]: doveadm(baucons): Error: User doesn't exist Oct 29 13:06:45 mx03.xxxxxxxxxx.at dovecot[661311]: doveadm(ulrike): Error: User doesn't exist but with doveadm user '*' gjn ulrike baucons This is a Problem on all my 3 system? only one is working correct this is a centos 7 Server -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

2 2

Dovecot version 2.3.17 - mail replication stopped working
by Daniel Botting 29 Oct '21

29 Oct '21

Hi, We upgraded to Dovecot 2.3.17 today and mail replication has stopped working as expected, the error in mail.err is: Oct 28 10:27:44 hostname dovecot: imap-login: Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: No such file or directory Oct 28 10:28:47 hostname dovecot: doveadm: Error: sync: invalid option -- 'T' This is constantly repeated afterwards All the files in /var/run/dovecot have last modified time of 10:27 The permissions on both hosts for this file are: srw-rw---- 1 root dovecot 0 Oct 28 10:27 stats-writer= OS: Debian 10.11 Doveconf -n output below: # 2.3.17 (e2aa53df5b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: Linux 4.19.0-18-amd64 x86_64 Debian 10.11 # Hostname: mailserver fqdn auth_verbose = yes default_vsz_limit = 0 doveadm_password = # hidden, use -P to show it first_valid_gid = 8 first_valid_uid = 8 last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_gid = 8 mail_location = maildir:~/Maildir mail_plugins = " notify replication" mail_uid = 8 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 index ihave duplicate mime foreverypart extracttext editheader imapflags 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-ldap.conf.ext driver = ldap } plugin { mail_replica = tcps:fqdn:port number sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +editheader +imapflags } postmaster_address = postmaster@ourdomain protocols = " imap sieve pop3" replication_dsync_parameters = -d -N -l 15 -U -T 10 replication_max_conns = 24 service aggregator { fifo_listener replication-notify-fifo { user = mail } unix_listener replication-notify { user = mail } } service auth { unix_listener /var/run/dovecot-exim-bridge { mode = 0660 user = Debian-exim } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 512 process_min_avail = 4 service_count = 1 } service imap { process_limit = 1024 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 1 service_count = 8 vsz_limit = 256 M } service managesieve { process_limit = 1024 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_cert = </ssl cert path ssl_cipher_list = ALL:!LOW:!SSLv2:!EXP:!aNULL ssl_client_ca_dir = /etc/ssl/certs ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap override_fields = home=/var/mail/%u uid=mail gid=mail } protocol lda { mail_plugins = " notify replication sieve" } protocol imap { mail_max_userip_connections = 32 mail_plugins = " notify replication" } protocol sieve { mail_max_userip_connections = 10 managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 64 k } Best regards Daniel

2 4

Re: [EXT] Re: Dovecot v2.3.17 released
by Frank Elsner 28 Oct '21

28 Oct '21

On Thu, 28 Oct 2021 19:17:40 +0300 (EEST) Aki Tuomi wrote: > > > On 28/10/2021 19:10 Frank Elsner <frank.elsner(a)mailbox.org> wrote: > > > > > > On Thu, 28 Oct 2021 17:32:28 +0300 (EEST) Aki Tuomi wrote: > > > > [ ... ] > > > > > I guess you are using systemd-coredump, so try > > > > > > coredumpctl dump -o core /usr/libexec/dovecot/imap { ... ] > In the directory you ran that command, there will be now a file called 'core'. Can you now do: > > gdb /usr/libexec/dovecot/imap core > bt full Hi Aki, I hope to deliver the requested info with this output (gdb) bt full #0 fts_user_autoindex_exclude (box=<optimized out>, box@entry=0x559500fdd138) at fts-user.c:347 fuser = <optimized out> #1 0x00007f50d8f623b6 in fts_mailbox_allocated (box=0x559500fdd138) at fts-storage.c:806 flist = <optimized out> v = 0x559500fdd7b8 fbox = 0x559500fdd918 #2 0x00007f50d942bd1c in hook_mailbox_allocated (box=box@entry=0x559500fdd138) at mail-storage-hooks.c:256 _data_stack_cur_id = 5 _foreach_end = 0x559500fce758 _foreach_ptr = 0x559500fce740 hooks = 0x7f50d8f90b40 <fts_mail_storage_hooks> ctx = 0x559500fde558 #3 0x00007f50d9426f11 in mailbox_alloc (list=0x559500fd40c8, vname=vname@entry=0x559500f87620 "Administration", flags=flags@entry=0) at mail-storage.c:885 _data_stack_cur_id = 4 new_list = 0x559500fd40c8 storage = 0x559500fd48d8 box = 0x559500fdd138 open_error = MAIL_ERROR_NONE errstr = 0x0 __func__ = "mailbox_alloc" #4 0x00005594fffcaae2 in cmd_create (cmd=0x559500fd38b8) at cmd-create.c:40 ns = 0x559500fd3390 --Type <RET> for more, q to quit, c to continue without paging-- mailbox = 0x559500f87620 "Administration" orig_mailbox = <optimized out> box = 0x559500fdc5a0 directory = <optimized out> len = 14 #5 0x00005594fffd8494 in command_exec (cmd=cmd@entry=0x559500fd38b8) at imap-commands.c:201 hook = 0x559500f93580 finished = <optimized out> __func__ = "command_exec" #6 0x00005594fffd64c2 in client_command_input (cmd=<optimized out>) at imap-client.c:1230 client = 0x559500fd2788 command = <optimized out> tag = 0x7f50d9331f3a <p_strdup+74> "]A\\A]\303\061\300\303ff.\017\037\204" name = 0x5594fffea726 "CREATE" ret = <optimized out> __func__ = "client_command_input" #7 0x00005594fffd6574 in client_command_input (cmd=<optimized out>) at imap-client.c:1297 client = 0x559500fd2788 command = <optimized out> tag = 0x559500f9e0e8 "161" name = 0x559500f9e0f0 "CREATE" ret = <optimized out> __func__ = "client_command_input" --Type <RET> for more, q to quit, c to continue without paging-- #8 0x00005594fffd697d in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x559500fd2788) at imap-client.c:1339 No locals. #9 client_handle_input (client=0x559500fd2788) at imap-client.c:1353 _data_stack_cur_id = 3 ret = <optimized out> remove_io = false handled_commands = false __func__ = "client_handle_input" #10 0x00005594fffd6f30 in client_input (client=0x559500fd2788) at imap-client.c:1397 cmd = 0x559500f9b6a8 output = 0x559500fd31f0 bytes = 27 __func__ = "client_input" #11 0x00007f50d9314249 in io_loop_call_io (io=0x559500fd3330) at ioloop.c:737 ioloop = 0x559500f8fe70 t_id = 2 __func__ = "io_loop_call_io" #12 0x00007f50d93158f2 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x559500f8fe70) at ioloop-epoll.c:222 ctx = 0x559500f925d0 events = <optimized out> event = 0x559500f92650 list = 0x559500f9b690 --Type <RET> for more, q to quit, c to continue without paging-- io = <optimized out> tv = {tv_sec = 1799, tv_usec = 999057} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = 0 call = <optimized out> __func__ = "io_loop_handler_run_internal" #13 0x00007f50d93142f0 in io_loop_handler_run (ioloop=0x559500f8fe70) at ioloop.c:789 __func__ = "io_loop_handler_run" #14 0x00007f50d93144b0 in io_loop_run (ioloop=0x559500f8fe70) at ioloop.c:762 __func__ = "io_loop_run" #15 0x00007f50d92884f3 in master_service_run (service=0x559500f8fcd0, callback=callback@entry=0x5594fffe4c90 <client_connected>) at master-service.c:863 No locals. #16 0x00005594fffc7f85 in main (argc=<optimized out>, argv=<optimized out>) at main.c:564 set_roots = {0x5594ffff98e0 <smtp_submit_setting_parser_info>, 0x5594ffff9600 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x559500f877f8 "\003", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x5594fffe5640 <login_client_connected>, failure_callback = 0x5594fffe4d60 <login_client_failed>, request_auth_token = true} service_flags = <optimized out> storage_service_flags = (MAIL_STORAGE_SERVICE_FLAG_NO_NAMESPACES | MAIL_STORAGE_SERVICE_FLAG_NO_SSL_CA) --Type <RET> for more, q to quit, c to continue without paging-- username = <optimized out> auth_socket_path = <optimized out> c = <optimized out> error = 0x7fffe05085a8 "" (gdb) By for today, Frank

2 1

Pigeonhole v0.5.17 released
by Aki Tuomi 28 Oct '21

28 Oct '21

We are pleased to release first release candidate for v0.5.14. We have done changes to packaging so please give us any feedback on how it works. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.17.t… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.17.t… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Kind regards, Aki Tuomi Open-Xchange oy --- - duplicate: The Sieve duplicate test is prone to false negatives when the user receives many e-mails concurrently, meaning that duplicate deliveries can still occur. - fileinto: v2.3.16 regression: Sieve delivery crashes if mail is delivered to non-existing and existing folder. - imap-filter-sieve: v2.3.15 regression: The CPU limits on Sieve execution are too easily exceeded in IMAP context (the IMAPSieve and FILTER=SIEVE capabilities). Changed the default to unlimited CPU time for IMAP context, since similar excessive resource usage can be caused by other means as well. The CPU limits on Sieve scripts executed at LDA/LMTP delivery are still enforced by default. - redirect: The Sieve redirect action has protections against users triggering mail loops. Unfortunately, the detection of a redirect mail loop sometimes causes the message to get lost if no other Sieve action is applied that delivers the message somewhere else. - redirect: v2.3.16 regression: With certain Sieve scripts if redirect fails due to temporary failure, the lmtp process may crash after the delivery. Fixes: Panic: file mail-user.c: line 229 (mail_user_deinit): assertion failed: ((*user)->refcount == 1).

3 3