- dovecot - dovecot.org

Re: dovecot v2.3.0: imap segfault when sieve_extprograms_plugin.so called
by Daniel Kenzelmann 04 Jan '18

04 Jan '18

That's the point, the fix was committed afterwards... https://github.com/dovecot/pigeonhole/commit/321a39be974deb2e7eff7b2a50 9a3ee6ff2e5ae1 So, any 0.5.1 release on the horizon? Thanks, Daniel Am Mittwoch, den 03.01.2018, 22:14 +0200 schrieb Aki Tuomi: > pigeonhole 0.5.0 has been already released... > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: Daniel Kenzelmann <dovecot.org(a)k8n.de> > Date: 03/01/2018 21:31 (GMT+02:00) > To: Rhys Williams <lux+mailinglists(a)melted.me>, dovecot(a)dovecot.org > Subject: Re: dovecot v2.3.0: imap segfault when > sieve_extprograms_plugin.so called > > Hi, > > see the following thread: > > https://www.dovecot.org/pipermail/dovecot/2017-December/110448.html > > We need to wait for an updated pigeonhole/dovecot... :-( > > Is there maybe some ETA for an updated release? (just wondering if it > makes sense to create an updated ebuild with the patch for gentoo) > > -Daniel > > > Am Mittwoch, den 03.01.2018, 18:12 +0000 schrieb Rhys Williams: > > Hi, > > > > I have recently upgraded to dovecot v2.3 on Ubuntu 16.04.3 from > > repo.dovecot.org and I switched to IMAPSieve for rspamd with the > > guide from the wiki. When a mail is moved from Junk to another > Inbox > > or vice-versa imap segfaults. > > > > I have posted debug logs and versions below, any help will be > greatly > > appreciated. > > > > Thanks, > > Rhys Williams > > > > lux@bifrost:~$ dovecot --version > > 2.3.0 (c8b89eb) > > > > lux@bifrost:~$ uname -a > > Linux bifrost 4.10.0-43-generic #47~16.04.1-Ubuntu SMP Wed Dec 13 > > 19:23:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > > > > Log of the crash: https://paste.ubuntu.com/26314370/ (https://paste > .u > > buntu.com/26314370/) > > Core dump: https://paste.ubuntu.com/26314349/ (https://paste.ubuntu > .c > > om/26314349/) > > dovecot -n: https://paste.ubuntu.com/26314365/ (https://paste.ubunt > u. > > com/26314365/)

2 1

Dovecot auth SASL for exim and plain auth issue without initial response
by Daniel Kenzelmann 04 Jan '18

04 Jan '18

Hi, I'm not entirely sure whether this issue is with exim or with dovecot. First some background: I'm using exim with dovecot-auth which in turn is using LDAP for authentication. When using AUTH PLAIN with the optional initial response argument, everything is fine. However when using AUTH PLAIN without the optional response argument, instead of getting an empty challenge ("334 ") as per RFC i am getting a "535 Incorrect authentication data". Example: Working: 220 XXXX ESMTP 2018-01-02 22:32:33+0100 EHLO test 250-XXXX Hello XXXXX [x.x.x.x] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250-AUTH PLAIN LOGIN 250-CHUNKING 250 HELP AUTH PLAIN XXXXXXXXXXXXXXXXXXXXXXXX== 235 Authentication succeeded NOT-WORKING: 220 XXXX ESMTP 2018-01-02 22:34:37+0100 EHLO test 250-XXXX Hello XXXXX [x.x.x.x] 250-SIZE 52428800 250-8BITMIME 250-PIPELINING 250-AUTH PLAIN LOGIN 250-CHUNKING 250 HELP AUTH PLAIN 535 Incorrect authentication data Here the SASL mechanism should return an empty challenge as per RFC (i.e. "334 " in SMTP): RFC 4954 - SMTP Service Extension for Authentication 4. The AUTH Command [..] The optional initial response argument to the AUTH command is used to save a round-trip when using authentication mechanisms that support an initial client response. ====> If the initial ====> response argument is omitted and the chosen mechanism requires ====> an initial client response, the server MUST proceed as defined ====> in Section 5.1 of [SASL]. In SMTP, a server challenge that ====> contains no data is defined as a 334 reply with no text part. ====> Note that there is still a space following the reply code, so ====> the complete response line is "334 ". [..] RFC 4422 - Simple Authentication and Security Layer (SASL) 5. Mechanism Requirements SASL mechanism specifications MUST supply the following information: 1) The name of the mechanism (see Section 3.1). This name MUST be registered as discussed in Section 7.1. 2) A definition of the server-challenges and client-responses of the authentication exchange, as well as the following: a) An indication of whether the mechanism is client-first, variable, or server-first. ===> If a SASL mechanism is defined as ===> client-first and the client does not send an initial response ===> in the authentication request, then the first server challenge ===> MUST be empty (the EXTERNAL mechanism is an example of this case). If a SASL mechanism is defined as variable, then the specification needs to state how the server behaves when the initial client response in the authentication request is omitted (the DIGEST-MD5 mechanism [DIGEST-MD5] is an example of this case). If a SASL mechanism is defined as server-first, then the client MUST NOT send an initial client response in the authentication request (the CRAM-MD5 mechanism [CRAM-MD5] is an example of this case). Thanks, Daniel

