- dovecot - dovecot.org

Re: Connection refused
by Aki Tuomi 24 Nov '21

24 Nov '21

Please keep responses on the list. You are missing ssl=yes. Aki > On 24/11/2021 06:35 fugee ohu <fugee279(a)gmail.com> wrote: > > > # doveconf -n > # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.5.7.2 () > # OS: Linux 5.14.17-x86_64-linode150 x86_64 Ubuntu 20.04.3 LTS > # Hostname: mail.servicemouse.com > doveconf: Error: t_readlink(/var/run/dovecot/dovecot.conf) failed: > readlink() failed: No such file or directory > auth_verbose = yes > mail_privileged_group = mail > 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 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 > } > plugin { > sieve = file:~/sieve;active=~/.dovecot.sieve > } > protocols = " imap lmtp sieve pop3 submission" > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0777 > user = postfix > } > } > ssl_cert = </etc/letsencrypt/live/mail.servicemouse.com/fullchain.pem > ssl_client_ca_dir = /etc/letsencrypt/live/mail.servicemouse.com > ssl_dh = # hidden, use -P to show it > ssl_key = # hidden, use -P to show it > submission_relay_host = 127.0.0.1 > submission_relay_ssl = starttls > submission_relay_trusted = yes > userdb { > driver = passwd > } > > On Tue, Nov 23, 2021 at 3:02 AM Aki Tuomi <aki.tuomi(a)open-xchange.com> wrote: > > > > > > > On 22/11/2021 20:18 fugee ohu <fugee279(a)gmail.com> wrote: > > > > > > > > > I'm unable to connect to dovecot: > > > > $ openssl s_client -connect mail.servicemouse.com:993 140439527167360:error:0200206F:system library:connect:Connection refused:../crypto/bio/b_sock2.c:110: 140439527167360:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:111: connect:errno=111 > > > > Can you provide output of `doveconf -n`? > > > > Aki

1 0

BUG: imapsieve with virtual mailboxes
by Claudemir Todo Bom 24 Nov '21

24 Nov '21

Hi, I've configured virtual mailboxes and it is working well, including the setting of the real mailbox that will receive messages moved to it. Problem starts when I try to use imapsieve plugin with this setup, I receive a panic on the log and the action isn't executed. To make the problem appears, all that its needed is to have a virtual folder defined with the real mailbox configured (! prefix on the virtual configuration file), having the imapsieve options enabled on dovecot configuration and a sieve script defined. Error occurs even if the sieve script is empty. This error was already reported back in 2017: https://www.dovecot.org/list/dovecot/2017-September/109445.html This is the relevant configuration for imapsieve: plugin { imapsieve_mailbox1_before = file:/etc/wwmail/antispamsieve/learn.sieve imapsieve_mailbox1_causes = COPY APPEND imapsieve_mailbox1_name = * sieve_global_path = /var/lib/dovecot/sieve/default.sieve sieve_pipe_bin_dir = /etc/wwmail/antispamsieve/ sieve_plugins = sieve_imapsieve sieve_extprograms } This is the error received: Oct 27 16:25:06 lab dovecot: imap(monitor(a)lab.wwmail.app)<28726><ug8CjVrPIqoAAAAAAAAAAAAAAAAAAAAB>: Panic: file mail-index-map.c: line 558 (mail_index_map_lookup_seq_range): assertion failed: (first_uid > 0) Oct 27 16:25:06 lab dovecot: imap(monitor(a)lab.wwmail.app)<28726><ug8CjVrPIqoAAAAAAAAAAAAAAAAAAAAB>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f8f68fe1b52] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f8f68fe1c6e] -> /usr/lib/dovecot/libdovecot.so.0(+0xff41b) [0x7f8f68ff041b] -> /usr/lib/dovecot/libdovecot.so.0(+0xff4b1) [0x7f8f68ff04b1] -> /usr/lib/dovecot/libdovecot.so.0(+0x5427c) [0x7f8f68f4527c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x49e07) [0x7f8f69104e07] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xf00a9) [0x7f8f691ab0a9] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_seq+0xf) [0x7f8f691b3e0f] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x829c) [0x7f8f68b1029c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_set_uid+0x35) [0x7f8f6910a9a5] -> /usr/lib/dovecot/modules/lib95_imap_sieve_plugin.so(+0x8cf2) [0x7f8f68b01cf2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x56) [0x7f8f69117806] -> dovecot/imap(+0x1584d) [0x56322e61784d] -> dovecot/imap(command_exec+0xa4) [0x56322e621cf4] -> dovecot/imap(+0x25bbf) [0x56322e627bbf] -> dovecot/imap(+0x25c6b) [0x56322e627c6b] -> dovecot/imap(+0x25f04) [0x56322e627f04] -> dovecot/imap(client_handle_input+0x1b5) [0x56322e6280d5] -> dovecot/imap(client_input+0x70) [0x56322e628490] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f8f690067d9] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7f8f69008642] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f8f690086f0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f8f690088b0] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8f68f78dd3] -> dovecot/imap(main+0x500) [0x56322e613fc0] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea) [0x7f8f68d4cd0a] -> dovecot/imap(_start+0x2a) [0x56322e6140ba] I am using packages of Debian Bookworm (testing) but the problem already occured on Debian Buster. Packages installed # dpkg --list | grep dovecot | awk '{print $2 " " $3}' dovecot-antispam 2.0+20171229-1+b8 dovecot-core 1:2.3.16+dfsg1-3 dovecot-imapd 1:2.3.16+dfsg1-3 dovecot-lmtpd 1:2.3.16+dfsg1-3 dovecot-managesieved 1:2.3.16+dfsg1-3 dovecot-mysql 1:2.3.16+dfsg1-3 dovecot-pop3d 1:2.3.16+dfsg1-3 dovecot-sieve 1:2.3.16+dfsg1-3 Please take a look at it. I can help provide more information if needed, but I think all relevant information to reproduce the bug is here. Best regards, Claudemir

