- dovecot - dovecot.org

Is Diffie-Hellman needed?
by dovecot＠ptld.com 13 Jan '22

13 Jan '22

Is Diffie-Hellman needed on a modern new dovecot setup? ssl_dh is empty by default. Both ssl_cert and ssl_key on my setup are pointing to let's encrypt certs. However i see Diffie-Hellman related warnings in logs: dovecot[1073]: imap-login: Error: Diffie-Hellman key exchange requested, but no DH parameters provided. Set ssl_dh=</path/to/dh.pem Am i causing issues for some users by not setting up ssl_dh or is this something being phased out?

4 6

source code doesn't compile
by Ruben Safir 12 Jan '22

12 Jan '22

I downloaded the dovecot source and it doesn't compile. The install script fails in auth because it makes a file and then tries to make a directory over it make[2]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' make[3]: Entering directory '/home/ruben/src/dovecot-2.3.17.1/src/auth' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c auth checkpassword-reply '/usr/local/lib/dovecot' libtool: warning: 'libstats_auth.la' has not been installed in '/usr/local/lib/dovecot/old-stats' libtool: install: /usr/bin/install -c .libs/auth /usr/local/lib/dovecot/auth libtool: install: /usr/bin/install -c .libs/checkpassword-reply /usr/local/lib/dovecot/checkpassword-reply /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' I am running an older version of dovecott and would really like to upgrade it and there is no package for this linux version -- So many immigrant groups have swept through our town that Brooklyn, like Atlantis, reaches mythological proportions in the mind of the world - RI Safir 1998 http://www.mrbrklyn.com DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 http://www.nylxs.com - Leadership Development in Free Software http://www2.mrbrklyn.com/resources - Unpublished Archive http://www.coinhangout.com - coins! http://www.brooklyn-living.com Being so tracked is for FARM ANIMALS and extermination camps, but incompatible with living as a free human being. -RI Safir 2013

7 14

Migrate mail_location
by hello＠reox.at 11 Jan '22

11 Jan '22

Hi! I have a dovecot installation, with the following configuration: mail_home = /var/vmail/%d/%n mail_location = maildir:~ I would like to migrate the mail_location to maildir:~/mail, to get around the issues described in the documentation. But I can not really find a good way to do that. I played around with doveadm sync/backup, but I can only copy everything into a new location (i.e. doveadm sync maildir:~/mail), but this does not really untangle the mail_home and location. My other idea was to migrate the maildir manually, i.e. move the maildir related folders and files (new, cur, tmp, all folders starting with a dot and containing itself {new,cur,tmp}, dovecot.* files, subscriptions file) into the ~/mail folder, but I'm not sure if this is a safe method. Is there any safe method to do this using dovecot tools? If the only way is a offline migration, I'm fine with that. Best, Sebastian

2 3

2.17.1 Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped)
by Salatiel Filho 10 Jan '22

10 Jan '22

Hi, my dovecot 2.17.1 instance is crashing a lot. Quick question: The coredump should contain some private data, am I correct ? Assuming so, should it be posted on a public maillist? Panic: file dsync-ibc.c: line 166 (dsync_ibc_send_mail_request): assertion failed: (request->guid != NULL || request->uid != 0) ... Fatal: master: service(doveadm): child 43879 killed with signal 6 (core dumped) Using gdb/bt over the coredump I get: Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `dovecot/doveadm-server'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 return ret; (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007f612d382db5 in __GI_abort () at abort.c:79 #2 0x00007f612db04485 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at failures.c:459 #3 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:471 #4 0x00007f612dbb10f7 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at failures.c:872 #5 0x00007f612db04126 in i_panic (format=format@entry=0x5641e4c16ba8 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:524 #6 0x00005641e4bcfcb2 in dsync_ibc_send_mail_request (ibc=0x5641e50a5990, request=0x5641e51dcc70) at dsync-ibc.c:166 #7 0x00005641e4bfe0bc in dsync_brain_send_mail_request (brain=0x5641e50a8538) at dsync-brain-mails.c:215 #8 dsync_brain_sync_mails (brain=brain@entry=0x5641e50a8538) at dsync-brain-mails.c:418 #9 0x00005641e4bf9ad8 in dsync_brain_run_real (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:716 #10 dsync_brain_run (changed_r=0x7ffcd2397a47, brain=0x5641e50a8538) at dsync-brain.c:749 #11 dsync_brain_run (brain=0x5641e50a8538, changed_r=0x7ffcd2397a47) at dsync-brain.c:737 #12 0x00005641e4bfa13e in dsync_brain_run_io (context=0x5641e50a8538) at dsync-brain.c:110 #13 0x00005641e4c0b3c3 in dsync_ibc_stream_input (ibc=0x5641e50a5990) at dsync-ibc-stream.c:232 #14 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e5040510) at ioloop.c:737 #15 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f89ce0) at ioloop-epoll.c:222 #16 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f89ce0) at ioloop.c:789 #17 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f89ce0) at ioloop.c:762 #18 0x00005641e4bddafa in cmd_dsync_run_remote (user=<optimized out>, user=<optimized out>) at doveadm-dsync.c:496 #19 cmd_dsync_run (_ctx=0x5641e4f89fe8, user=<optimized out>) at doveadm-dsync.c:703 #20 0x00005641e4bdfc26 in doveadm_mail_next_user (ctx=0x5641e4f89fe8, error_r=0x7ffcd2397de8) at doveadm-mail.c:462 #21 0x00005641e4be0d74 in doveadm_mail_cmd_exec (wildcard_user=0x0, ctx=0x5641e4f89fe8) at doveadm-mail.c:654 #22 doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:983 #23 0x00005641e4bf17c7 in doveadm_cmd_run_ver2 (argc=argc@entry=10, argv=argv@entry=0x5641e4fa3788, cctx=cctx@entry=0x7ffcd2397f40) at doveadm-cmd.c:465 #24 0x00005641e4bf5d1a in doveadm_cmd_server_run_ver2 (cctx=0x7ffcd2397f40, argv=0x5641e4fa3788, argc=10, conn=0x5641e4f81328) at client-connection-tcp.c:187 #25 doveadm_cmd_handle (cctx=0x7ffcd2397f40, argv=<optimized out>, argc=<optimized out>, cmd_name=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:214 #26 client_handle_command (args=<optimized out>, conn=0x5641e4f81328) at client-connection-tcp.c:284 #27 client_connection_tcp_input (conn=0x5641e4f81328) at client-connection-tcp.c:436 #28 0x00007f612dbc78ad in io_loop_call_io (io=0x5641e4f88ee0) at ioloop.c:737 #29 0x00007f612dbc8f19 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x5641e4f3df40) at ioloop-epoll.c:222 #30 0x00007f612dbc7950 in io_loop_handler_run (ioloop=0x5641e4f3df40) at ioloop.c:789 #31 0x00007f612dbc7ad0 in io_loop_run (ioloop=0x5641e4f3df40) at ioloop.c:762 #32 0x00007f612db39287 in master_service_run (service=0x5641e4f3dda0, callback=<optimized out>) at master-service.c:863 #33 0x00005641e4bd09f2 in main (argc=<optimized out>, argv=<optimized out>) at main.c:124 # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17.1 (a1a0b892) # OS: Linux 4.18.0-348.7.1.el8_5.x86_64 x86_64 AlmaLinux release 8.5 (Arctic Sphynx) xfs # Hostname: redacted auth_username_format = %Ln doveadm_password = # hidden, use -P to show it first_valid_uid = 1000 mail_home = /var/spool/imap/%n mail_location = maildir:/var/spool/imap/%n/mail:VOLATILEDIR=/var/spool/imap/%n mail_plugins = " notify replication" 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 namespace { list = children location = maildir:/var/spool/imap/redacted/mail/:INDEXPVT=/var/spool/imap/%n/pub-seen-idx/ mailbox * { autoexpunge = 60 days } prefix = redacted/ separator = / subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = scheme=CRYPT username_format=%n /etc/dovecot/users driver = passwd-file } passdb { args = failure_show_msg=yes dovecot driver = pam } plugin { mail_replica = tcps:10.111.1.1:26 sieve = file:/var/spool/imap/%n/sieve;active=/var/spool/imap/%n/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve.d/ sieve_global = /var/lib/dovecot/sieve.d/ } protocols = imap lmtp sieve replication_dsync_parameters = -d -N -l 60 -U service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = dovecot } unix_listener replication-notify { mode = 0666 user = dovecot } } service doveadm { inet_listener { port = 26 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 user = dovecot } } ssl = required ssl_cert = </etc/ssl/certs/cluster-redacted.crt ssl_key = # hidden, use -P to show it userdb { args = username_format=%n /etc/dovecot/users default_fields = uid=vmail gid=mail home=/var/spool/imap driver = passwd-file } userdb { driver = passwd override_fields = uid=vmail gid=mail home=/var/spool/imap/%n } protocol lmtp { mail_plugins = " notify replication sieve" } protocol imap { ssl_cert = </etc/ssl/certs/redacted.crt ssl_key = # hidden, use -P to show it } Atenciosamente/Kind regards, Salatiel

1 0

Spamassassin fails
by Hans Brage 10 Jan '22

10 Jan '22

Hi! I've been running a server with Dovecot, Sieve, Spamassassin and getmail to handle my emails for several years now. Just before christmas I did one of these regular updates and since then I got problems with spamassassin. Quite a lot of spam is not been filtered out. I can see a lot of errors like these in the mail-log. spamd: failed to create readable default_prefs: /home/vmail/.spamassassin/user_prefs Vmail is the user that is running my scripts that retrieves email and executes spamc. Any ideas? Regards, Hans

2 3

Dovecot 2.3.17 on FreeBSD 12.2 panic
by Bert JW Regeer 10 Jan '22

10 Jan '22

Hello, I have dovecot 2.3.17 running on FreeBSD 12.2 and it keeps panicking: Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Jan 10 03:04:07 strida dovecot[55198]: imap(xistence(a)0x58.com)<56382><dx4KlzHVQecmAQKCQwA50VytdgLnsQSr>: Fatal: master: service(imap): child 56382 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps) Ignore the core not dumped, this is happening over and over, and I got one process to core dump: # lldb /usr/local/libexec/dovecot/imap -c imap.core (lldb) target create "/usr/local/libexec/dovecot/imap" --core "imap.core" Core file '/usr/local/vmail/domains/0x58.com/xistence/imap.core' (x86_64) was loaded. (lldb) bt * thread #1, name = 'imap', stop reason = signal SIGABRT * frame #0: 0x0000000011588c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x0000000011587084 libc.so.7`__raise + 52 frame #2: 0x00000000114fd279 libc.so.7`abort + 73 frame #3: 0x00000000113736f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x0000000011371eaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x0000000011372c71 libdovecot.so.0`___lldb_unnamed_symbol864$$libdovecot.so.0 + 33 frame #6: 0x00000000113720bb libdovecot.so.0`i_panic + 187 frame #7: 0x0000000011363d3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000011ef7c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x0000000011ef550f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x000000001113ed5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000000111381e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x0000000001043db4 imap`cmd_select_full + 356 frame #13: 0x000000000104c582 imap`command_exec + 178 frame #14: 0x000000000104ae8a imap`___lldb_unnamed_symbol58$$imap + 58 frame #15: 0x000000000104af91 imap`___lldb_unnamed_symbol58$$imap + 321 frame #16: 0x00000000010499e7 imap`client_handle_input + 471 frame #17: 0x0000000001048178 imap`client_input + 120 frame #18: 0x000000001138ca9f libdovecot.so.0`io_loop_call_io + 111 frame #19: 0x000000001138f45b libdovecot.so.0`io_loop_handler_run_internal + 347 frame #20: 0x000000001138cffa libdovecot.so.0`io_loop_handler_run + 346 frame #21: 0x000000001138ce58 libdovecot.so.0`io_loop_run + 88 frame #22: 0x00000000112f11c8 libdovecot.so.0`master_service_run + 24 frame #23: 0x000000000105a417 imap`main + 1383 frame #24: 0x000000000103bed2 imap`_start + 226 (lldb) ^D I was able to generate a core dump by issue a doveadm command too: (lldb) bt * thread #1, name = 'doveadm', stop reason = signal SIGABRT * frame #0: 0x00000008017b1c2a libc.so.7`__sys_thr_kill + 10 frame #1: 0x00000008017b0084 libc.so.7`__raise + 52 frame #2: 0x0000000801726279 libc.so.7`abort + 73 frame #3: 0x000000080159c6f3 libdovecot.so.0`___lldb_unnamed_symbol873$$libdovecot.so.0 + 147 frame #4: 0x000000080159aeaf libdovecot.so.0`___lldb_unnamed_symbol862$$libdovecot.so.0 + 47 frame #5: 0x000000080159ae71 libdovecot.so.0`default_fatal_handler + 33 frame #6: 0x000000080159b0bb libdovecot.so.0`i_panic + 187 frame #7: 0x000000080158cd3f libdovecot.so.0`array_idx_modifiable_i + 79 frame #8: 0x0000000802236c68 lib20_fts_plugin.so`fts_user_autoindex_exclude + 72 frame #9: 0x000000080223450f lib20_fts_plugin.so`fts_mailbox_allocated + 239 frame #10: 0x0000000801367d5a libdovecot-storage.so.0`hook_mailbox_allocated + 154 frame #11: 0x00000008013611e1 libdovecot-storage.so.0`mailbox_alloc + 449 frame #12: 0x000000080222d5fc lib20_fts_plugin.so`fts_backend_rescan + 60 frame #13: 0x000000080227c1a3 lib20_doveadm_fts_plugin.so`___lldb_unnamed_symbol15$$lib20_doveadm_fts_plugin.so + 99 frame #14: 0x000000000107172f doveadm`___lldb_unnamed_symbol134$$doveadm + 479 frame #15: 0x000000000107252c doveadm`doveadm_cmd_ver2_to_mail_cmd_wrapper + 2492 frame #16: 0x0000000001083c98 doveadm`doveadm_cmd_run_ver2 + 1416 frame #17: 0x00000000010836d7 doveadm`doveadm_cmd_try_run_ver2 + 71 frame #18: 0x0000000001086da3 doveadm`main + 835 frame #19: 0x000000000105fa92 doveadm`_start + 226 (lldb) # doveadm fts rescan -u xistence(a)0x58.com doveadm(xistence(a)0x58.com): Panic: file array.c: line 10 (array_idx_modifiable_i): assertion failed: (idx < array->buffer->used / array->element_size) Abort (core dumped) # dovecot-sysreport Gathering configurations ... grep: The -P option is not supported grep: The -P option is not supported grep: The -P option is not supported Gathering system informations ... Creating archive ... All done! Please report file dovecot-sysreport-strida.0x58.com-1641784164.tar.gz Removing temp files at /tmp/tmp.z5qJkwrW … While reading about fts/fts_squat I came across the page noting it was deprecated. I am running a mail server for myself, and have avoided installing Solr this entire time, but I guess its time to upgrade. In the mean time hopefully this core dump can help figure out what is going on. Bert JW Regeer