2 5

Dovecot panic for one user after upgrading
by Owen B. Mehegan 04 Jan '18

04 Jan '18

The EC2 instance that I run Dovecot on (personal mail server) was forcibly "retired" yesterday, and as a result I ended up rebuilding from backups. In the process I switched from Ubuntu Precise to Ubuntu Xenial (12.04 to 16.04), and this in turn caused me to upgrade Dovecot from 2.0.19 to 2.0.22. Now, although accessing mail seems to work OK using my various clients, I am seeing these errors in my logs: Jan 3 05:56:58 -- dovecot: imap(owen): Panic: file mail-index-sync-keywords.c: line 227 (keywords_update_records): assertion failed: (data_offset >= sizeof(struct mail_index_record)) Jan 3 05:56:58 -- dovecot: imap(owen): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7aee2) [0x7fe9c08dbee2] -> /usr/lib/dovecot/libdovecot.so.0(+0x7afcd) [0x7fe9c08dbfcd] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fe9c0880a61] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x828) [0x7fe9c0c1fdd8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xef) [0x7fe9c0c2079f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x238) [0x7fe9c0c21758] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_map+0x71) [0x7fe9c0c18de1] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd28fd) [0x7fe9c0c2e8fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd2f03) [0x7fe9c0c2ef03] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_open+0x78) [0x7fe9c0c2efe8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_open+0x92) [0x7fe9c0c08042] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5e8d2) [0x7fe9c0bba8d2] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5e9b8) [0x7fe9c0bba9b8] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x37b86) [0x7fe9c0b93b86] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_open+0x20) [0x7fe9c0b93d00] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x20) [0x7fe9c0c073b0] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x37) [0x7fe9c0b940e7] -> dovecot/imap(imap_status_get+0x77) [0x55d3b4c3f977] -> dovecot/imap(cmd_status+0x1a9) [0x55d3b4c32969] -> dovecot/imap(command_exec+0x9c) [0x55d3b4c3806c] -> dovecot/imap(+0x193e2) [0x55d3b4c363e2] -> dovecot/imap(+0x1946c) [0x55d3b4c3646c] -> dovecot/imap(client_handle_input+0x165) [0x55d3b4c36825] -> dovecot/imap(client_input+0x82) [0x55d3b4c36db2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7fe9c08efc6c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7fe9c08f1101] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7fe9c08efcf5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7fe9c08efe98] Jan 3 05:56:59 -- dovecot: imap(owen): Fatal: master: service(imap): child 18289 killed with signal 6 (core dumped) I have deleted the dovecot.* files in the Maildir for all users (did this while Dovecot was stopped, then started it again), but the errors persist. They are especially frequent for one particular user. I can't figure out where the core file is, it doesn't seem to be in my home or in /var/run/dovecot Here's my dovecot -n output: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-1043-aws x86_64 Ubuntu 16.04.3 LTS mail_location = maildir:~/Maildir 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 } protocols = " imap" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/letsencrypt/live/mydomain/cert.pem ssl_key = </etc/letsencrypt/live/mydomain/privkey.pem userdb { driver = passwd } Thanks in advance for any support you can offer!

2 2

dovecot v2.3.0: imap segfault when sieve_extprograms_plugin.so called
by Rhys Williams 03 Jan '18

03 Jan '18

Hi, I have recently upgraded to dovecot v2.3 on Ubuntu 16.04.3 from repo.dovecot.org and I switched to IMAPSieve for rspamd with the guide from the wiki. When a mail is moved from Junk to another Inbox or vice-versa imap segfaults. I have posted debug logs and versions below, any help will be greatly appreciated. Thanks, Rhys Williams lux@bifrost:~$ dovecot --version 2.3.0 (c8b89eb) lux@bifrost:~$ uname -a Linux bifrost 4.10.0-43-generic #47~16.04.1-Ubuntu SMP Wed Dec 13 19:23:27 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Log of the crash: https://paste.ubuntu.com/26314370/ (https://paste.ubuntu.com/26314370/) Core dump: https://paste.ubuntu.com/26314349/ (https://paste.ubuntu.com/26314349/) dovecot -n: https://paste.ubuntu.com/26314365/ (https://paste.ubuntu.com/26314365/)

3 3

Problem with master password
by Harald Leithner 03 Jan '18

03 Jan '18

