- dovecot - dovecot.org

Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted
by Jesús Ángel del Pozo 25 Nov '21

25 Nov '21

Hello, I know maildir format does not allow to delete INBOX as stated in https://dovecot.org/list/dovecot/2016-January/102988.html. Nevertheless, even though I deleted the entire Maildir manually with rm -rf, doveadm backup fails with "Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted". I would like to make a user's maildir backup to a different folder. For example: rm -rf /tmp/zbbb/; doveadm backup -u test(a)disguised.domain.com maildir:/tmp/zbbb/ But I keep receiving this error message: Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted Do you know what might be causing this problem? If I use sdbox instead of maildir, the backup works: rm -rf /tmp/zbbb/; doveadm backup -u test(a)disguised.domain.com sdbox:/tmp/zbbb/ However, I would like to use maildir format for the backup as all my mailboxes use this format. Regards,

1 0

sieve discard option debug
by Jose Manuel 24 Nov '21

24 Nov '21

Hi, i have a question if someone can help me with this. My sieve file configuration is this: cat enabled_script.sieve require ["fileinto"]; if header :contains "subject" "@ggmaail.com" { fileinto "INBOX.Spam"; } elsif header :contains "subject" "TW" { discard; elsif header :contains :comparator "i;octet" "X-Spam-Status" "autolearn=spam" { discard; } When the condition is true and a mail is discard i can not discriminate in the logs what was the reason. 1) "subject" "@ggmail.com" or 2) "subject" "TW" I can only see this message over the logs: February 15th 2021, 17:39:33.000 lmtp(mail(a)mail.domain)<27188><kJhTEMWjKmA0agAAaUS+oQ>: sieve: msgid=<001701d703b9$234a8b80$69dfa280$(a)correo.es> <001701d703b9$234a8b80$69dfa280$(a)correo.es>: marked message to be discarded if not explicitly delivered (discard action) (Note: i changed the domain names) My question is: Can i setup or add any option in my sieve filter for more info about the discard reason ??? Any rules together with the discard option ? I am out of idea about it. Thanks in advanced!!!

2 1

doing good job answering all these questions so quickly Aki and Team
by Marc 24 Nov '21

24 Nov '21

Just want to say, doing good job answering all these questions so quickly Aki and Team! :) > -----Original Message----- > From: dovecot <dovecot-bounces(a)dovecot.org> On Behalf Of Aki Tuomi > Sent: Wednesday, 24 November 2021 08:02 > To: fugee ohu <fugee279(a)gmail.com>; dovecot(a)dovecot.org > Subject: Re: Connection refused > > 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

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