2 3

outlook 2019 not working
by postmaster 10 Jan '22

10 Jan '22

Just tried connecting a Windows 10 client with Outlook 2019 but it fail's on both POP3 or IMAP - i knew it was working when i tested it after the server setup about a year ago because i documented everything with screenshots. All other devices we use (Thunderbird, iPhone/iPad, Android devices, RoundCube) are working without any issue, just Outlook won't connect anymore. We don't have much Windows/Outlook experience - any help/hints appreciated. This what i have in the logs, but doesn't see anything that helps: 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:22:25 pop3-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1694, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 1 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl: owner = 0 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: Mailbox INBOX: Mailbox opened because: POP3 INBOX 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Info: Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0, bytes=12/43 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3-login: Debug: SSL alert: close notify 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:22:25 pop3(user1(a)mail-server.cc)<1694><jsRYKzDVCMSyvWci>: Debug: dict(proxy): dict destroyed 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x10, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: before SSL initialization 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server hello 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write certificate 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write server done 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read client key exchange 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS read finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write session ticket 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write change cipher spec 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3/TLS write finished 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully 2022.01.10 02:23:00 imap-login: Info: Login: user=<user1(a)mail-server.cc>, method=PLAIN, rip=178.189.103.34, lip=195.88.238.13, mpid=1696, TLS, TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Loading modules from directory: /usr/lib/dovecot/modules 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib01_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib15_notify_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_mail_log_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_replication_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_virtual_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Module loaded: /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Added userdb setting: plugin/quota_rule=*:bytes=10240000 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Effective uid=5000, gid=5000, home=/srv/vmail/mail-server.cc/user1/ 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict created (uri=file:/srv/vmail/shared-mailboxes.db, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota root: name=User Quota backend=dict args=:proxy::sqluserquota 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=* bytes=10240000 messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Trash bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota rule: root=User Quota mailbox=Sent bytes=+1024000 (10%) messages=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=10240000 (100%) messages=0 reverse=no command=quota-warning 100 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9728000 (95%) messages=0 reverse=no command=quota-warning 95 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=9216000 (90%) messages=0 reverse=no command=quota-warning 90 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota warning: bytes=8192000 (80%) messages=0 reverse=no command=quota-warning 80 user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Quota grace: root=User Quota bytes=1024000 (10%) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota-dict: user=user1(a)mail-server.cc, uri=proxy::sqluserquota, noenforcing=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict created (uri=proxy::sqluserquota, base_dir=/var/run/dovecot) 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/srv/vmail/mail-server.cc/user1/maildir 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: maildir++: root=/srv/vmail/mail-server.cc/user1/maildir, index=, indexpvt=, control=, inbox=/srv/vmail/mail-server.cc/user1/maildir,alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 1 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: Namespace : type=shared, prefix=shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/srv/vmail/%d/%n/maildir:INDEX=~/maildir/shared/%u:CONTROL=~/maildir/shared/%u 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: shared: root=/var/run/dovecot, index=, indexpvt=, control=, inbox=, alt= 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: initializing backend with data: vfile 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: acl username = user1(a)mail-server.cc 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl: owner = 0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: Global ACLs disabled 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: quota: quota_over_flag check: quota_over_script unset - skipping 2022.01.10 02:23:00 imap-login: Debug: SSL error: Connection closed 2022.01.10 02:23:00 imap-login: Debug: SSL alert: close notify 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: acl vfile: file /srv/vmail/mail-server.cc/user1/maildir/dovecot-acl not found 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Info: Disconnected: Connection closed (IDLE running for 0.001 + waiting input for 0.001 secs, 2 B in + 10 B out, state=wait-input) in=11 out=461 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(file): dict destroyed 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): Waiting for dict to finish pending operations 2022.01.10 02:23:00 imap(user1(a)mail-server.cc)<1696><S1ptLTDVEcSyvWci>: Debug: dict(proxy): dict destroyed thx, Alex

2 1