Hi, I have a problem using the master password feature of dovecot. I'm able to login with the password but then dovecot can't select the INBOX. IMAP test: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=SCRAM-SHA-1 AUTH=CRAM-MD5] ITronic Mail Store a login user(a)itronic.at*admin password a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE NOTIFY QUOTA ACL RIGHTS=texk] Logged in a list "" "%" * LIST (\HasNoChildren) "/" INBOX a OK List completed (0.003 + 0.000 + 0.003 secs). a select INBOX a NO [SERVERBUG] Internal error occurred. Refer to server log for more information. [2017-12-28 12:32:41] (0.001 + 0.000 secs). The log with mail debuging doesn't tell me much: 2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(user(a)itronic.at): Debug: INBOX: Mailbox opened because: SELECT 2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(user(a)itronic.at): Debug: acl vfile: file /srv/storage1/vmail/itronic/6/mdbox/mailboxes/INBOX/dbox-Mails/dovecot-acl not found 2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(user(a)itronic.at): Debug: acl vfile: file /srv/storage1/vmail/itronic/6/mdbox/mailboxes/dovecot-acl not found 2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(user(a)itronic.at): Debug: Namespace : Using permissions from /srv/storage1/vmail/itronic/6/mdbox: mode=0700 gid=default 2017-12-28T12:24:47+01:00 mailstore1 dovecot: imap(user(a)itronic.at): Error: Opening INBOX failed: Mailbox doesn't exist: INBOX If I use the password of the user it works without problems, I also tested other users, they have the same problem. dovecot -n # 2.2.devel (5af0c9f): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (6c95b56) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.10 auth_cache_negative_ttl = 1 secs auth_cache_size = 10 M auth_cache_ttl = 1 secs auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN DIGEST-MD5 SCRAM-SHA-1 CRAM-MD5 APOP auth_verbose = yes default_client_limit = 600 default_vsz_limit = 512 M dict { lastlogin = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlacl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 1001 first_valid_uid = 1001 hostname = mailstore1(a)itronic.at imap_hibernate_timeout = 1 mins imap_id_log = * imap_id_send = * imap_idle_notify_interval = 10 mins imap_logout_format = bytes=%i/%o instance_name = mailstore1 last_valid_gid = 1001 last_valid_uid = 1001 lda_original_recipient_header = X-LDA-Original-To lmtp_rcpt_check_quota = yes login_greeting = ITronic Mail Store login_trusted_networks = x.y.z.0/24 mail_attachment_dir = /srv/storage1/vmail_sis mail_attachment_hash = %{sha512} mail_attachment_min_size = 64 k mail_cache_min_mail_count = 5 mail_gid = vmail mail_location = mdbox:~/mdbox mail_plugins = zlib lazy_expunge stats acl quota mail_log notify mail_prefetch_count = 100 mail_server_admin = mailto:postmaster@itronic.at mail_server_comment = ITronic Mail System mail_shared_explicit_inbox = yes mail_uid = vmail mailbox_list_index = yes 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 vacation-seconds mdbox_preallocate_space = yes namespace { hidden = yes list = no location = mdbox:~/mdbox:MAILBOXDIR=expunged:LISTINDEX=expunged.list.index prefix = "#EXPUNGED/" subscriptions = no type = private } namespace { list = children location = mdbox:%%h/mdbox prefix = "#Users/%%u/" separator = / subscriptions = yes type = shared } namespace inbox { hidden = no inbox = yes location = mailbox Archvie { special_use = \Archive } mailbox Drafts { special_use = \Drafts } mailbox Sent { special_use = \Sent } mailbox Spam { special_use = \Junk } mailbox Trash { special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::sqlacl last_login_dict = proxy::lastlogin last_login_key = last-login/%u lazy_expunge = "#EXPUNGED/" lazy_expunge_only_last_instance = no mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mailbox_create mail_log_fields = uid box msgid size flags vsize from subject quota = dict:User quota::proxy::sqlquota quota_grace = 10%% quota_rule = *:storage=1024M quota_rule2 = "#EXPUNGED:storage=+1024M" quota_warning = storage=100%% quota-warning 100 %u quota_warning2 = storage=95%% quota-warning 95 %u quota_warning3 = storage=80%% quota-warning 80 %u recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = file:/srv/storage1/vmail/%{userdb:accountToken}/ sieve_extensions = +vacation-seconds sieve_global = /etc/dovecot/sieve sieve_max_actions = 64 sieve_max_redirects = 8 sieve_max_script_size = 2M sieve_quota_max_scripts = 0 sieve_quota_max_storage = 64M sieve_vacation_default_period = 1d sieve_vacation_min_period = 1h stats_refresh = 30 secs stats_track_cmds = yes zlib_save = gz zlib_save_level = 6 } pop3_uidl_duplicates = rename protocols = imap lmtp sieve pop3 service auth-worker { user = $default_internal_user } service auth { inet_listener { port = 4180 } unix_listener auth-userdb { mode = 0666 } } service dict { unix_listener dict { group = vmail mode = 0666 } } service imap-hibernate { unix_listener imap-hibernate { group = vmail mode = 0666 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 1 service_count = 0 } service imap { process_limit = 1024 unix_listener imap-master { user = dovecot } unix_listener imap { group = vmail mode = 0666 } vsz_limit = 512 M } service lmtp { inet_listener lmtp { address = x.y.z.135 port = 24000 } unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service managesieve { process_limit = 50 } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_min_avail = 20 service_count = 1 vsz_limit = 64 M } service pop3 { process_limit = 1024 } service quota-warning { executable = script /opt/scripts/quota-warning.sh unix_listener quota-warning { user = vmail } user = dovecot } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } shutdown_clients = no ssl_cert = </etc/dovecot/private/STAR.itronic.at.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA:AES256-SHA:DHE-RSA-CAMELLIA128-SHA:DHE-RSA-CAMELLIA256-SHA:CAMELLIA128-SHA:CAMELLIA256-SHA:ECDHE-RSA-DES-CBC3-SHA:DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_options = no_compression ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv2 !SSLv3 submission_host = x.y.z.198 syslog_facility = local0 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } valid_chroot_dirs = /srv/storage1/vmail verbose_proctitle = yes protocol imap { mail_max_userip_connections = 30 mail_plugins = zlib lazy_expunge stats imap_stats quota imap_quota acl imap_acl last_login mail_log notify } protocol lda { mail_plugins = zlib lazy_expunge stats acl sieve quota mail_log notify } protocol lmtp { mail_plugins = zlib lazy_expunge stats acl sieve quota mail_log notify } protocol sieve { mail_max_userip_connections = 10 managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } protocol pop3 { mail_max_userip_connections = 10 mail_plugins = zlib lazy_expunge stats acl last_login mail_log notify } ----- I would be happy for any debugging help. thx -- Harald Leithner ITronic Wiedner Hauptstraße 120/5.1, 1050 Wien, Austria Tel: +43-1-545 0 604 Mobil: +43-699-123 78 4 78 Mail: leithner(a)itronic.at | itronic.at