2 4

dsync not deleting mail on remote side
by Otto Frauchiger 23 Nov '21

23 Nov '21

Sorry, first time sent using the wrong mail address. Hello Short version: Dovecot's dsync from release 2.3.7.2 (default install from focal repository) running under Ubuntu 20.04.6 LTS server is not deleting mails on the identical remote server. Background: I have installed this configuration using automated scripts several times for customers. Functionally identical installations done on Ubuntu LTS Servers 14.04, 16.04 and 18.04 are running for years without problem. Now I have tried several times to do the same with Ubuntu 20.04 and can't get dsync to work properly. Last year I could fall back onto Ubuntu 18.04. This time I can't and must install the latest versions. Setup: - Two VM's on ESXI 6.7U3 with 36 GB of disk space and 8 GB ram, 10k spinning disks or SSD with HW RAID1 - Mariadb for mail users (master - master synched) - Postfixadmin to manage the users - Postfix - Dovecot - Some with Roundcube - The clients can connect to either one server and connect SMTPS (465 or 587) or POPS (995) to the servers. - The two servers connect on a dedicated network without routing (SSL, port > 49000). The synchronization network has no mail traffic except the one that synchronizes the servers. - Additionally the two servers are ntp peers within a few ms - but that is only relevant to know when we start comparing logs from the machines Problem description: - When I send one mail to one account, it is immediately synched to the other server. This is also seen in the dovecot log and I can connect to any one of the two servers to download it. - When I read and delete the mail on one server, it is NOT deleted on the other server. I do not see a trigger in the dovecot log that kicks on the synchronization (like I do when sending mails). As a result, the mail can be downloaded and deleted from both servers. - When I send a new mail to one of the two servers, the synchronization takes place and the mail that I read and deleted is also gone on the remote (backup) server. - Changing users, rights in dsynch.conf , SSL on or off, or connecting to PLAIN ports 25, 110 or 143 is never improved it. Iptables or ufw are not in use. - In my case I have systems using the server that' don't like duplicate mails and the servers fail the acceptance test criteria. - This causes duplicate mail if one client is connecting to the other server. Since a new mail fixes that duplicate mail problem, it is likely that up to now nobody detects it and complains about this. Especially if the servers would run in a primary - backup mode. I assume that's why I could not find reportings on the web until now. Dovecot -n: See attachments Log from my automated test system using Ubuntu 20.01 and focal default dovecot package from repository (dovecot 2.3.7.2): 2021-11-22 18:20:06.30 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:06.81 - SMTP Server: mail-pri Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 2021-11-22 18:20:14.90 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:15.37 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr no delete) 2021-11-22 18:20:17.32 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:17.77 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr no delete) -> synchronization worked when sending mails 2021-11-22 18:20:27.52 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:27.96 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr and delete) 2021-11-22 18:20:30.72 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:31.17 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr and delete) -> synchronization failed after POP3 connection with delete 2021-11-22 18:20:53.06 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:53.66 - SMTP Server: mail-sec Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 2021-11-22 18:20:57.91 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:58.33 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr no delete) 2021-11-22 18:21:00.82 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:21:01.27 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr no delete) 2021-11-22 18:21:04.65 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:21:05.11 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr and delete) 2021-11-22 18:21:08.95 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:21:09.40 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr and delete) 2021-11-22 18:21:39.50 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- Reference log with the same installation using Ubuntu 18.04 and bionic default package form repository (dovecot 1:2.2.33.2-1ubuntu4.7): 2021-11-23 13:55:06.93 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:54:49.86 - SMTP Server: mail-pri Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 2021-11-23 13:55:06.93 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:07.47 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 (retr no delete) 2021-11-23 13:55:13.10 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:13.66 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 (retr no delete) -> synchronization OK for sending mails 2021-11-23 13:55:22.32 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:22.87 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 (retr and delete) 2021-11-23 13:55:27.91 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:28.35 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - no mails found -> synchronization OK for deleting mails 2021-11-23 13:55:36.48 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:37.00 - SMTP Server: mail-sec Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 2021-11-23 13:55:45.94 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:46.48 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 (retr no delete) 2021-11-23 13:55:55.59 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:56.14 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 (retr no delete) 2021-11-23 13:56:05.70 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:56:06.26 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 (retr and delete) 2021-11-23 13:56:38.70 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:56:39.12 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - no mails found P.S. I compared the dovecot and postfix config files between these two versions and both servers and they are functionally identical except where they need to be different. I would appreciate any help here. If needed I can create log files that show that nothing is triggered as well as produce wireshark captures (port 25 and 110) or the link for the synch (currently with ssl but I could change that if needed). Thanks in advance Otto -- This email has been checked for viruses by AVG. https://www.avg.com