Patch: assertion failed in doveadm fts lookup
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting this patch, which I have been applying locally since I originally posted it. Hopefully it can be considered for inclusion in the official release. It was tested on dovecot 2.3.16 but applies against the latest version 2.3.17.1. This is the "assertion failed" that it addresses doveadm fts lookup -u john(a)voipsupport.it body "text to look for" doveadm(john(a)voipsupport.it): Panic: file mail-storage.c: line 2108 (mailbox_get_open_status): assertion failed: (box->opened) doveadm(john(a)voipsupport.it): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7ff624fa7072] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff624fa718e] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc3b) [0x7ff624fb3c3b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xffc71) [0x7ff624fb3c71] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x5536f) [0x7ff624f0936f] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x3fc31) [0x7ff6250bcc31] -> /usr/local/lib/dovecot/lib21_fts_solr_plugin.so(+0x540d) [0x7ff62244f40d] -> /usr/local/lib/dovecot/lib20_fts_plugin.so(fts_backend_lookup+0x4d) [0x7ff6246b624d] -> /usr/local/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so(+0x2e8c) [0x7ff62240ce8c] -> doveadm(+0x31ded) [0x55f0c7f3aded] -> doveadm(+0x32862) [0x55f0c7f3b862] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x55f0c7f3c6fd] -> doveadm(doveadm_cmd_run_ver2+0x4d8) [0x55f0c7f4d158] -> doveadm(doveadm_cmd_try_run_ver2+0x3a) [0x55f0c7f4d1aa] -> doveadm(main+0x1f6) [0x55f0c7f2b606] -> /lib64/libc.so.6(__libc_start_main+0xd5) [0x7ff624bc8b75] -> doveadm(_start+0x2e) [0x55f0c7f2ba0e] Aborted (core dumped) Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c --- dovecot-2.3.17.1-orig/src/plugins/fts/doveadm-fts.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/doveadm-fts.c 2022-01-09 01:33:23.396342025 +0100 @@ -47,6 +47,14 @@ i_array_init(&result.scores, 16); box = mailbox_alloc(info->ns->list, info->vname, 0); + mailbox_set_reason(box,"fts search"); + if (mailbox_open(box) < 0) { + i_error("Couldn't open mailbox: %s", + mailbox_get_last_internal_error(box, NULL)); + doveadm_mail_failed_error(ctx, MAIL_ERROR_TEMP); + return -1; + } + if (fts_backend_lookup(backend, box, ctx->search_args->args, FTS_LOOKUP_FLAG_AND_ARGS, &result) < 0) { i_error("fts lookup failed"); John

2 1

Non-user logins?
by Ken Wright 09 Jan '22

09 Jan '22

My Dovecot issues continue. Right now I see at least two issues: first, my logs consistently show non-users trying (and failing) to log in, and I'm still unable to log in from my email client (Evolution or Roundcube, either one). I'll post about the second issue later; right now I wonder why I'm getting so many non-users trying to log in. Am I the subject of concerted hacking attacks, or is there something else going on? Some of the attempted logins are more-or-less random names claiming to be @mydomain, but at least one is a username that's really on my server, to wit: Jan 7 22:52:01 grace dovecot: lmtp(776281): Error: lmtp-server: conn unix:pid=776262,uid=117 [3]: rcpt www-data(a)mydomain.com: Failed to lookup user www-data(a)mydomain.com: Internal error occurred. Refer to server log for more information. (Another quick question: which server log should I check?) So, if anyone can tell me what's going on with all these logins, I'd be much obliged! Ken

9 16

Patch: enhancements for solr/tika integration
by John Fawcett 09 Jan '22

09 Jan '22

Hi here's a patch with some enhancements that I am applying locally for solr/tika integration. Hopefully this can be considered for inclusion. I've tested up to 2.3.16 and this patch applies against latest version 2.3.17.1. The contents are: 1. Allow username and password in tika configuration (as is already supported for solr). For example: fts_tika = https://user:password@tika_host:tika_port/tika/tika This means that tika can be more easily located on a different server to dovecot. Locating Solr and Tika on separate servers can isolate the Dovecot server from issues that may happen on Solr or Tika (like out of memory). 2. Introduce an optional configurable limit on the size of emails whose message bodies will be indexed with solr via a new setting fts_max_size, to be put in the plugin section. For example plugin { ... fts_max_size = 2M ... } Message body indexing is skipped for messages that are larger than this setting. 3. Introduce an optional configurable limit on the size of emails whose attachments will be sent to tika for keyword extraction, via a new setting fts_max_size_tika, to be put in the plugin section. For example: plugin { ... fts_max_size_tika = 1M } I noticed that some very large attachments are being sent to tika and these often do not have any useful content to index. For simplicity the check is done on message size not individual or total attachment size. Here's the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-build-mail.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-build-mail.c 2022-01-09 01:33:23.398341998 +0100 @@ -17,6 +17,7 @@ #include "fts-filter.h" #include "fts-api-private.h" #include "fts-build-mail.h" +#include "settings-parser.h" /* there are other characters as well, but this doesn't have to be exact */ #define IS_WORD_WHITESPACE(c) \ @@ -25,6 +26,8 @@ wherever */ #define MAX_WORD_SIZE 1024 +static bool debug = FALSE; + struct fts_mail_build_context { struct mail *mail; struct fts_backend_update_context *update_ctx; @@ -34,6 +37,7 @@ buffer_t *word_buf, *pending_input; struct fts_user_language *cur_user_lang; + bool oversized_tika; }; static int fts_build_data(struct fts_mail_build_context *ctx, @@ -223,7 +227,7 @@ parser_context.user = mail_storage_get_user(storage); parser_context.content_disposition = ctx->content_disposition; - + parser_context.oversized_tika = ctx->oversized_tika; if (fts_parser_init(&parser_context, &ctx->body_parser)) { /* extract text using the the returned parser */ *binary_body_r = TRUE; @@ -496,7 +500,32 @@ bool binary_body; const char *error; int ret; - + uoff_t msg_size; + uoff_t fts_max_size = 0; + uoff_t fts_max_size_tika = 0; + const char * fts_max_size_setting; + const char * fts_max_size_tika_setting; + bool oversized_msg; + bool oversized_tika; + + fts_max_size_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size"); + if (fts_max_size_setting != NULL) { + if (debug) i_debug("fts_max_size %s",fts_max_size_setting); + if (settings_get_size(fts_max_size_setting, &fts_max_size, &error) < 0) { + i_error("%s",error); + fts_max_size = 0; + } + if (debug) i_debug("fts_max_size (value) %"PRIuUOFF_T,fts_max_size); + } + fts_max_size_tika_setting = mail_user_plugin_getenv(update_ctx->backend->ns->user, "fts_max_size_tika"); + if (fts_max_size_tika_setting != NULL) { + if (debug) i_debug("fts_max_size_tika %s",fts_max_size_tika_setting); + if (settings_get_size(fts_max_size_tika_setting, &fts_max_size_tika, &error) < 0) { + i_error("%s",error); + fts_max_size_tika = 0; + } + if (debug) i_debug("fts_max_size_tika (value) %"PRIuUOFF_T,fts_max_size_tika); + } *may_need_retry_r = FALSE; if (mail_get_stream_because(mail, NULL, NULL, "fts indexing", &input) < 0) { if (mail->expunged) @@ -505,10 +534,21 @@ mailbox_get_last_internal_error(mail->box, NULL)); return -1; } - + oversized_msg = FALSE; + oversized_tika = FALSE; + i_stream_get_size(input,TRUE,&msg_size); + if (fts_max_size > 0 && msg_size > fts_max_size) { + i_info("Skipping message body indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size %s",msg_size,fts_max_size_setting); + oversized_msg = TRUE; + } + if (fts_max_size_tika > 0 && msg_size > fts_max_size_tika) { + i_info("Skipping message attachment indexing because size %"PRIuUOFF_T" exceeds setting fts_max_size_tika %s",msg_size,fts_max_size_tika_setting); + oversized_tika = TRUE; + } i_zero(&ctx); ctx.update_ctx = update_ctx; ctx.mail = mail; + ctx.oversized_tika = oversized_tika; if ((update_ctx->backend->flags & FTS_BACKEND_FLAG_TOKENIZED_INPUT) != 0) ctx.pending_input = buffer_create_dynamic(default_pool, 128); @@ -563,7 +603,7 @@ message_decoder_set_return_binary(decoder, TRUE); body_part = TRUE; } else { - if (skip_body) + if (skip_body ||oversized_msg) continue; } @@ -597,7 +637,7 @@ else (void)fts_parser_deinit(&ctx.body_parser, NULL); } - if (ret == 0 && body_part && !skip_body && !body_added) { + if (ret == 0 && body_part && !skip_body && !oversized_msg && !body_added) { /* make sure body is added even when it doesn't exist */ block.data = NULL; block.size = 0; ret = fts_build_body_block(&ctx, &block, TRUE); diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser.h 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser.h 2022-01-09 01:33:23.399341985 +0100 @@ -10,6 +10,7 @@ /* Can't be NULL */ const char *content_type; const char *content_disposition; + bool oversized_tika; }; struct fts_parser_vfuncs { diff -ur dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c --- dovecot-2.3.17.1-orig/src/plugins/fts/fts-parser-tika.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts/fts-parser-tika.c 2022-01-09 01:33:23.400341972 +0100 @@ -57,7 +57,7 @@ tuser = p_new(user->pool, struct fts_parser_tika_user, 1); MODULE_CONTEXT_SET(user, fts_parser_tika_user_module, tuser); - if (http_url_parse(url, NULL, 0, user->pool, + if (http_url_parse(url, NULL, HTTP_URL_ALLOW_USERINFO_PART, user->pool, &tuser->http_url, &error) < 0) { i_error("fts_tika: Failed to parse HTTP url %s: %s", url, error); return -1; @@ -148,6 +148,10 @@ if (tika_get_http_client_url(parser_context->user, &http_url) < 0) return NULL; + if (parser_context->oversized_tika) { + i_info("skipping tika parser due to oversized message"); + return NULL; + } if (http_url->path == NULL) http_url->path = "/"; @@ -159,6 +163,11 @@ http_url->host.name, t_strconcat(http_url->path, http_url->enc_query, NULL), fts_tika_parser_response, parser); + if (http_url->user != NULL) { + http_client_request_set_auth_simple( + http_req, http_url->user, http_url->password); + } + http_client_request_set_port(http_req, http_url->port); http_client_request_set_ssl(http_req, http_url->have_ssl); if (parser_context->content_type != NULL) John

1 0

Patch: safeguard against too large value for uid being sent to solr for single mailbox searches
by John Fawcett 09 Jan '22

09 Jan '22

Hi I'm reposting a patch for solr integration which I have been applying locally. It applies against 2.3.17.1. Dovecot already has a mechanism when doing solr fts searches on multiple mailboxes that prevents a too large value for maximum rows being sent to solr. #define SOLR_MAX_MULTI_ROWS 100000 (defined and used in plugins/fts-solr/fts-backend-solr.c) However on single mailbox searches Dovecot uses the last uid of the mailbox, which can be too large for solr. My suggested patch is to also limit maximum rows to return on single mailbox searches. Here is the patch: diff -ur dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c --- dovecot-2.3.17.1-orig/src/plugins/fts-solr/fts-backend-solr.c 2021-12-03 12:48:47.000000000 +0100 +++ dovecot-2.3.17.1-new/src/plugins/fts-solr/fts-backend-solr.c 2022-01-09 01:33:23.401341959 +0100 @@ -837,7 +837,7 @@ str = t_str_new(256); str_printfa(str, "wt=xml&fl=uid,score&rows=%u&sort=uid+asc&q=%%7b!lucene+q.op%%3dAND%%7d", - status.uidnext); + I_MIN(status.uidnext,SOLR_MAX_MULTI_ROWS)); prefix_len = str_len(str); if (solr_add_definite_query_args(str, args, and_args)) { John

1 0

Can't log in from Evolution or Roundcube
by Ken Wright 09 Jan '22

09 Jan '22

When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream returned no data”. At least to me, that's not particularly informative. Is it any more informative to anyone else? Ken

3 10

Sv: banning
by Sebastian Nielsen 08 Jan '22

08 Jan '22

I would say, lock accounts to for example IP address, ASN or GeoIP. This can be accomplished simply by a custom login handler, which also checks IP against database. And first time users, and those who change country/ISP/IP have to simply logon to a web interface (where 2FA can be required and also Captcha) and add their IPs/ASNs/Geo's. For a larger user base, I would recommend GeoIP and no web interface, save country of first login to database, and subsequent logins must originate from same country. Users that want to reset have to contact support. If you are a web hotel who only sell service to a specific country at all, lock the ports in firewall to that GeoIP. For smaller user base, like 50-100 users, I would recommend locking to ASN and providing a web interface where multiple ASN can be added. So people syncing from mobile and home can succeed. For very small user base, like 10's of users, just plan lock to IP. By connecting IP to accounts, you greatly reduce the attack surface.

1 0

TLS connection closed unexpectedly
by Ken Wright 08 Jan '22

08 Jan '22

I reinstalled Dovecot this evening, because I haven't been able to receive emails recently. After configuring and adjusting for the use of PostfixAdmin, I get the following error message in Evolution:; Failed to open folder. The reported error was "Failed to authenticate: TLS connection closed unexpectedly". Does anyone recognize this error? Ken

6 8

Update from 2.3.16 to 2.3.17 Received invalid SSL certificate: unable to get certificate CRL
by Salatiel Filho 08 Jan '22

08 Jan '22

Hi, after updating from dovecot.x86_64 2:2.3.16-2 to 2:2.3.17.1-1 on AlmaLinux 8 my dovecot replication stopped working. Log is full of Error: doveadm server disconnected before handshake: Received invalid SSL certificate: unable to get certificate CRL: /CN=my.domain.redacted (check ssl_client_ca_* settings?) No configuration has changed on my side. My certificate is a wildcard certificate ( not sure if related ). I am also replicating over tcps. Anyone else facing this issue? Atenciosamente/Kind regards, Salatiel

1 0

Sieve scripts igniored
by Sam R 07 Jan '22

07 Jan '22

Hello, I have an issue with Sieve plugin, I can drive rules remotely with sieve:// myserver.fr:4190/?tls=YES, the rules are well created under /home/vmail/name.firstname, but these are never executed. I have also read https://doc.dovecot.org/configuration_manual/sieve/troubleshooting/, but I don't see any evident mistake. here is my dovecot -n : # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 ext4 # Hostname: mail.xxx.fr auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = login plain gssapi mail_location = maildir:/home/vmail/%n/Maildir/ mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relationa l regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttex t 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 { driver = pam } passdb { driver = pam } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3" service lmtp { executable = lmtp -L unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl = required ssl_cert = </etc/letsencrypt/live/mail.xxx.fr/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_client_ca_file = /etc/letsencrypt/live/mail.xxx.fr/chain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = uid=vmail gid=vmail home=/home/vmail/%u allow_all_users=yes driver = static } userdb { driver = passwd } protocol lmtp { mail_plugins = " sieve" } protocol lda { mail_plugins = " sieve" } Thanks for helping. kind regards. Samuel

3 3

feature-request: make received-header on submission optional or at least drop the ip in it
by dc-ml＠dvl.werbittewas.de 07 Jan '22

07 Jan '22

hi. we're just trying to re-structure a system and want to use dovcots submission-ability. because the github-repository have no entry for any issues at all, we're sending this feature-fequest to this ML. unfortunately there doesn't seem to be any option to drop the received-header at all or at least hide the IP of the user. because the client-ip is covered by GDPR as personal data and so it should never shown to others without a certain reason, we want to hide it, but there's no "submission_add_received_header"-option like for lmtp and it doesn't seem to be any other option to hide this information. maybe this is possible to implement in near future? thanks a lot. best regards d.

8 18

Dovecot fixing maildir message size?
by Grant Keller 07 Jan '22

07 Jan '22

We recently updated dovecot from 2.1.17 to 2.3.10. It used to be when we encountered the following error: Jan 6 15:29:20 d.imapd.sonic.net dovecot: imap(momomo): session=aBd2O/LULMu4F6ia Error: Mailbox INBOX: UID=1: read(/var/spool/mail/07/00/momomo/cur/1510707300.12345_0.a.spam,S=1234:2,) failed: Cached message size larger than expected (1234 > 704, box=INBOX, UID=1) (read reason=) Dovecot would fix the size by renaming the file. Now this doesn't appear to be the case. Was there a change in behaviour, or is there an option I need to enable now to have dovecot auto fix this?

1 0

Re: Error: fts_solr: received invalid uid
by oliver.krone＠snoog.ch 07 Jan '22

07 Jan '22

Hello, I made serveral tests, never had a problemm woth dovecot version 2.3.4 with 2.3.13 things get worse and dovecot crashes. I might have read someting in the release notes of dovecot 2.3.13. that there is a problem. Regards Oliver > On 1/2/22 3:08 PM, John Fawcett wrote: >> unless I'm missing something that doesn't look like the type of query >> dovecot launches - dovecot sends various parameters including the >> request for xml results. The thing that looks odd to me is that the >> results fields should be single values not arrays enclosed in [], ie I >> would have expected >> "uid":21, >> >> instead of >> >> "uid":[21], >> >> I'd be interested to see the equivalent xml output produced by running >> a query that dovecot sends. >> > > This Solr instance is not configured properly for dovecot.? Most of the > fields are configured as multiValued (which is why you see an array > rather than a single value), and the response is JSON.? A Solr instance > that is properly configured for dovecot would return XML, not JSON. > > You're going to want to provide a proper solrconfig.xml and > managed-schema file, restart Solr or reload the core for dovecot, and > do > a full reindex.? At the following URL, you can find the shell script > that I use to do a full reindex: > > https://apaste.info/tK1B > > At the following URL are links to the solrconfig.xml and schema that > are > appropriate for dovecot.? These instructions say to name the schema > file > "schema.xml" ... this will work, as long as Solr has read-write access > to the conf directory so it can rename the file to "managed-schema".? > If > it doesn't, then you should name the file "managed-schema" yourself. > > https://doc.dovecot.org/configuration_manual/fts/solr/ > > Thanks, > Shawn

2 2

Doveadm auth test fails
by Ken Wright 07 Jan '22

07 Jan '22

I've been having trouble logging into my email server (postfix 3.4.13, dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the doveadm auth test, and got the following result: kwright@grace:~$ sudo doveadm auth test me(a)mydomain.com Password: passdb: me(a)mydomain.com auth failed extra fields: user=me(a)mydomain.com I logged in to PostfixAdmin and made sure I was using the correct password, but got exactly the same result afterward. Should I have restarted Dovecot after changing the password? I'm totally confused by this problem; any and all suggestions will be gratefully received! Ken

3 6

Enable push notifications for all users
by Felix Ingram 06 Jan '22

06 Jan '22

Hello all, Is there a way to enable push notifications for all users, rather than having to enable them one by one? My thinking was to set mail_attribute_dict to a static file but I can’t work out what I would need to put in it. (I’ve now realised that that will not allow me to have other attributes to be different per user, but that’s not a real issue with my use case) If a flat file isn’t the answer, then is a SQL dict my best bet? Thanks in advance, Felix

2 4

Re: Expunged message reappeared
by Claudio Corvino 05 Jan '22

05 Jan '22

Hi Alex, thanks for your answer, I think this could be related to Dovecot version in use, in our case it is the same: 2.3.4.1 (f79e8e7e4). It could be useful to know if someone can confirm this assumption so we can try an upgrade to the latest version hoping this could solve our issue. Regards On 07/12/21 08:36, Joelly Alexander wrote: > > Don't have the issue with duplicate logs but same problem with > re-appearing of deleted messages very often in a two node setup with > dsync replication. > Messages sometimes have to be deleted multiple times until they stay > in the thrash folder. > > Running dovecot version 2.3.4.1 (f79e8e7e4) > > When i 'move' messages to the Trash folder they seem to stay there but > when i delete them they usually come back. > > Alex > > On 12/3/21 5:53 PM, Claudio Corvino wrote: >> >> I forgot to mention that sometimes users receive duplicate messages >> and Dovecot log: >> >> Dec 3 10:16:12 xxx dovecot: >> lmtp(xxx@xxx)<13468><OOFDAlXgqWGcNAAAIQnY6g:12>: Warning: >> /mnt/mail-storage-lv0007/xxx/Maildir/dovecot-uidlist: Duplicate file >> entry at line 2072: 1638522075.M489729P12338.xxx,S=5854,W=5943 (uid >> 71164 -> 71166) >> >> Thanks >> >> Regars >> >> On 03/12/21 17:50, Claudio Corvino wrote: >>> >>> Hi, >>> >>> I have two IMAP/LMTP Dovecot server in replica (version 2.3.4.1), I >>> use LDAP/AD for /userdb, /replica is working, but sometimes I get >>> these errors into log: >>> >>> Dec 3 15:47:15 xxx dovecot: imap(xxx)<28251><TOSxmj7SPRYloY5/>: >>> Warning: Maildir /mnt/mail-storage-lv0007/xxx/Maildir: Expunged >>> message reappeared, giving a new UID (old uid=233140, >>> file=1638540323.M588041P27708.xxx,S=84376,W=85507:2,) >>> >>> The user delete the message and then the message reappears into mail >>> client after one second. >>> >>> Does anybody knows how can I fix it? >>> >>> Thanks in advance >>> >>> Regards >>> >>

2 3

how to delete attachment and replace some words in subject
by lujie 05 Jan '22

05 Jan '22

hi, all, I need to filter email as follow rules: 1, delete the attachments; 2, replace some word in subject with code; 3, redirect to other email with the modified subject and original text in body. sieve and exrprograms used in my script. But error in run sieve script while try to set body text , which contains invalid character "cr lf". Thanks. -- Best Regards, Jessica

2 1

Doveadm auth fails
by Ken Wright 05 Jan '22

05 Jan '22

I'm still troubleshooting a faulty email server, and got the following results when I tried doveadm: kwright@grace:/etc/dovecot/conf.d$ doveadm auth lookup me(a)mydomain.com Error: auth-master: passdb lookup(me(a)mydomain.com): Auth PASS lookup failed Error: passdb lookup failed for me(a)mydomain.com kwright@grace:/etc/dovecot/conf.d$ doveadm auth test me(a)mydomain.com Password: Error: auth-client: conn unix:/var/run/dovecot/auth-client: connect(/var/run/dovecot/auth-client) failed: Permission denied (euid=1000(kwright) egid=1000(kwright) missing +r perm: /var/run/dovecot/auth-client, dir owned by 0:0 mode=0755) kwright@grace:/etc/dovecot/conf.d$ ls -la /var/run/dovecot/auth-client srw------- 1 dovecot root 0 Jan 4 19:09 /var/run/dovecot/auth-client I see /var/run/dovecot/auth-client only has read and write permissions for the owner and nothing for anyone else. Is this part of my problem? Ken

2 3

Re: Error: fts_solr: received invalid uid
by oliver.krone＠snoog.ch 04 Jan '22

04 Jan '22

Here is what solr sends to dovecot, the offending uid in this exmaple is '21' { "responseHeader":{ "status":0, "QTime":1, "params":{ "q":"body:Zeitserver"}}, "response":{"numFound":1,"start":0,"numFoundExact":true,"docs":[ { "uid":[21], "box":["2e60f3054059c95fbf580600eb1947e0"], "user":["oliver.krone(a)snoog.ch"], "id":"21/2e60f3054059c95fbf580600eb1947e0/oliver.krone(a)snoog.ch", "body":[" ... "], "hdr":[" ... "], "from":["..."], "subject":["..."], "to":["..."], "_version_":1720682332306800640}] }} Oliver >> I'm using dovecot 2.3.13,? solr 8.x. and roundcube 1.5.1. However when >> I do a search I get the the Error: fts_solr: received invalid uid, >> search results are ok. >> >> Thanks > Presumably one of the uid returned from solr could not be decoded (i.e. > converted to an int). The offending uid should have been printed as > part > of the message. If you need to get more info you could investigate what > is being returned by solr running the exact same query from a browser > if > you're able to retrieve it from the solr log. > > Alternatively you could set rawlog_dir in the fts_solr dovecot settings > and then look at what is being sent back from solr in the .in file that > is logged. > > https://doc.dovecot.org/settings/plugin/fts-solr-plugin/?highlight=fts%20do… > > John

3 2

Client Passdb out
by Ken Wright 03 Jan '22

03 Jan '22

I've been trying to log into Dovecot without success, and this is what I found in /var/log/mail.log: Jan 3 02:47:33 grace dovecot: auth: Debug: client passdb out: FAIL#0111#011user=me(a)mydomain.com Jan 3 02:47:33 grace dovecot: imap-login: Disconnected (auth failed, 1 attempts in 6 secs): user=<me(a)mydomain.com>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.10, TLS, session=<bgBsu6jUhqzAqAEB> I know I provided the correct password, but I'm still having no joy. Ken

2 1

Re: Error: fts_solr: received invalid uid (John Fawcett)
by oliver.krone＠snoog.ch 03 Jan '22

03 Jan '22

Hi John, You are right this was not a dovecot solr query. It is really strange everything seems to work with Dovecot 2.3.4. E.g. search and rebuilding index from scratch using doveadm. As soon as I use version 2.3.13 things are getting wild: dovecot crashed when I re-scan the index using doveadm and search does not work anymore, after re-scan: Panic: file http-client-request.c: line 1240 (http_client_request_send_more): assertion failed: (req->payload_input != NULL) doveadm(krone(a)invectrix.ch): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fc54cace4e2] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fc54cace5fe] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc49b) [0x7fc54cada49b] -> /usr/lib/dovecot/libdovecot.so.0(+0xfc4d1) [0x7fc54cada4d1] -> /usr/lib/dovecot/libdovecot.so.0(+0x53aee) [0x7fc54ca31aee] -> /usr/lib/dovecot/libdovecot.so.0(+0x4aec2) [0x7fc54ca28ec2] -> /usr/lib/dovecot/libdovecot.so.0(http_client_connection_output+0xee) [0x7fc54ca7ebde] -> /usr/lib/dovecot/libdovecot.so.0(+0x122171) [0x7fc54cb00171] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7fc54caeff59] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7fc54caf1592] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7fc54caf0000] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fc54caf01c0] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c4cd) [0x7fc54ca7a4cd] -> /usr/lib/dovecot/libdovecot.so.0(http_client_request_finish_payload+0x2c) [0x7fc54ca7a6dc] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xf243) [0x7fc54c0a6243] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_parser_more+0x25) [0x7fc54c0a5345] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0xbfcf) [0x7fc54c0a2fcf] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_build_mail+0xa27) [0x7fc54c0a3a87] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x11f0b) [0x7fc54c0a8f0b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x2e) [0x7fc54cbf14ae] -> doveadm(+0x3761f) [0x55d18bdbf61f] -> doveadm(+0x31bad) [0x55d18bdb9bad] -> doveadm(+0x32860) [0x55d18bdba860] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x22d) [0x55d18bdbb4ad] -> doveadm(doveadm_cmd_run_ver2+0x4c8) [0x55d18bdcbb88] -> doveadm(doveadm_cmd_try_run_ver2+0x3a) [0x55d18bdcbbda] -> doveadm(main+0x1d0) [0x55d18bdaa450] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7fc54c69fd0a] -> doveadm(_start+0x2a) [0x55d18bdaa92a] and solr: 2022-01-03 00:13:20.829 ERROR (qtp1991278377-21) [ x:dovecot] o.a.s.s.HttpSolrCall null:[com.ctc.wstx.exc.WstxLazyException] com.ctc.wstx.exc.WstxIOException: Early EOF .... Caused by: org.eclipse.jetty.io.EofException: Early EOF at org.eclipse.jetty.server.HttpInput$3.getError(HttpInput.java:1143) at org.eclipse.jetty.server.HttpInput$3.noContent(HttpInput.java:1131) at org.eclipse.jetty.server.HttpInput.read(HttpInput.java:318) Seems like dovecot is sending an empty query? Oliver > > Hi Oliver > > unless I'm missing something that doesn't look like the type of query > dovecot launches - dovecot sends various parameters including the > request for xml results. The thing that looks odd to me is that the > results fields should be single values not arrays enclosed in [], ie I > would have expected > > "uid":21, > > instead of > > "uid":[21], > > I'd be interested to see the equivalent xml output produced by running > a > query that dovecot sends. > > John >