2 2

sieve - Failed to store into mailbox 'INBOX/${1}': Mailbox doesn't exist: INBOX/${1}
by Ludovic Terrier 02 Jan '18

02 Jan '18

Hello, First of all, happy new year! I’ve recently configured my mail server and was using a simple sieve rule in order to store all my ‘user+pattern(a)example.xn--com-to0a ingoing email to be stored in the INBOX/pattern folder. This setup worked very well. I restarted my server this morning (don’t know if it’s related…) and since Dovecot keep storing my emails in INBOX with following errors: root@server:~# cat /var/mail/vhosts/example.com/ludovic/.dovecot.sieve.log sieve: info: started log at Jan 01 12:13:56. error: msgid=<20180101111353.C332C25386(a)server.example.com>: failed to store into mailbox 'INBOX/${1}': Mailbox doesn't exist: INBOX/${1}. Sieve script: root@server:~# cat /var/mail/vhosts/example.com/ludovic/sieve/roundcube.sieve require ["envelope","fileinto","subaddress"]; if header :contains "X-Spam-Flag" "YES" { fileinto "Junk"; } if envelope :detail :matches "to" "*" { fileinto "INBOX/${1}"; } # rule:[contact] if allof (header :contains "to" "contact(a)example.com") { fileinto "INBOX/contact"; stop; } I don’t remember having made recent change in my Dovecot config… only adding the last rule in the sieve script. Any hint? Thanks. Please find below more info of my Dovecot setup (quite long). Is it better to use some pastebin for such long info? Regards, ----------------------------------------------------------------------------------------------------------------------------------------------------------------- Info (version and dovecot -n): root@server:~# dovecot --version 2.2.27 (c0f36b0) root@helios:~# dovecot -n # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1524) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.3 auth_cache_size = 10 M auth_username_format = %Ln first_valid_uid = 999 imap_idle_notify_interval = 29 mins last_valid_uid = 999 mail_attachment_dir = /var/mail/attachments mail_attachment_min_size = 64 k mail_fsync = never mail_home = /var/mail/vhosts/%d/%n mail_location = mdbox:~/mdbox 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 imapsieve namespace inbox { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { imapsieve_mailbox1_before = file:/etc/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = Junk imapsieve_mailbox2_before = file:/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = Junk imapsieve_mailbox2_name = * recipient_delimiter = + sieve = file:~/sieve;active=~/.dovecot.sieve sieve_after = /usr/local/etc/dovecot/sieve-after.d sieve_before = /usr/local/etc/dovecot/sieve-before.d sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve sieve_plugins = sieve_imapsieve sieve_extprograms sieve_quota_max_storage = 50M } protocols = " imap lmtp sieve sieve" service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { address = 127.0.0.1, ::1 } process_min_avail = 2 service_count = 0 vsz_limit = 1 G } service imap { process_min_avail = 2 service_count = 256 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 0 } } ssl = required ssl_cert = </etc/letsencrypt/pem/server.example.com.pem ssl_cipher_list = ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256 ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes ssl_protocols = !SSLv3 !TLSv1 !TLSv1.1 TLSv1.2 userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } protocol lmtp { mail_fsync = optimized mail_plugins = " sieve" } protocol lda { mail_fsync = optimized mail_plugins = " sieve" } protocol imap { mail_max_userip_connections = 50 mail_plugins = " imap_sieve » } ----------------------------------------------------------------------------------------------------------------------------------------------------------------- — Ludovic

2 2

dovecot-pigeonhole problems after upgrade to v2.3.0
by Fabian A. Santiago 02 Jan '18

02 Jan '18