1 0

dsync not deleting mail on remote side
by Otto Frauchiger 23 Nov '21

23 Nov '21

Hello Short version: Dovecot's dsync from release 2.3.7.2 (default install from focal repository) running under Ubuntu 20.04.6 LTS server is not deleting mails on the identical remote server. Background: I have installed this configuration using automated scripts several times for customers. Functionally identical installations done on Ubuntu LTS Servers 14.04, 16.04 and 18.04 are running for years without problem. Now I have tried several times to do the same with Ubuntu 20.04 and can't get dsync to work properly. Last year I could fall back onto Ubuntu 18.04. This time I can't and must install the latest versions. Setup: - Two VM's on ESXI 6.7U3 with 36 GB of disk space and 8 GB ram, 10k spinning disks or SSD with HW RAID1 - Mariadb for mail users (master - master synched) - Postfixadmin to manage the users - Postfix - Dovecot - Some with Roundcube - The clients can connect to either one server and connect SMTPS (465 or 587) or POPS (995) to the servers. - The two servers connect on a dedicated network without routing (SSL, port > 49000). The synchronization network has no mail traffic except the one that synchronizes the servers. - Additionally the two servers are ntp peers within a few ms - but that is only relevant to know when we start comparing logs from the machines Problem description: - When I send one mail to one account, it is immediately synched to the other server. This is also seen in the dovecot log and I can connect to any one of the two servers to download it. - When I read and delete the mail on one server, it is NOT deleted on the other server. I do not see a trigger in the dovecot log that kicks on the synchronization (like I do when sending mails). As a result, the mail can be downloaded and deleted from both servers. - When I send a new mail to one of the two servers, the synchronization takes place and the mail that I read and deleted is also gone on the remote (backup) server. - Changing users, rights in dsynch.conf , SSL on or off, or connecting to PLAIN ports 25, 110 or 143 is never improved it. Iptables or ufw are not in use. - In my case I have systems using the server that' don't like duplicate mails and the servers fail the acceptance test criteria. - This causes duplicate mail if one client is connecting to the other server. Since a new mail fixes that duplicate mail problem, it is likely that up to now nobody detects it and complains about this. Especially if the servers would run in a primary - backup mode. I assume that's why I could not find reportings on the web until now. Dovecot -n: See attachments Log from my automated test system using Ubuntu 20.01 and focal default dovecot package from repository (dovecot 2.3.7.2): 2021-11-22 18:20:06.30 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:06.81 - SMTP Server: mail-pri Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 2021-11-22 18:20:14.90 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:15.37 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr no delete) 2021-11-22 18:20:17.32 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:17.77 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr no delete) -> synchronization worked when sending mails 2021-11-22 18:20:27.52 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:27.96 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr and delete) 2021-11-22 18:20:30.72 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:31.17 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:06, Msg 00001 (retr and delete) -> synchronization failed after POP3 connection with delete 2021-11-22 18:20:53.06 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:53.66 - SMTP Server: mail-sec Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 2021-11-22 18:20:57.91 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:20:58.33 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr no delete) 2021-11-22 18:21:00.82 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:21:01.27 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr no delete) 2021-11-22 18:21:04.65 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:21:05.11 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr and delete) 2021-11-22 18:21:08.95 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-22 18:21:09.40 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-22 18:20:53, Msg 00002 (retr and delete) 2021-11-22 18:21:39.50 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- Reference log with the same installation using Ubuntu 18.04 and bionic default package form repository (dovecot 1:2.2.33.2-1ubuntu4.7): 2021-11-23 13:55:06.93 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:54:49.86 - SMTP Server: mail-pri Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 2021-11-23 13:55:06.93 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:07.47 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 (retr no delete) 2021-11-23 13:55:13.10 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:13.66 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 (retr no delete) -> synchronization OK for sending mails 2021-11-23 13:55:22.32 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:22.87 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:54:49, Msg 00001 (retr and delete) 2021-11-23 13:55:27.91 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:28.35 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - no mails found -> synchronization OK for deleting mails 2021-11-23 13:55:36.48 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:37.00 - SMTP Server: mail-sec Port 465 TLS - User: user(a)test.ch - To: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 2021-11-23 13:55:45.94 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:46.48 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 (retr no delete) 2021-11-23 13:55:55.59 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:55:56.14 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 (retr no delete) 2021-11-23 13:56:05.70 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:56:06.26 - POP3 Server: mail-pri Port 995 TLS - User: user(a)test.ch - From: user(a)test.ch - Subject: Test 2021-11-23 13:55:36, Msg 00002 (retr and delete) 2021-11-23 13:56:38.70 - ---------------------------------------------------------------------------- ---------------------------------------------------------------------- 2021-11-23 13:56:39.12 - POP3 Server: mail-sec Port 995 TLS - User: user(a)test.ch - no mails found P.S. I compared the dovecot and postfix config files between these two versions and both servers and they are functionally identical except where they need to be different. I would appreciate any help here. If needed I can create log files that show that nothing is triggered as well as produce wireshark captures (port 25 and 110) or the link for the synch (currently with ssl but I could change that if needed). Thanks in advance Otto -- This email has been checked for viruses by AVG. https://www.avg.com