2 2

Can't connect to database
by Ken Wright 03 Jan '22

03 Jan '22

Dovecot has been giving me problems for the past week or so. Today the error log showed me this: Jan 2 13:33:39 grace dovecot: auth-worker(3250): Error: mysql(localhost): Connect failed to database (postfix): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) - waiting for 5 seconds before retry The socket is there, showing full permissions (rwx for owner, group, and rest of the universe) so I can't understand why dovecot can't connect. Is there anyone who can help? Ken

3 3

master: service(imap): child xxxx killed with signal 11
by Lukas Matasovsky 02 Jan '22

02 Jan '22

Dear Maintainer, I have several dovecot installations, all of them stopped working with the upgrade from .16 to .17. Maybe I am missing something, or it's a bug. All I can see is a signal 11 after each login attempt. Attached you can find a sysreport plus a core dump, both from different states of configuration (I reverted the core-dump settings later on) of the same server, but the effect has been the same ever since upgrading. I have other servers that use pam (not mariadb) and local maildirs that show the same behavior. For now, I have downgraded all servers, if needed I could run some more tests. Thank you for checking & cheers, Lukas

2 3

Dovecot Docker Image Volumes
by Thomas Bellebaum 02 Jan '22

02 Jan '22

Hello there and happy new year, I have a question/request regarding the Docker Image hosted at https://hub.docker.com/r/dovecot/dovecot. The Dockerfile itself declares two volumes: - `/etc/dovecot` for configuration data - `/srv/mail` for mail storage It seems inconvenient in some cases to have the image create these volumes, especially in case of the former. Consider a minimal Dockerfile like the following: ``` FROM dovecot/dovecot:latest COPY dovecot.conf /etc/dovecot/dovecot.conf ``` This creates a new image building on top of the official one, which has statically configured configuration, and thus does not need to save its config in a volume. Yet currently, since the base image exports volumes, a config volume is created. A user might also choose to save mail in a different directory or even in a remote SQL database, rendering the second volume unnecessary. I would like to know a bit about the reasons for declaring the volumes, and suggest removing the line, should this be an option. Some impact considerations: - Removing the volumes for future image versions will not impact existing deployments building on tags other than `latest`. - As the default (example) configuration is not very useful for non-test-setups, most people have probably assigned the config volume explicitly, e.g. using docker's `-v` option. These people will also not be affected. - The description explicitly states to mount `/srv/mail/`, but some people might rely on the the automatic volume creation nonetheless. - Some obscure proprietary scripts may rely on the current behavior. In any case, if the volumes are no longer declared, the image description should mention that the mail storage location (the default being `/var/mail`) must be saved e.g. by using volumes, and probably also that the configuration is expected at `/etc/dovecot/dovecot.conf`. Stay healthy and have a nice day, -- Thomas Bellebaum <thomas(a)bellebaum.eu>