Hello, After upgrading to dovecot 2.3.0, my sieve filtering is broken. I managed it via roundcube's managesieve plugin. my emails are not being filtered accordingly into their folders and when i attempt to access the filter interface in roundcube, my maillog reports: Dec 28 12:05:07 mail roundcube: <gs7miohh> PHP Error: Unable to connect to managesieve on 127.0.0.1:4190 in /var/www/roundcubemail/plugins/managesieve/lib/Roundcube/rcube_sieve_engine.php on line 222 (GET /mail/?_task=settings&_action=plugin.managesieve) Dec 28 12:05:07 mail roundcube: ERROR: Not currently in AUTHORISATION state (1) Dec 28 12:05:07 mail httpd: ERROR: Failed to write to socket: connection lost () Now I'm willing to consider the possibility that the RC plugin doesn't work with v2.3.0 of dovecot sieve but why wouldn't my current sieve filters be functional? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

4 14

Dbox and NVMe drives
by Andrew 02 Jan '18

02 Jan '18

Hi all, We're looking at replacing our existing NFS setup and using local storage on multiple nodes - using Director to send clients to the correct node. We have about 10,000 mailboxes using about 6TB at the moment, a mix of IMAP and POP, probably 65% IMAP. I'm thinking of moving from Maildir to Dbox; using 2TB NVMe drives in RAID1 as primary storage and 4x 6TB SATA disks in RAID10 for altstorage and probably smaller SATA SSDs in RAID1 for the indexes. I guess my question is, have other people had bad experiences with flash based storage on medium sized mail servers and does splitting the storage like these seem sensible for Dbox in terms of maximizing performance? Thanks! S.

1 0

Sieve can't move messages in a public namespace
by Paolo 02 Jan '18

02 Jan '18

Hello, my dovecot version is 2.1.17 I've configured some public namespaces (config attached). When a mail arrives at a certain mail address, that mail is handled by dovecot lmtp server and a sieve script is executed that shuold move the message in one of the namespaces. This is the script: require "fileinto"; if header :contains "From" "example(a)example.com" { fileinto :create "Cond-UFF_FORNITORI/CONTABILITA/Inviata"; } else { fileinto :create "Cond-UFF_FORNITORI/CONTABILITA/Ricevuta"; } The problem is that the sieve script fails with the error: sieve: info: started log at Jun 27 12:42:28. error: msgid=<c9154db4-ff68-52a3-2639-11f09f225f68(a)fcr.re.it>: failed to store into mailbox 'Cond-UFF_FORNITORI/CONTABILITA/Ricevuta': Mailbox doesn't exist: Cond-UFF_FORNITORI/CONTABILITA/Ricevuta. I double checked config, dovecot documentation, sieve documentation, ACL, filesystem paths, filesystem permissions, etc. etc. I'm pretty sure it's all right. So why isn't sieve working? Thanks if you bother to answer & Cheers Paolo

4 6

dovecot-submission SMTP send error with Thunderbird (BODY=8BITMIME)
by Reuben Farrelly 02 Jan '18

02 Jan '18