1 0

Connection refused
by fugee ohu 23 Nov '21

23 Nov '21

I'm unable to connect to dovecot: > $ openssl s_client -connect mail.servicemouse.com:993 140439527167360:error:0200206F:system library:connect:Connection refused:../crypto/bio/b_sock2.c:110: 140439527167360:error:2008A067:BIO routines:BIO_connect:connect error:../crypto/bio/b_sock2.c:111: connect:errno=111

2 1

Retrieive vsz_limit programatically
by Joan Moreau 23 Nov '21

23 Nov '21

Hello How to get, programatically (C/C++), the value of teh dovecot.conf file of vsz_limit and default_vsz_limit ? Thank you

5 9

ZFS storage and backup
by infoomatic 23 Nov '21

23 Nov '21

Hi listmembers, I am about to migrate our mailservices to FreeBSD + ZFS. Thus, before entering the sheer endless stage of performance testing, I thought I would ask here kindly for all kinds of information. My setups are nothing special with few users, however, I would like to have a nice setup, maybe some of you could contribute to this thread. We are using slow spinning disks, but we may consider using ssds in a not-so-distant future. *) storages: any infos on ZFS options or whether to use mdbox or sdbox, and what configs/options regarding compression etc. *) backup: what is a best practice regarding backups? - using only the dovecot tools or leveraging the great features of ZFS (or both) with snapshots etc.? Thanks for all sorts of infos, probably saving me quite some time evaluating different options! Robert

5 6

Mailinglistserver IPv6 address blacklisted
by Arjen de Korte 21 Nov '21

21 Nov '21