2 1

Permission denied
by Ken Wright 02 Jan '22

02 Jan '22

My server has been running just fine for over a year, until I upgraded PostfixAdmin and somehow messed things up. Now I can't log in, and my mail client (Evolution, if it matters) keeps popping up an authentication request. The server is Ubuntu 20.04, my Dovecot is version 2.3.7.2, and Evolution is 3.40.4-1. I've also tried logging in with Roundcube with no success. Any insight or suggestions will be gratefully received! Here's the most recent entry from /var/log/mail.err: Dec 28 22:05:02 grace dovecot: lmtp(me(a)mydomain.com)<910309><SOFiMl7Qy2Hl4w0AThsuZQ>: Error: lmtp- server: conn unix:pid=906625,uid=117 [6]: rcpt me(a)mydomain.com: Mailbox INBOX: open(/var/mail/vmail/me(a)mydomain.com/tmp/1640747102.M850878P910309.grac ) failed: Permission denied Any further information available upon request!

3 6

spf helo pass
by Benny Pedersen 02 Jan '22

02 Jan '22

would be nice to see added :=) talvi.dovecot.org txt "spfv1 a -all"

5 13

auth crashes when oauth2 passdb is enabled
by Sebastiano Degan 01 Jan '22

01 Jan '22

I've enabled both sql and oauth2 passdb, regardless of the method used by the client, I get the following error: Jan 1 15:38:56 mail dovecot[52828]: auth: Panic: file http-client.c: line 646 (http_client_context_close): assertion failed: (cctx->clients_list == NULL) Jan 1 15:38:56 mail dovecot[52826]: master: Error: service(auth): command startup failed, throttling for 2.000 secs Jan 1 15:38:56 mail dovecot[52828]: auth: Fatal: master: service(auth): child 52840 killed with signal 6 (core dumped) Jan 1 15:38:56 mail dovecot[52828]: imap-login: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=192.168.1.104, lip=192.168.1.101, TLS, session=<QW7rFYfUgcTAqAFo> If I remove the oauth2 passdb, there are no problems. This is the output of dovecot -n: # 2.3.17 (e2aa53df5b): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: FreeBSD 13.0-RELEASE-p4 amd64 nullfs # Hostname: localhost auth_mechanisms = plain login oauthbearer xoauth2 default_internal_user = vmail first_valid_uid = 0 hostname = ***DELETED*** mail_location = maildir:/data/mailboxes/%d/%n mail_plugins = " fts fts_solr" mail_privileged_group = vmail 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 namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /usr/local/etc/dovecot/dovecot-oauth2.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } plugin { antispam_backend = pipe antispam_mail_notspam = learn_ham antispam_mail_sendmail = /usr/bin/rspamc antispam_mail_sendmail_args = -h;localhost:11334 antispam_mail_spam = learn_spam antispam_spam = Junk antispam_trash = Trash fts = solr fts_solr = url=http://localhost:8983/solr/dovecot sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.d sieve_dir = ~/sieve } postmaster_address = ***DELETED*** protocols = imap lmtp sieve pop3 service auth-worker { unix_listener auth-worker { user = vmail } } service auth { inet_listener { port = 1666 } unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } user = vmail } service imap-login { inet_listener imap { port = 0 } } service lmtp { inet_listener lmtp { port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } user = vmail } service pop3-login { inet_listener pop3 { port = 0 } } ssl = required ssl_cert = </usr/local/etc/letsencrypt/live/***DELETED***/fullchain.pem ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/data/mailboxes/%d/%n driver = static } protocol lda { mail_plugins = " fts fts_solr sieve" } protocol imap { mail_plugins = " fts fts_solr imap_sieve" } protocol lmtp { mail_plugins = " fts fts_solr sieve" postmaster_address = ***DELETED*** }