Hi, With latest 2.3 -git (and 2.3.0 release), I'm running into this error with Thunderbird: "An error occurred while sending mail. The mail server responded: 5.5.4 Unsupported mail BODY type. Please verify that your email address is correct in your account settings and try again." This is fatal and means Thunderbird cannot use the submission service - fortunately I can revert back to a native Postfix service which works. Here's a tcpdump of the conversation: thunderstorm /etc/dovecot/conf.d # tcpdump -A port 587 dropped privs to tcpdump tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 262144 bytes 14:12:19.975982 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [S], seq 572328223, win 64800, options [mss 1440,nop,wscale 8,nop,nop,sackOK], length 0 `._.. .? .D.1...E.....>. .D.1..........#...K". ........ .w.............. 14:12:19.976022 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [S.], seq 3954361671, ack 572328224, win 28800, options [mss 1440,nop,nop,sackOK,nop,wscale 7], length 0 `.c|. .@ .D.1..........# .D.1...E.....>..K.....G". ..p.:4.............. 14:12:19.976158 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [.], ack 1, win 8235, length 0 `._....? .D.1...E.....>. .D.1..........#...K". ...HP. +. .. 14:12:19.983409 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 1:43, ack 1, win 225, length 42 `.c|.>.@ .D.1..........# .D.1...E.....>..K.....H". P...:R..220 thunderstorm.reub.net Dovecot ready. 14:12:19.992790 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [P.], seq 1:54, ack 43, win 8234, length 53 `._..I.? .D.1...E.....>. .D.1..........#...K". ...rP. *.H..EHLO [IPv6:2001:44b8:31d4:1311:45ec:e191:8093:3e9d] 14:12:19.992828 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [.], ack 54, win 225, length 0 `.c|...@ .D.1..........# .D.1...E.....>..K.....r". UP...:(.. 14:12:19.993027 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 43:200, ack 54, win 225, length 157 `.c|...@ .D.1..........# .D.1...E.....>..K.....r". UP...:...250-thunderstorm.reub.net 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING 14:12:20.015953 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [P.], seq 54:91, ack 200, win 8234, length 37 `._..9.? .D.1...E.....>. .D.1..........#...K". U....P. *....AUTH PLAIN xxxx 14:12:20.035676 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 200:222, ack 91, win 225, length 22 `.c|.*.@ .D.1..........# .D.1...E.....>..K......". zP...:>..235 2.7.0 Logged in. 14:12:20.036642 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [P.], seq 91:143, ack 222, win 8234, length 52 `._..H.? .D.1...E.....>. .D.1..........#...K". z...%P. *....MAIL FROM:<xxx(a)reub.net> BODY=8BITMIME SIZE=444 14:12:20.036826 IP6 inside-mail.reub.net.submission > 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175: Flags [P.], seq 222:260, ack 143, win 225, length 38 `.c|.:.@ .D.1..........# .D.1...E.....>..K.....%". .P...:N..555 5.5.4 Unsupported mail BODY type 14:12:20.089196 IP6 2001:44b8:31d4:1311:45ec:e191:8093:3e9d.61175 > inside-mail.reub.net.submission: Flags [.], ack 260, win 8233, length 0 `._....? .D.1...E.....>. .D.1..........#...K". ....KP. ).... Curiously enabling rawlog doesn't capture this error, which is why I used tcpdump above. The logs from it like this: thunderstorm /run/dovecot/rawlogs # cat 20171219-141149.5633.1.in 1513653109.109030 220 thunderstorm.reub.net ESMTP Postfix (3.3-20171028) 1513653109.109266 250-thunderstorm.reub.net 1513653109.109266 250-PIPELINING 1513653109.109266 250-SIZE 40960000 1513653109.109266 250-VRFY 1513653109.109266 250-ETRN 1513653109.109266 250-STARTTLS 1513653109.109266 250-ENHANCEDSTATUSCODES 1513653109.109266 250-8BITMIME 1513653109.109266 250-DSN 1513653109.109266 250 SMTPUTF8 1513653130.973720 221 2.0.0 Bye thunderstorm /run/dovecot/rawlogs # cat 20171219-141149.5633.1.out 1513653109.109087 EHLO thunderstorm.reub.net 1513653130.973351 QUIT 1513653130.973829 QUIT thunderstorm /run/dovecot/rawlogs # This with: # Write protocol logs for relay connection to this directory for debugging #submission_relay_rawlog_dir = submission_relay_rawlog_dir = /run/dovecot/rawlogs/ Is this a separate but unrelated problem with rawlog support in this the submission? I would have expected it to capture the full conversation log including any protocol errors and failures like this. Reuben

3 5

Re: Random delivery
by Joseph Tam 01 Jan '18

01 Jan '18

"Jorge Bastos" <mysql.jorge(a)decimal.pt> writes: > I?d like to achieve something that i don?t know if it?s possible. It's almost always possible; it really depends on how much work you want to do. > I have account info(a)domain.tld and when an email is received, I want to > forward it to several accounts, always in this order: > > ? Email1(a)domain.tlf > ? Email2(a)domain.tld > ? Email3(a)domain.tld Others have suggested a postfix method. You can also pipe it to a script that will select a destination to forward to alias "info(a)domain.tld" to "|/my/selector|script". This will work both in Postfix, sendmail, and probably most other MTAs. If you actually want randomization (rather than sequential round-robin), you can simplify because you won't need to record the last delivery. Use /dev/urandom or unix time() mod 3 to select forwarding address. Joseph Tam <jtam.home(a)gmail.com>

3 2

User is only found if globed at the end
by Palav Palavets 01 Jan '18

01 Jan '18

User is only found if globed at the end: [root@www conf.d]# dovecot --version 2.2.10 [root@www conf.d]# cat /etc/accounts test@example.com:{CRYPT}pEZfBPqH83Nuo [ root@www conf.d]# doveadm user "test(a)example.com" field valueuserdb lookup: user test(a)example.com doesn't exist [root@www conf.d]# doveadm user "test(a)examplel.com*" test(a)example.com [root@www conf.d]# file /etc/accounts /etc/accounts: ASCII text

1 0

Re: Random delivery
by Andreas Born 31 Dec '17

31 Dec '17

Jorge Bastos wrote: > I have account info(a)domain.tld and when an email is received, I want to > forward it to several accounts, always in this order: > > ð Email1(a)domain.tlf > ð Email2(a)domain.tld > ð Email3(a)domain.tld > > And when it reached email3(a)domain.tld it starts again with email1(a)domain.tld > > Would something like this be possible? If you use the sql driver for userdb lookups, you could do this by means of your mysql lookup query. Just implement a counter and adapt the appropriate INBOX setting für the "mail" variable in the result set.

1 0

Adding Sieve to Roundcube
by ＠lbutlr 31 Dec '17

31 Dec '17

I'm planning on adding support for sieve to Roundcube here in the near future and am looking for any recommendations on read-mes on how to do this. I am planning on waiting until 2.3.0 hits Freebsd Ports -- No Sigs. Blame Apple.

5 6