It looks like the mailinglist server IPv6 address has been blacklisted: https://check.spamhaus.org/listed/?searchterm=2a04:3545:1000:720:acc1:5bff:… The 'Show details' shows the entire 2a04:3545:1000:720::/64 network is blacklisted. Whois tells this is a network used by UpCloud Cloud Servers. So either the mailinglistserver or a server it shares its network with is compromised. If UpCloud gives its users their own /64, it would probably be the former. Otherwise it might make sense to ask them for one, as sharing IPv6 networks between customers is a no-no in the IPv6 world.

2 1

Solr FTS - message deletes not working as expected
by Shawn Heisey 19 Nov '21

19 Nov '21

I have Solr FTS enabled in dovecot. It is behaving differently than I would expect. When I delete messages in Thunderbird normally, using IMAP to talk to dovecot, the deletion hits Solr right away. If I then ask Thunderbird to empty the trash, that delete also hits Solr immediately. But if I use shift-delete in Thunderbird, which deletes the message immediately without going through Trash, things are different. One delete that I did (6 messages) took at least a minute before Solr saw the request. And on other tests that I ran, deleting one message, I never did see the delete request hit Solr. I waited for several minutes. I use the shift-delete mechanism a lot more than the method that sends to trash. That way I do not need to remember to empty the trash. Dovecot version is 2:2.3.16-2+ubuntu20.04 installed from the dovecot repo, not from distro packages. I don't think the Solr version matters, but just in case I am wrong, that is 8.10.1. I don't recall exactly what I changed in the solrconfig.xml and managed-schema files, but it should not be anything that affects how Solr FTS works. The problem seems to be that Solr FTS isn't sending deletes, not that Solr is behaving incorrectly. I just discovered that trying to get the dovecot config failed: root@bilbo:~# doveconf -n # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-master.conf line 64: Invalid size: $default_vsz_limit After fixing that, this is what I get for the config: root@bilbo:/etc/dovecot# doveconf -n # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.11.0-1020-aws x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: REDACTED default_vsz_limit = 1 G dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } first_valid_uid = 150 last_valid_uid = 150 listen = * mail_gid = mail mail_location = maildir:/var/vmail/%d/%u mail_plugins = " quota fts fts_solr" mail_privileged_group = mail 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 index ihave duplicate mime foreverypart extracttext namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = solr fts_autoindex = yes fts_solr = url=http://localhost:8983/solr/dovecot/ quota = dict:User quota::proxy::quota quota_grace = 10%% quota_max_mail_size = 100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO sieve = file:/var/vmail/sieve/%d/%u/sieve;active=/var/vmail/sieve/%d/%u/.dovecot.sieve sieve_default = file:/var/vmail/global.sieve } postmaster_address = postmaster@REDACTED protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = mail mode = 0666 user = vmail } } service dict { unix_listener dict { group = postfix mode = 0660 user = vmail } } service imap { vsz_limit = 1 G } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = </etc/ssl/certs/local/mainwildcards.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota fts fts_solr sieve" } protocol lda { mail_plugins = " quota fts fts_solr sieve" } protocol imap { mail_max_userip_connections = 20 mail_plugins = " quota fts fts_solr imap_quota" } I repeated the delete test after fixing the config and there was no change -- the delete request never made it to Solr. Reindexing completely for my dovecot install takes about 8 minutes. I have less than 150K messages. Reindexing for some could take hours or days. This is what I use to initiate a full reindex: root@bilbo:~# cat /usr/local/sbin/reindexsolr #!/bin/sh DOVECOT_SOLR_URL_BASE="http://localhost:8983/solr/dovecot" DEL_ALL_QUERY_XML="<delete><query>*:*</query></delete>" MAIL_ROOT=/var/vmail service dovecot stop curl \ "${DOVECOT_SOLR_URL_BASE}/update?commit=true&optimize=true" \ -H "Content-Type: text/xml" \ --data-binary "${DEL_ALL_QUERY_XML}" find ${MAIL_ROOT} -name "dovecot.index*" -print0 | xargs -0 rm -f service dovecot start doveadm index -A -q '*'

3 11

FTS config - cannot search substrings
by infoomatic 19 Nov '21

19 Nov '21

Hi, I have an issue with FTS, maybe someone here can help me out. Basically my setup is working with solr + tika enabled, however, it seems my search is not configured the way I expect it. Eg when I receive a pdf document containing the word "myfoobar" I cannot search for "myfoo" or "foobar", but searching for "myfoobar" shows the right result. Any ideas? Thanks!

2 2