1 0

Add arm64 support to docker image
by alpe 01 Jan '22

01 Jan '22

I think the issue is here: ADD https://github.com/krallin/tini/releases/download/v0.19.0/tini /sbin/tini # buildkit tini has arm64 (and others) version. So it should be easy to make the container work with arm.

1 0

How to set LMTP over TLS for incoming emails in exim and dovecot
by Zakaria 01 Jan '22

01 Jan '22

1 0

cumulative resource limit exceeded
by Mats Mellstrand 31 Dec '21

31 Dec '21

Hi I’m running dovecot-2.3.15 and dovecot-pigeonhole-0.5.15 on FreeBSD 13 To day i suddenly get errors in my personal logfile (.dovecot.sieve.log) sieve: info: started log at Dec 29 20:26:42. .dovecot: error: cumulative resource usage limit exceeded. Is there anything I can do about this error? /mm

3 2

modernizing dovecot.conf
by Laura Steynes 30 Dec '21

30 Dec '21

Happy Holidays, And if you like me are working throughout so more senior engineers get their holidays, my condolences hah Taking the time to bring our dovecot.conf into the 2021/22 era .since its quiet time of year, Do I read it right that where we have things like service imap { process_limit = 1024 executable = imap imap-postlogin are not needed now ? and process limit is a global option? things like pop3/imap_client_workarounds = fooy are now global options, not to be in protocol { } sections ? I am reading the example conf files and see these outside the protocol sections where they have in the past lived, this is what makes me think they are now global and not needed in sub sections. but I may be missing some linking going from file to file , we have forever updated our single config file, just fixing whatever breaks when major versions break something, easier to find options in one file, rather than trying to sift through 40 included files like I am looking at now :-)

4 7

Six failed tests on openindiana (Opensolaris derivative)
by Friedrich Kink 29 Dec '21

29 Dec '21

Hi all, I'm new to this list, so please forgive me if I violate netiquette (and let me know how to improve, because it is not at all my intent). I want to create two packages (dovecot and dovecot-2.3-pigeonhole) hosted by openindiana.org. First of all, everything compiles fine and works as expected, but (there is always a but ;-)) 6 out of 41540 tests failed. To build a clean package I'd like to understand the nature of the failed tests and even more would like to fix the tests. I tried to find some hints how to tackle down the issue but was not successful so far. dovecot version 2.3.17.1, gcc version (OpenIndiana 7.5.0-il-0) 7.5.0 configure options: --sysconfdir=/etc \ --with-gssapi=plugin \ --with-ldap=plugin \ --with-sql=plugin \ --with-lua=plugin \ --with-ssl=openssl \ --with-sodium \ --with-mysql \ --with-pgsql failed tests: array_free ........................................................... : ok $(SOURCE_DIR)/src/lib/test-backtrace.c:21: Assert failed: strstr(str_c(bt), "main") != NULL backtrace_append ..................................................... : FAILED $(SOURCE_DIR)/src/lib/test-backtrace.c:45: Assert failed: strstr(bt, "main") != NULL backtrace_get ........................................................ : FAILED base32_encode() with padding ......................................... : ok buffer_replace() ..................................................... : ok $(SOURCE_DIR)/src/lib/test-buffer-istream.c:55: Assert failed: buffer_append_full_file(result, TEST_FILENAME, SIZE_MAX, &error) == BUFFER_APPEND_READ_ERROR $(SOURCE_DIR)/src/lib/test-buffer-istream.c:56: Assert failed: error != NULL && *error != '\0' buffer_append_full_file .............................................. : FAILED buffer_append_full_istream ........................................... : ok connection idle kill ................................................. : ok $(SOURCE_DIR)/src/lib/test-connection.c:563: Assert failed: !received_quit $(SOURCE_DIR)/src/lib/test-connection.c:563: Assert failed: !received_quit connection handshake failed (version) ................................ : FAILED connection handshake failed (handshake_args) ......................... : ok file_cache_switch_fd ................................................. : ok $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: fstat(.test_file_cache) failed: Bad file number $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: mmap_anon(.test_file_cache, 4096) failed: Not enough space $(SOURCE_DIR)/src/lib-test/test-common.c:245: Assert failed: suppress == TRUE Error: mremap_anon(.test_file_cache, 8192) failed: Not enough space file_cache_errors .................................................... : FAILED file_create_locked() ................................................. : ok ostream file send istream file ....................................... : ok $(SOURCE_DIR)/src/lib/test-ostream-file.c:172: Assert failed: input2->v_offset == 10 $(SOURCE_DIR)/src/lib/test-ostream-file.c:173: Assert failed: output->offset == 14 ostream file send istream sendfile() ................................. : FAILED ostream multiplex (simple) ........................................... : ok Again, compilation works clean without any warning. If you could provide some hints how to start would be great. I know I'm kind of inch picker but want to provide best experience to possible users and not give any chance to complain back to dovecot community. kind regards, Fritz

2 1

dovecot panic
by tobisworld＠gmail.com 27 Dec '21

27 Dec '21

Hi list since today I receive dovecot panics in my mail logs, whenever I want to access on my inbox in my mailclient (evolution) Details: dovecot --version 2.3.17.1 (476cd46418) Centos 7 (latest updates) x86 architecture mailbox stored in NFS > Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq <= t->view- >map->hdr.messages_count) > Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fb86f592142] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb86f59224e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf72fe) [0x7fb86f5a02fe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf73a1) [0x7fb86f5a03a1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb86f4eee38] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf438d) [0x7fb86f95b38d] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf43da) [0x7fb86f95b3da] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_finish+0x177) [0x7fb86f95ba87] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf9ad6) [0x7fb86f960ad6] - > /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit_full+0x9d) [0x7fb86f960fad] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit+0x1c) [0x7fb86f96106c] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_cache_set_seq_corrupted_reason+0x61) [0x7fb86f94a921] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_set_mail_cache_corrupted+0xed) [0x7fb86f8b9bbd] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a3e9) [0x7fb86f8e13e9] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a6b0) [0x7fb86f8e16b0] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_get_physical_size+0x38) [0x7fb86f8a6ba8] -> /usr/libexec/dovecot//lib20_mail_log_plugin.so(+0x2465) [0x7fb86e49b465] -> /usr/libexec/dovecot//lib15_notify_plugin.so(notify_contexts_mail_copy+ 0x5c) [0x7fb86e69f3ec] -> /usr/libexec/dovecot//lib15_notify_plugin.so(+0x25d4) [0x7fb86e6a05d4] -> /usr/libexec/dovecot//lib10_quota_plugin.so(+0x102ae) [0x7fb86eab72ae] -> /usr/libexec/dovecot//lib01_acl_plugin.so(+0xef3e) [0x7fb86eccef3e] -> /usr/lib64/dovecot/libdovecot- storage.so.0(+0x50c4c) [0x7fb86f8b7c4c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x58) [0x7fb86f8b7ec8] -> dovecot/imap(+0x1175b) [0x55a2b1a5375b] -> dovecot/imap(command_exec+0x64) [0x55a2b1a61f04] -> dovecot/imap(+0x1dde2) [0x55a2b1a5fde2] -> dovecot/imap(+0x1de71) [0x55a2b1a5fe71] -> dovecot/imap(+0x1e039) [0x55a2b1a60039] -> dovecot/imap(client_handle_input+0x205) [0x55a2b1a602f5] -> dovecot/imap(client_input+0x79) [0x55a2b1a608d9] I attached output from dovecot-sysreport here to this report Best regards tobi

1 1

Re: Dovecot does not start on MacOS 12.01
by Steven Smith 19 Dec '21

19 Dec '21

Re: https://www.mail-archive.com/dovecot@dovecot.org/msg84784.html <https://www.mail-archive.com/dovecot@dovecot.org/msg84784.html> I just upgraded to macOS 12.1, ran into this issue, and discovered this thread from the error message. Is there a viable workaround or patch yet? I tried the workaround in this thread, and still see these issues. Set default_vsz_limit = 0 in ./conf.d/10-master.conf. Observe that: dovecot now launches without the setrlimit(RLIMIT_DATA, 268435456) error at the command line However, the mail-err.log is still filled with these errors (below), perhaps for the child processes. Steve > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4629 returned error 89 (Fatal failure) > Dec 19 11:22:06 master: Error: service(imap-login): command startup failed, throttling for 2.000 secs > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4630 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4628 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4627 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4619 returned error 89 (Fatal failure) > Dec 19 11:22:06 imap-login: Error: Dec 19 11:22:06 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:06 imap-login: Fatal: master: service(imap-login): child 4631 returned error 89 (Fatal failure) > Dec 19 11:22:09 imap-login: Error: Dec 19 11:22:09 service(imap-login): Fatal: setrlimit(RLIMIT_DATA, 2147483648): Invalid argument > Dec 19 11:22:09 imap-login: Fatal: master: service(imap-login): child 4638 returned error 89 (Fatal failure) > Dec 19 11:22:09 master: Error: service(imap-login): command startup failed, throttling for 4.000 secs > On Mon, 1 Nov 2021 14:55:25 +0200, Aki Tuomi said: > > I think this is happening because MacOS no longer supports RLIMIT_DATA. We'll > try to look into this. default_vsz_limit = 0 seems good enough workaround. > Aki

1 2

Undefined symbol using fts-flatcurve with repo.dovecot.org packages
by Mike Acar 18 Dec '21

18 Dec '21