Package repository now available
by aki.tuomi＠dovecot.fi 30 Dec '17

30 Dec '17

Dovecot now has package repository for Debian, CentOS and Ubuntu available at https://repo.dovecot.org/ Packages are provided for 2.3 series and forward. Please let us know if you run into any trouble with these. --- Aki Tuomi Dovecot oy

8 16

Automatic Debian repository (Xi) updated
by Stephan Bosch 29 Dec '17

29 Dec '17

Hi, Now that we have a new Dovecot v2.3 release, I've created a new Xi builder that follows the git master branch to automatically produce Debian packages for the future Dovecot v2.4. The existing v2.3 repository now follows the master-2.3 branch, meaning that this will only follow developments/fixes ported to the v2.3 stable release series. This was already true for the v2.2 oldstable packages. All repositories now finally have the capability of updating version numbers automatically based on releases (as it used to be before we switched to git). This operates a little different than before though: the normal (alpha) repositories produce packages with a version that has an "~alpha" suffix. The base version represents the *next* release version, rather than the current as it was before. So, if the last Dovecot release was 2.3.0, Xi will release packages with version 2.3.1~alpha0, which is the version we're working towards. Another development is that the builders for v2.2 and v2.3 also follow the release-2.x.y branches once these are created. These branches are forked from the respective master-2.x branch once the first release candidate for a release is to be created, so that packages produced in this stream will follow those developments, including the actual release (and any small patch releases that may follow). Unlike the alpha packages, rc packages have a base version that matches the release version. Packages for the release branches are output to separate repository. While e.g. the repository for automatic packages for Debian stable is called "stable-auto", the release branch packages are published to a repository called "stable-rc-auto". The /etc/apt/sources.list line for that would look as follows: deb http://xi.dovecot.fi/debian/ stable-rc-auto/dovecot-2.3 main Keep in mind that, while the rc repositories will have a little more stability, these are still produced fully automatically without any regular human supervision. Using these for production systems is therefore not recommended. Also, since this is a new feature, these repositories are still to be considered experimental. IMPORTANT: Much of this work was prepared and tested earlier in the http://xi.dovecot.fi/debian.new repository. This repository is now shut down and will not be updated anymore. Therefore, all of you who have switched to that repository must switch back to the normal one. As you know, Dovecot now operates a repository with v2.3 packages for the community edition. Unlike Xi, the production of these packages is triggered manually and the resulting packages are suitable for production systems. Xi is still the repository to use if you wish to follow very recent developments (within the hour!) for testing purposes. Regards, Stephan.

1 0

Re: Random delivery
by Aki Tuomi 29 Dec '17

29 Dec '17

Not sure how this is random ... =) So you want it to deliver a the mail to first email1, next email to email2, next to email3, and next to email1. I am pretty sure you can do this better with postfix with transport that redirects it to one of these accounts in order. Aki > On December 29, 2017 at 2:09 AM Jorge Bastos <mysql.jorge(a)decimal.pt> wrote: > > > Howdy, > > > > Id like to achieve something that i dont know if its possible. > > > > I have account info(a)domain.tld and when an email is received, I want to > forward it to several accounts, always in this order: > > > > ð Email1(a)domain.tlf > > ð Email2(a)domain.tld > > ð Email3(a)domain.tld > > > > And when it reached email3(a)domain.tld it starts again with email1(a)domain.tld > > > > Would something like this be possible? >

1 0

doveconf -n not showing all changes
by Marc Weustink 29 Dec '17

29 Dec '17

Hi, Today I was testing the last dovecot release 2.3 from the dovecot repo on ubuntu 16.04. (I upgraded from 2.2.23) I cannot recall if I noticed it before, but doveconf -n not showing all changes. To be able to track my changes, I don't touch the config files provided in conf.d/ anymore, but I write them in local.conf (I did in the past so doveconf -n still shows something) I was testing the new submission service so I added to local.conf: protocols = imap pop3 lmtp sieve submission service submission-login { inet_listener submission { # test port = 588 } } submission_relay_host = 127.0.0.1 after restarting dovecot, submission works, mails get relayed. However doveconf -n shows: protocols = imap pop3 lmtp sieve This is very confusing. Marc

2 2

rename dirs at file system to strip .INBOX prefix?
by Voytek Eymont 29 Dec '17

29 Dec '17

looking at my personal email in /var/vmail/vmail1/dom.tld/voytek(a)dom.tld/Maildir I have some older dirs prefixed with .INBOX as so: .INBOX.Sent.2010.11 .INBOX.Sent.2010.12 around 30 or so, every other dir, .Sent or otherwise, doesn't have INBOX prefix can I just rename them from terminal to strip .INBOX from dir name..? and, if I do, what else I need to do or is that a bad idea, if so, how to get rid of old '.INBOX' prefixes? thanks, -- Voytek

1 0

Random delivery
by Jorge Bastos 29 Dec '17

29 Dec '17