Hi, I'm trying to use dovecot-fts-flatcurve with dovecot 2:2.3.15-1+debian10 from repo.dovecot.org, but it looks like the package doesn't include ICU, which fts-flatcurve requires. After compilation and installation, I get an error from doveadm: doveadm fts-flatcurve stats -u user INBOX Fatal: Couldn't load required plugin /usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: dlopen() failed: /usr/lib/dovecot/modules/lib21_fts_flatcurve_plugin.so: undefined symbol: _ZTIN6icu_638ByteSinkE Unmangled, I think that's this symbol: U typeinfo for icu_63::ByteSink I checked the rules file from dovecot_2.3.15-1%2Bdebian10.debian.tar.xz and it appears that configure doesn't include --with-icu. Is there a plan to include this in a future release? -- | Mike Acar | | mike at waspfactory dot org |

1 0

Re: Re: invalid vsize-hdr
by Станислав Дырив 17 Dec '21

17 Dec '21

it helps for me (dovecot 2.2.36 @ centos7): #delete index files: find /path/to/user/maildir/ -type f -name dovecot.index* -delete find /path/to/user/maildir/ -type f -name dovecot-uidlist -delete #then re-create index by command: doveadm force-resync -u "user(a)domain.com" '*'

1 0

Can dovecot be leveraged to exploit Solr/Log4shell?
by Joseph Tam 15 Dec '21

15 Dec '21

I'm surprised I haven't seen this mentioned yet. An internet red alert went out Friday on a new zero-day exploit. It is an input validation problem where Java's Log4j module can be instructed via a specially crafted string to fetch and execute code from a remote LDAP server. It has been designated the Log4shell exploit (CVE-2021-44228). Although I don't use it, I immediately thought of Solr, which provides some dovecot installations with search indexing. Can dovecot be made to pass on arbitrary loggable strings to affected versions of Solr (7.4.0-7.7.3, 8.0.0-8.11.0)? Those running Solr to implement Dovecot FTS should look at https://solr.apache.org/security.html#apache-solr-affected-by-apache-log4j-… Joseph Tam <jtam.home(a)gmail.com>

6 8

quota warnings not sent out anymore
by mj 15 Dec '21

15 Dec '21

Hi, We suddenly realised that our maildir quota warnings are no longer sent out. We don't understand why not. This is dovecot 2.3.4.1 on debian 10.11. We use a script to send out the notification, adapted from the dovecot wiki here: (https://doc.dovecot.org/configuration_manual/quota/) Our quota notification script is: > #!/bin/sh > PERCENT=$1 > USER=$2 > cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o "plugin/quota=maildir::noenforcing" > From: noreply(a)domain.com > Subject: quota warning > > Your mailbox is now $PERCENT% full. > > Please delete or archive items to decrease your mailbox size. Our complete doveconf -n output is at the end of this email. When calling the script manually as user root, it works perfectly. But as user vmail or dovecot, no notifications are sent at all. I guess this is relevant: > root@dovecot:/etc/dovecot# ls -l /var/run/dovecot/ > total 8 > srw------- 1 root root 0 Dec 6 00:00 anvil > srw------- 1 root root 0 Dec 6 00:00 anvil-auth-penalty > srw------- 1 dovecot root 0 Dec 6 11:34 auth-client > srw------- 1 dovecot root 0 Dec 6 11:34 auth-login > srw------- 1 root root 0 Dec 6 11:34 auth-master > -rw------- 1 root root 32 Jul 19 17:39 auth-token-secret.dat > srw-rw-rw- 1 vmail vmail 0 Dec 6 11:34 auth-userdb > srw------- 1 dovecot root 0 Dec 6 11:34 auth-worker > srw------- 1 root root 0 Dec 6 11:34 config > srw-rw---- 1 root dovecot 0 Dec 6 11:34 dict > srw-rw---- 1 root dovecot 0 Dec 6 11:34 dict-async > srw------- 1 root root 0 Dec 6 11:34 director-admin > srw-rw-rw- 1 root root 0 Dec 6 11:34 dns-client > srw------- 1 root root 0 Dec 6 11:34 doveadm-server > lrwxrwxrwx 1 root root 25 Dec 6 00:00 dovecot.conf -> /etc/dovecot/dovecot.conf > drwxr-xr-x 2 root root 40 Jul 19 17:39 empty > srw-rw---- 1 root dovecot 0 Dec 6 11:34 imap-hibernate > srw------- 1 root root 0 Dec 6 11:34 imap-master > srw-rw-rw- 1 root root 0 Dec 6 11:34 imap-urlauth > srw------- 1 dovecot root 0 Dec 6 11:34 imap-urlauth-worker > srw-rw-rw- 1 root root 0 Dec 6 11:34 indexer > srw------- 1 dovecot root 0 Dec 6 11:34 indexer-worker > srw------- 1 dovecot root 0 Dec 6 11:34 ipc > srw-rw-rw- 1 root root 0 Dec 6 11:34 lmtp > srw------- 1 root root 0 Dec 6 11:34 log-errors > drwxr-x--- 2 root nogroup 120 Dec 6 11:34 login > srw------- 1 root root 0 Dec 6 11:34 master > -rw------- 1 root root 6 Dec 6 00:00 master.pid > srw------- 1 root root 0 Dec 6 11:34 old-stats > prw------- 1 root root 0 Dec 6 11:34 old-stats-mail > prw------- 1 root root 0 Dec 6 11:34 old-stats-user > srw------- 1 vmail root 0 Dec 6 11:34 quota-warning > srw------- 1 root root 0 Dec 6 11:34 replication-notify > prw------- 1 root root 0 Dec 6 11:34 replication-notify-fifo > srw------- 1 dovecot root 0 Dec 6 11:34 replicator > srw-rw---- 1 vmail vmail 0 Dec 6 11:34 stats-reader > srw-rw---- 1 vmail vmail 0 Dec 6 11:34 stats-writer > drwxr-x--- 2 root nogroup 80 Dec 6 11:34 token-login Can anyone help, and explain what is going on here? Thank you very much in advance for a reply! MJ The doveconf -n output: > root@imap:/etc/dovecot# doveconf -n > # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.4 () > # OS: Linux 4.19.0-17-amd64 x86_64 Debian 10.11 xfs > # Hostname: mail.company.com > auth_debug = yes > auth_failure_delay = 10 secs > auth_master_user_separator = * > auth_mechanisms = plain login > auth_username_format = %Ln > auth_verbose = yes > auth_verbose_passwords = sha1 > default_vsz_limit = 512 M > deliver_log_format = %f | %s | msgid=%m: %$ > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > login_greeting = Dovecot ready. > login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c lport=%a > mail_gid = vmail > mail_location = maildir:/var/vmail/%Ln/Maildir:LAYOUT=fs:DIRNAME=mAildir > mail_plugins = acl lazy_expunge zlib quota mail_log notify > mail_shared_explicit_inbox = yes > mail_uid = vmail > 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 > namespace { > list = children > location = maildir:/var/vmail/%%u/Maildir:LAYOUT=fs:DIRNAME=mAildir:INDEX=/var/vmail/%u/shared/%%u > prefix = shared/%%n/ > separator = / > subscriptions = no > type = shared > } > namespace inbox { > inbox = yes > location = > mailbox "Deleted items" { > special_use = \Trash > } > mailbox Drafts { > special_use = \Drafts > } > mailbox Junk { > special_use = \Junk > } > mailbox Sent { > special_use = \Sent > } > mailbox "Sent items" { > special_use = \Sent > } > mailbox Trash { > special_use = \Trash > } > mailbox inbox { > auto = subscribe > } > prefix = > separator = / > type = private > } > passdb { > args = /etc/dovecot/deny.imap > deny = yes > driver = passwd-file > } > passdb { > args = /etc/dovecot/master-users > driver = passwd-file > master = yes > } > passdb { > args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > result_failure = return-fail > } > plugin { > acl = vfile > acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db > mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename append > mail_log_fields = uid box msgid from subject > quota = maildir > quota_rule = ?:storage=5G > quota_rule2 = Trash:storage=+100M > quota_warning = storage=97%% quota-warning 97 %u > quota_warning2 = storage=95%% quota-warning 95 %u > quota_warning3 = storage=90%% quota-warning 90 %u > quota_warning4 = storage=85%% quota-warning 85 %u > quota_warning5 = storage=80%% quota-warning 80 %u > quota_warning6 = -storage=100%% quota-warning below %u > sieve = ~/.dovecot.sieve > sieve_default = /var/lib/dovecot/default.sieve > sieve_dir = ~/sieve > } > protocols = imap lmtp sieve > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = vmail > mode = 0666 > user = vmail > } > } > service imap-login { > process_limit = 500 > process_min_avail = 2 > } > service quota-warning { > executable = script /usr/local/bin/quota-warning.sh > unix_listener quota-warning { > user = vmail > } > user = dovecot > } > service stats { > unix_listener stats-reader { > group = vmail > mode = 0660 > user = vmail > } > unix_listener stats-writer { > group = vmail > mode = 0660 > user = vmail > } > } > shutdown_clients = no > ssl = required > ssl_cert = </etc/ssl/letsencrypt/fullchain.pem > ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 > ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > ssl_min_protocol = TLSv1.2 > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%n allow_all_users=yes > driver = static > } > userdb { > args = /etc/dovecot/dovecot-ldap.conf.ext > driver = ldap > } > verbose_proctitle = yes > protocol lda { > mail_plugins = acl lazy_expunge zlib quota mail_log notify sieve quota > } > protocol imap { > imap_max_line_length = 2 M > mail_max_userip_connections = 40 > mail_plugins = acl lazy_expunge zlib quota mail_log notify imap_quota imap_acl > }

2 5

dovecot-2.3.17: "Panic: file ioloop.c: line 865"
by Piper Andreas 14 Dec '21

14 Dec '21

Hello, since the upgrade from dovecot-2.3.16 to 2.3.17 I get 'Panic'-errors in the system-log of my replicator hosts. See below for log messages, doveconf-output and gdb-backtrace. Storage filesystem is ZFS. The error seems to be correlated with exactly one user-mailbox, this user is repeatedly noted as 'failed' in replication status, although replication of this mailbox seems to work, as the mailbox status shows always the identical size on both replicators. The error can be produced by forcing replication of this individual mailbox. Is there anything I can do to repair this mailbox? Thanks for any hints, Andreas Example log-messages: Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: write(<local>) failed: Timed out after 60 seconds Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == cur rent_ioloop) Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7 f4e59419182] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f4e5941929e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8a5e) [0x7f4e59427a5e] -> /usr/lib/dovecot/libdovecot.so.0(+0xf8b01) [0x7f4e59427b01] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f 4e593744a7] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_destroy+0x2dc) [0x7f4e5944121c] -> dovecot/doveadm-server(+0x46fb6) [0x563d0 150ffb6] -> dovecot/doveadm-server(doveadm_print+0x27) [0x563d01508fb7] -> dovecot/doveadm-server(+0x2b427) [0x563d014f4427] -> dove cot/doveadm-server(+0x2da44) [0x563d014f6a44] -> dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x2cf) [0x563d014f7c6f] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x43b) [0x563d01508c1b] -> dovecot/doveadm-server(+0x44612) [0x563d0150d612] -> /usr /lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f4e594406d9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal +0x134) [0x7f4e59442034] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f4e594407e0] -> /usr/lib/dovecot/libdovec ot.so.0(io_loop_run+0x38) [0x7f4e59440a18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4e593a6a23] -> dovecot/ doveadm-server(main+0x102) [0x563d014e6922] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f4e58bc1bf7] -> dovecot/d oveadm-server(_start+0x2a) [0x563d014e69aa] Nov 11 07:17:50 vhrz311 dovecot: doveadm(119455): Fatal: master: service(doveadm): child 119455 killed with signal 6 (core dumped) 'doveconf -n': # 2.3.17 (e2aa53df5b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17 (054dddfa) # OS: Linux 4.15.0-162-generic x86_64 Ubuntu 18.04.6 LTS # Hostname: vhrz311.HRZ.Uni-Marburg.DE auth_cache_negative_ttl = 0 auth_cache_size = 10 M auth_master_user_separator = * auth_worker_max_count = 1024 base_dir = /var/run/dovecot/ default_client_limit = 10000 default_vsz_limit = 6 G doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_gid = 10000 first_valid_uid = 10000 imap_max_line_length = 640 k last_valid_gid = 10000 last_valid_uid = 10000 mail_attribute_dict = file:%h/mdbox/dovecot-attributes mail_gid = 10000 mail_location = mdbox:%h/mdbox mail_plugins = " mail_log notify zlib notify replication" mail_privileged_group = mail mail_uid = 10000 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 namespace inbox { hidden = no inbox = yes list = yes location = prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot.deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/private/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.hrz.conf.ext driver = ldap name = passdb_ldap_hrz } passdb { args = /etc/dovecot/dovecot-ldap.staff.conf.ext driver = ldap name = passdb_ldap_staff } passdb { args = /etc/dovecot/dovecot-ldap.students.conf.ext driver = ldap name = passdb_ldap_students } plugin { mail_replica = tcp:172.25.1.95 sieve = file:~/sieve;active=~/.dovecot.sieve sieve_default = /var/lib/dovecot/default.sieve sieve_max_actions = 55 sieve_max_redirects = 50 } pop3_uidl_format = %08Xv%08Xu postmaster_address = postmaster(a)hrz.uni-marburg.de protocols = imap pop3 lmtp sieve replication_dsync_parameters = -d -n INBOX -l 30 -U replication_max_conns = 20 service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth-worker { user = $default_internal_user } service auth { client_limit = 10000 } service config { process_min_avail = 8 } service doveadm { inet_listener { port = 12345 } vsz_limit = 6 G } service imap-login { process_min_avail = 64 service_count = 0 } service imap { process_limit = 8192 } service lmtp { inet_listener lmtp { port = 24 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 8 service_count = 0 } service pop3-login { process_min_avail = 8 service_count = 0 } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } service submission-login { service_count = 0 } ssl = required ssl_ca = </etc/ssl/certs/umr-chain.pem ssl_cert = </etc/ssl/certs/vhrz311.hrz.uni-marburg.de.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_require_crl = no userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap name = userdb_ldap } protocol imap { imap_metadata = yes mail_max_userip_connections = 25 mail_plugins = " mail_log notify zlib notify replication imap_zlib" } protocol lmtp { mail_plugins = " mail_log notify zlib notify replication sieve" } gdb: gdb /usr/lib/dovecot/doveadm-server /var/vmail/system-cores/core GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/dovecot/doveadm-server...(no debugging symbols found)...done. [New LWP 119455] [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/doveadm-server'. Program terminated with signal SIGABRT, Aborted. #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 51 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 #1 0x00007f4e58be0921 in __GI_abort () at abort.c:79 #2 0x00007f4e59427a11 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #3 0x00007f4e59427b01 in ?? () from /usr/lib/dovecot/libdovecot.so.0 #4 0x00007f4e593744a7 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #5 0x00007f4e5944121c in io_loop_destroy () from /usr/lib/dovecot/libdovecot.so.0 #6 0x0000563d0150ffb6 in ?? () #7 0x0000563d01508fb7 in doveadm_print () #8 0x0000563d014f4427 in ?? () #9 0x0000563d014f6a44 in ?? () #10 0x0000563d014f7c6f in doveadm_cmd_ver2_to_mail_cmd_wrapper () #11 0x0000563d01508c1b in doveadm_cmd_run_ver2 () #12 0x0000563d0150d612 in ?? () #13 0x00007f4e594406d9 in io_loop_call_io () from /usr/lib/dovecot/libdovecot.so.0 #14 0x00007f4e59442034 in io_loop_handler_run_internal () from /usr/lib/dovecot/libdovecot.so.0 #15 0x00007f4e594407e0 in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 #16 0x00007f4e59440a18 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 #17 0x00007f4e593a6a23 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 #18 0x0000563d014e6922 in main ()

4 5

Dovecot, Solr (FTS) and iOS body search
by Ben Howard 13 Dec '21

13 Dec '21

I had a question about full text search with Dovecot, Solr with iOS as a client (the built in default mail client). Does anyone happen to know if it's possible to get the iOS mail client to search bodies of email via IMAP with Dovecot and Solr on the server? I've looked at the IMAP queries being sent to Solr and regardless of iOS settings only the subject or to/cc/from seem to get queried. i.e.: test search query: Foobar Request [dovecot] webapp=/solr path=/select params={q={!lucene+q.op%3DAND}subject:Foobar&fl=uid,score&sort=uid+asc (trimmed for space) test search query with 'message' selected as search via the GUI in iOS mail app: Foobar 2021-12-12 22:16:43.840 INFO (qtp1309129055-21) [ x:dovecot] o.a.s.c.S.Request [dovecot] webapp=/solr path=/select params={q={!lucene+q.op%3DAND}to:Foobar+OR+cc:Foobar+OR+from:Foobar+OR+subject:Foobar&fl=uid,score&sort=uid+asc (trimmed for space) I also put Wireshark between an iOS device and the mail server to see the IMAP commands being issued client side and it matches with what Dovecot is seeing - i.e. only to/cc/from/subject no body queries. dovecot version: 2.3.17.1 (476cd46418), solr 8.11.0 and fts_enforced = yes Is it just not possible for the iOS mail client to search for keywords within the body of emails via IMAP/Dovecot/Solr? Any pointers, or just knowing I should give up, would be most gratefully received. Thanks

1 0

Re: 2.3.17: Panic on LMTP deliveries
by Volker ********* 13 Dec '21

13 Dec '21

It WORKS!!! :-) Great, thanks! Best regards Volker Am 12.12.2021 um 13:00 schrieb Volker: > That´s a good message, thank you very much! > > I will try the patch! > > Kind regards > Volker > > Am 12.12.2021 um 12:48 schrieb Aki Tuomi: >>>> Hello! >>>> >>>> While searching for an explanation for the fact that after updating to >>>> Dovecot 2.3.17_1 (FreeBSD 12.2) I suddenly stopped receiving emails and >>>> following error messages appeared in the dovecot.log, >>>> >>>> /Error: lmtp-server: conn unix:uid=125 [1]: rcptuser(a)domain.tld: >>>> duplicate db: Useruser(a)domain.tld doesn't have home dir set, disabling >>>> duplicate database// >>>> // >>>> //Dec 12 08:42:54 lmtp(user(a)domain.tld)<80363><z7AxDf6ntWHrOQEAp6O1gg>: >>>> Panic: file imem.c: line 65 (i_strconcat): assertion failed: (str1 != NULL) >>>> >>>> /I found your answer here >>>> <https://www.mail-archive.com/dovecot@dovecot.org/msg84893.html>: >>>> >>>> /Problem confirmed. This is a 2.3.17 regression. Tracking internally as >>>> DOP-2659./ >>>> / >>>> Regards, >>>> Stephan./ >>>> >>>> >>>> But what exactly does your answer mean for those affected? >>>> >>>> That all users who use Dovecot and use the whole thing without >>>> "mail_home" and only with "mail_location", must wait until a BugFix >>>> appears to be able to receive emails again? >>>> >>>> >>>> Thanks in advance and have a nice advent sunday >>>> Volker >>>> >>>> P. S.: >>>> In my case dovecot -n shows >>>> >>>> /mail_location = maildir:/var/mail/vhosts/%d/%n// >>>> //mail_home = /var/mail/vhosts/%d/%n >>>> >>>> /so mail_home is even set!/ >>>> / >>>> >>> You can roll back to 2.3.16 as well? >>> >>> Aki >> After looking bit more, this issue is fixed and will be in 2.3.18. If you want, you can try applying >> >> https://github.com/dovecot/core/compare/98f709de%5E..d36d2c59.patch >> >> which should fix this issue. >> >> Aki >

1 0

Send to mailbox + alias??
by postfix＠aecperformance.com 12 Dec '21

12 Dec '21

Is there any way to set postfix/dovecot to: 1. Deliver email to the mailbox -> ie. bob(a)test.com <mailto:bob@test.com> AND 2. Set the email as an alias and send it to the forwarded address -> bobs.boss(a)bosses.com <mailto:bobs.boss@bosses.com> This would be given that both email accounts are set up as virtual_users in MySql. Right now if I set up an alias and mailbox for the same email the alias overrides the mailbox and the email is delivered to the forwarded account and not to the email's mailbox. If the mailbox exists I need the email sent to both the mailbox and the forwarded mailbox. Can I do that? If so, how?

2 1

submission Connection failed: Failed to connect to remote server
by fugee ohu 12 Dec '21

12 Dec '21

I'm getting this error when I try to send mail mail dovecot: submission(username-here)<113012><tY+KjubSZJJHvuNn>: Debug: smtp-client: conn 127.0.0.1:25 [1]: Connection failed: Failed to connect to remote server

2 1

Re[7]: Replicator bug report
by Daniel Miller 12 Dec '21

12 Dec '21

On 12/7/2021 12:29:49 PM, "Daniel Miller" <dmiller(a)amfes.com> wrote: >>service replicator { >> vsz_limit = 2G >>} >> >>Aki >> >Tried that - got another one. I just tried setting service replicator { vcsz_limit = 5G } and I still get: Dec 7 15:08:25 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 4294967336 bytes -- Daniel

3 4