Howdy, Id like to achieve something that i dont know if its possible. I have account info(a)domain.tld and when an email is received, I want to forward it to several accounts, always in this order: ð Email1(a)domain.tlf ð Email2(a)domain.tld ð Email3(a)domain.tld And when it reached email3(a)domain.tld it starts again with email1(a)domain.tld Would something like this be possible?

1 0

Ubuntu Auth Issues with new repository code..
by Howard Leadmon 28 Dec '17

28 Dec '17

Saw the new repository notification, and figured what the heck I would try letting it upgrade me from the current v2.2.22 release that apparently is in the Ubuntu 16.04 packages, to the new repository release of v2.3.0. I followed the info on repo.dovecot.org, and first it started bitching about lmtp (dovecot: master: Fatal: service(lmtp) access(/usr/lib/dovecot/lmtp) failed: No such file or directory), so I went back and installed the dovecot-lmtpd package and that seemed to fix that issue. Just FYI, I had dovecot-core, dovecot-imapd, and dovecot-pop3d installed on the system. OK, so now it started up, said it was 2.3.0 and I thought all was good, but now all authentication is failing. I turned on some of the logging debugging, and am seeing the below: dovecot: auth-worker(19578): Debug: pam(toss1,127.0.0.1,<IR3NJlZhFtZ/AAAB>): lookup service=dovecot dovecot: auth-worker(19578): Debug: pam(toss1,127.0.0.1,<IR3NJlZhFtZ/AAAB>): #1/1 style=1 msg=Password: dovecot: auth-worker(19578): pam(toss1,127.0.0.1,<IR3NJlZhFtZ/AAAB>): pam_authenticate() failed: System error dovecot: auth: Debug: client passdb out: FAIL#0111#011user=toss1 dovecot: imap-login: Aborted login (auth failed, 1 attempts in 3 secs): user=<toss1>, method=PLAIN, rip=127.0.0.1, lip=127.0.1.1, session=<IR3NJlZhFtZ/AAAB> I took and compared my auth files like 10-auth.conf, and auth-system.conf.ext, and they are identical between the two versions, even though they were overwritten as part of the upgrade. If I just uninstall the 2.3.0 release, and install 2.2.22 back on the server, it all just starts working again. So for now I am back on 2.2, but was willing to give 2.3 a run if I can get it going. Any ideas as to what to look at to get this working, would be great. As stated above, this is Ubuntu Server 16.04.03, and I am also running Postfix and amavis-new, but don't think they should really impact me using dovecot for email over POP3 or IMAP.. --- Howard Leadmon PBW Communications, LLC http://www.pbwcomm.com

5 6

2.3.0 upgrade from 2.2.x
by Fabian A. Santiago 28 Dec '17

28 Dec '17

Question; So after updating to 2.3.0 and following the recommended warnings / changes from running doveconf -n and then doing that same command > "a new conf file", and then renaming the conf files and restarting dovecot, I should be good to go with my old config updated to the new config spec? Just confirming. Thanks. What I mean is doing the -n to a new file hasn't changed or removed anything from my old config? Unless it was a changed or obsoleted option and in that case it would have warned me anyway, correct? -- Thanks, Fabian S. OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC

2 2

Question about imap (expunge response)
by kjonca＠o2.pl 28 Dec '17

28 Dec '17

(This is not neccesarily about dovecot, but rather IMAP protocol) At https://drive.google.com/open?id=1j3oa5jYeSdiPbgaihq02K-u_vHbZLJZQ is fetchmail log from my sessinon with polish email provider "Wirtualna Polska" As you can se fetchmail logged "* 1 EXPUNGE" as a response to "STORE" command. According to https://tools.ietf.org/html/rfc3501#section-7.4.1 EXPUNGE must not be sent as response to STORE command. Am I right that their imap server is erroneous or am I missing something? KJ -- http://stopstopnop.pl/stop_stopnop.pl_o_nas.html Lonely men seek companionship. Lonely women sit at home and wait. They never meet.

2 2

Re: Renewing certificates
by Joseph Tam 28 Dec '17

28 Dec '17

Kenneth Porter <shiva(a)sewingwitch.com> writes: > Thanks. Some digging indicates that this is equivalent to doveadm reload. > Both paths ultimately send a SIGHUP to the server which initiates a full > reload of the configuration. > > I'll be combining this with a restart of sendmail. Alas, I don't see a way > to get it to reload its configuration. Should be the same way: send a SIGHUP signal to the parent process. http://etutorials.org/Server+Administration/Sendmail/Part+II+Administration… I'm not sure whether this will cause the sendmail worker processes to dump their cients, but if it did, SMTP is fault tolerant enough that delivery should be retried later. Joseph Tam <jtam.home(a)gmail.com>

1 0

Renewing certificates
by Kenneth Porter 27 Dec '17

27 Dec '17

I'm setting up certbot/letsencrypt to provide a certificate for dovecot and sendmail. Is it necessary to restart dovecot to load the new certificate, as shown in most examples I find in blogs? That seems rude to established connections. When does dovecot read the cert and key files? Once at startup or each time a connection requests SSL? Is there a preferred locking protocol when changing the two files to keep dovecot from reading one while the other is being replaced and getting a mismatched pair?

3 3