- dovecot - dovecot.org

Shared mailboxes, users with dots and a bug in subscriptions
by Tobias Stein 17 May '22

17 May '22

Hi, i'm running Dovecot 2.3.14.alpha0 with shared namespaces and stumbled across some errors messages logged, when the list of subscribed mailboxes is queried by a client. For every distinct account of in the list of subscriptions two corresponding lines are logged: Jan 28 11:42:34 mx1 dovecot: auth: missing passwd file: /etc/dovecot/private/example/users Jan 28 11:42:34 mx1 dovecot: auth: missing passwd file: /etc/dovecot/private/example/users Jan 28 11:42:34 mx1 dovecot: auth: missing passwd file: /etc/dovecot/private/example/users Jan 28 11:42:36 mx1 dovecot: imap(example_user(a)example.com)<3638><xl6li/O5VsVfWxyn>: Error: mkdir(/var/run/dovecot/user-not-found/noc@example) failed: Permission denied (euid=109(vmail) egid=118(vmail) missing +w perm: /var/run/dovecot, dir owned by 0:0 mode=0755) Jan 28 11:42:36 mx1 dovecot: imap(example_user(a)example.com)<3638><xl6li/O5VsVfWxyn>: Error: mkdir(/var/run/dovecot/user-not-found/info@example) failed: Permission denied (euid=109(vmail) egid=118(vmail) missing +w perm: /var/run/dovecot, dir owned by 0:0 mode=0755) Jan 28 11:42:36 mx1 dovecot: imap(example_user(a)example.com)<3638><xl6li/O5VsVfWxyn>: Error: mkdir(/var/run/dovecot/user-not-found/root@example) failed: Permission denied (euid=109(vmail) egid=118(vmail) missing +w perm: /var/run/dovecot, dir owned by 0:0 mode=0755) Similar messages are logged, when invalid entries are listed in '/var/lib/dovecot/db/shared-mailboxes', which i already pruned and haven't received them anymore since. I think these errors are caused by an unintended behaviour when writing "~/Maildir/subscriptions", which looks (shortened) like this. V 2 INBOX/INBOX shared/noc@example com/INBOX shared/info@example com/INBOX shared/root@example com/test shared/root@example com/test test_sub The subscription-file.c explodes the name on every hierarchy separator ('.','\0') and inserts a TAB character. Unfortunately it also explodes on the DNS label delimiter „.‟. This should probably be fixed by passing a structure containing the required information to the formatter to distinguish mailboxes from domain-names. Subscription in combination with multiple domains and shared mailboxes seems broken to me. Actually i can't even explain to me, why it is working in face of the errors. :-) Unfortunately in Maildir++ the separator dot is hard-coded. There is a very old thread on this mailing list, that suggests using „auth_username_translation‟ to replace dots with a different character, but this idea is getting worse the longer i think about it. I absolutely dislike the idea to set LAYOUT=fs, namespace/separator = § to change the separators to split on, because this would mean to restructure the physical layout of all mailboxes (hierarchically) and mess around with lots of files. I attached a dovecot-sysreport to reproduce the behaviour. /etc/dovecot/private/example.com/users looks like this: ### user:password:uid:gid:(gecos):home:(shell):extra_fields noc:{SSHA512}_hash_:::::: info:{SSHA512}_hash_:::::: root:{SSHA512}_hash_:::::: Please correct me if i'm wrong or point me to a workaround, but i think the layout code needs some love. :-) Best regards Tobias

2 4

Re: Permissions and ownership on /dev/shm/dovecot
by doug 16 May '22

16 May '22

1 0

Fatal Error after upgrade to 2:2.3.19-2+debian11
by Sebastian Kroczek 16 May '22

16 May '22

Hello all, I updated the server tonight and with it Dovecot from 2.2.27 to 2:2.3.19-2+debian11. However, there seems to be a problem with the ACLs, because since then fatal errors are logged (see core dump). I suspect that some outdated configuration is causing this behavior, but so far I couldn't figure out which one it could be. I also have no clue right now how to debug this further. Thank you very much for your help. If more information are needed, I will of course be happy to provide them. VG Sebastian ======== Error logs ========= May 16 13:33:43 Fatal: imap(user1(a)domain.com)<0r5YZR/fM4AfrHBI>: master: service(imap): child 238359 killed with signal 11 (core dumped) May 16 13:33:46 Fatal: imap(user2(a)domain.com)<Ul+kZR/fA4AfrHBI>: master: service(imap): child 238386 killed with signal 11 (core dumped) May 16 13:33:46 Fatal: imap(user3(a)domain.com)<VGOkZR/fG4AfrHBI>: master: service(imap): child 238387 killed with signal 11 (core dumped) May 16 13:34:54 Fatal: imap(user4(a)domain.com)<1WS6aR/fHoAfrHBI>: master: service(imap): child 238509 killed with signal 11 (core dumped) May 16 13:34:54 Fatal: imap(user2(a)domain.com)<mQu6aR/fBIAfrHBI>: master: service(imap): child 238508 killed with signal 11 (core dumped) May 16 13:35:27 Fatal: imap(user3(a)domain.com)<pWGYax/fE4AfrHBI>: master: service(imap): child 238589 killed with signal 11 (core dumped) May 16 13:35:27 Fatal: imap(user1(a)domain.com)<s/mgax/fG4AfrHBI>: master: service(imap): child 238590 killed with signal 11 (core dumped) ======== END Error logs ========= ======== dovecot.conf ========== # 2.3.19 (b3ad6004dc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 5.10.0-14-amd64 x86_64 Debian 11.3 # Hostname: wv-imap1.wavecloud.de auth_mechanisms = plain login default_vsz_limit = 4 G dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf } first_valid_gid = 5000 first_valid_uid = 5000 imap_capability = +XDOVECOT last_valid_gid = 5000 last_valid_uid = 5000 listen = 10.10.115.XX login_trusted_networks = 10.10.115.XX 10.10.115.XX mail_location = maildir:~/ mail_log_prefix = "%s(%u)<%{session}>: " mail_plugins = acl notify quota fts fts_solr virtual maildir_stat_dirs = 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 ihave namespace { inbox = yes location = mailbox Archive { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Items" { auto = no special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace Virtual { hidden = yes list = no location = virtual:/etc/dovecot/virtual:INDEX=/srv/vmail/_virtual/%u prefix = Virtual/ separator = / subscriptions = no } namespace shared { list = yes location = maildir:%%h:INDEX=~/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-sql-password.conf driver = sql } passdb { args = /etc/dovecot/admin-sql.conf driver = sql master = yes pass = yes } plugin { acl = vfile acl_shared_dict = proxy::acl fts = solr fts_autoindex = yes fts_solr = url=http://wv-solr1.wavecloud.de:8983/solr/dovecot/ quota = maildir:User quota quota_rule = *:storage=20G quota_rule2 = Trash:storage=+100M quota_rule3 = SPAM:ignore quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u sieve = ~/.dovecot.sieve sieve_before = /var/vmail/globalsieverc sieve_max_script_size = 1M sieve_quota_max_scripts = 42 sieve_quota_max_storage = 10 } protocols = imap pop3 sieve lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = vmail mode = 0666 user = vmail } unix_listener auth-master { mode = 0666 } } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap-login { process_min_avail = 1 service_count = 0 vsz_limit = 500 M } service lmtp { inet_listener lmtp { address = 0.0.0.0 port = 24 } } service managesieve-login { executable = /usr/lib/dovecot/managesieve-login inet_listener sieve { address = 10.10.115.10 port = 4190 } process_min_avail = 1 service_count = 1 } service managesieve { executable = /usr/local/sbin/dovecot-managesieve.sh } service pop3-login { process_min_avail = 1 service_count = 1 } service quota-warning { executable = script /usr/local/sbin/quota-warning.sh user = vmail } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } shutdown_clients = no ssl_cert = </etc/ssl/cert.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 2048 mail_plugins = acl notify quota fts fts_solr virtual imap_quota imap_acl } protocol pop3 { mail_plugins = acl notify quota fts fts_solr virtual pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { hostname = wv-imap1.wavecloud.de mail_fsync = optimized mail_plugins = acl notify quota fts fts_solr virtual sieve postmaster_address = postmaster(a)example.com quota_full_tempfail = yes sendmail_path = /usr/lib/sendmail } protocol sieve { managesieve_implementation_string = Dovecot Pigeonhole } protocol lmtp { mail_fsync = optimized mail_plugins = acl notify quota fts fts_solr virtual sieve } ======== END dovecot.conf ========== ======== Core-Dump ================= PID: 240475 (imap) UID: 5000 (vmail) GID: 5000 (vmail) Signal: 11 (SEGV) Timestamp: Mon 2022-05-16 13:49:56 CEST (1min 17s ago) Command Line: dovecot/imap [user1(a)domain.com XX.XX.XX.XX MYRIGHTS] Executable: /usr/lib/dovecot/imap Control Group: /system.slice/dovecot.service Unit: dovecot.service Slice: system.slice Boot ID: acb78ce2252049778ff969755d277453 Machine ID: 1367ff1e75be457cacbf5e204a28711b Hostname: wv-imap1 Storage: /var/lib/systemd/coredump/core.imap.5000.acb78ce2252049778ff969755d277453.240475.1652701796000000.zst Message: Process 240475 (imap) of user 5000 dumped core. Stack trace of thread 240475: #0 0x00007f5db938c17c acl_mailbox_get_aclobj (lib01_acl_plugin.so + 0xf17c) #1 0x00007f5db93776ed n/a (lib02_imap_acl_plugin.so + 0x36ed) #2 0x000055f5568444d4 command_exec (imap + 0x224d4) #3 0x000055f55684244f n/a (imap + 0x2044f) #4 0x000055f5568424fa n/a (imap + 0x204fa) #5 0x000055f5568429d5 client_handle_input (imap + 0x209d5) #6 0x000055f556842f40 client_input (imap + 0x20f40) #7 0x00007f5db9682529 io_loop_call_io (libdovecot.so.0 + 0x118529) #8 0x00007f5db9683c12 io_loop_handler_run_internal (libdovecot.so.0 + 0x119c12) #9 0x00007f5db96825d0 io_loop_handler_run (libdovecot.so.0 + 0x1185d0) #10 0x00007f5db9682790 io_loop_run (libdovecot.so.0 + 0x118790) #11 0x00007f5db95f5353 master_service_run (libdovecot.so.0 + 0x8b353) #12 0x000055f556833f0a main (imap + 0x11f0a) #13 0x00007f5db93c5d0a __libc_start_main (libc.so.6 + 0x26d0a) #14 0x000055f556833fca _start (imap + 0x11fca) =========== END Core-Dump ============= -- Wavecon GmbH Anschrift: Gustavstraße 18, 90762 Fürth Website: www.wavecon.de Support: support(a)wavecon.de Telefon: +49 (0)911-1206581 (werktags von 9 - 17 Uhr) Hotline 24/7: 0800-WAVECON Fax: +49 (0)911-2129233 Registernummer: HRB Fürth 18164 GF: Cemil Degirmenci UstID: DE251398082 Pflichtinformationen nach Art. 13 DSGVO siehe wavecon.de/de/datenschutz

3 5

TLS renegotiation issue (CVE-2011-1473) in Dovecot
by Greg Earle 16 May '22

16 May '22

Hello, At work I'm running a Dovecot 2.3.15 server on a RHEL 7.9 system with OpenSSL 1.0.2k. Our IT Security people are threatening to shut it down because of this: > We were notified of a possible TLS renegotiation vulnerability on > [FQHN]. > > [Parent organization] ticket NNNNNNN is open to track efforts. > > We conducted a manual test on the site for TLS Renegotiation on IMAP > port 993. > > We found that this was set to enabled. > > In order to remediate we will need to either: > > 1. Disable Renegotiation (preferred) > 2. Set a max aggregated renegotiation > > Please remediate as soon as possible. > > References: > > https://support.f5.com/csp/article/K15278 > > https://nvd.nist.gov/vuln/detail/cve-2011-1473 > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1473 I did some Googling and among the results, I found a few old posts from this mailing list among them, which to summarize basically seemed to say "Yeah, we could write some code ... " but that was about it. The IT Security rep sent me a reference to an ancient Red Hat article https://access.redhat.com/articles/23543 which is hysterical - ancient history, references NSS and Tomcat, suggests changes to an add-on product (Red Hat Certificate Server) that is EOL, etc. Is there any way to mitigate this issue? (The only thing I can think of is to upgrade the Dovecot server to RHEL 8 and restrict connections to only TLSv1.3, but that ain't gonna happen overnight.) Thanks, - Greg

3 2

Duplicate messages if message is moved when using dsync
by Thom Pol 16 May '22

16 May '22

Hi, Hope you are well. We have a cluster of 2 Dovecot servers, both on v2.3.13 (89f716dc2), using dsync to sync the messages between them. Previously, we used TCPS to sync the messages, but after some testing, we concluded that syncing over SSH resulted in a lot less failed syncs, so we started using SSH. The change has been a success, but I now notice a issue when a email client immediately moves a messages to a separate folder while Dovecot is syncing, where the message is seen twice in the folder (with the exact same headers/content). For example, I have set a filter in my email client, Thunderbird, to immediately move all emails coming from this list to a separate folder. When opening that folder, I do not see one, but two unread messages, both identical to each other. When checking the directories on the server, I see this: mx1: /var/vmail/example.com/joe/Maildir/.Subdir.Subdir/cur/1652615808.M190190P990486.mx2,S=19089,W=19384:2,S /var/vmail/example.com/joe/Maildir/.Subdir.Subdir/cur/1652615811.M180050P1376677.mx1,S=19089,W=19384:2,S mx2: /var/vmail/example.com/joe/Maildir/.Subdir.Subdir/cur/1652615811.M981426P990530.mx2,S=19089,W=19384:2,S /var/vmail/example.com/joe/Maildir/.Subdir.Subdir/cur/1652615808.M190190P990486.mx2,S=19089,W=19384:2,S Note the difference: on mx1, one indicates mx1, and one mx2, while on the other server, both indicate mx2/ Any idea (other then telling end-users not to use such filters) how we could prevent these duplicate messages? This is our config: # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-13-cloud-amd64 x86_64 Debian 11.3 # Hostname: mx1.example.com auth_mechanisms = plain login disable_plaintext_auth = no dsync_remote_cmd = ssh -p 222 -l%{login} %{host} doveadm dsync-server -u%u imap_capability = +SPECIAL-USE XLIST listen = *,[::] lmtp_rcpt_check_quota = yes log_timestamp = "%Y-%m-%d %H:%M:%S " mail_max_userip_connections = 100 mail_plugins = quota mail_privileged_group = vmail 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 = separator = . } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { mail_replica = remote:root@mx2.example.com quota = dict:user::file:/var/vmail/%d/%n/.quotausage quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO sieve = /var/vmail/%d/%n/.sieve sieve_after = /var/vmail/%d/%n/.ispconfig.sieve sieve_before = /var/vmail/%d/%n/.ispconfig-before.sieve sieve_max_actions = 100 sieve_max_redirects = 25 sieve_max_script_size = 2M } protocols = imap pop3 lmtp replication_max_conns = 50 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0600 user = vmail } user = root } service imap-login { client_limit = 1000 process_limit = 512 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service quota-status { client_limit = 1 executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 user = vmail } } 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/postfix/smtpd.cert ssl_cipher_list = kEECDH:+kEECDH+SHA:kEDH:+kEDH+SHA:+kEDH+CAMELLIA:kECDH:+kECDH+SHA:kRSA:+kRSA+SHA:+kRSA+CAMELLIA:!aNULL:!eNULL:!SSLv2:!RC4:!MD5:!DES:!EXP:!SEED:!IDEA:!3DES ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { auth_verbose = yes mail_plugins = quota quota imap_quota quota notify replication } protocol pop3 { auth_verbose = yes mail_plugins = quota quota quota notify replication pop3_uidl_format = %08Xu%08Xv } protocol lda { mail_plugins = quota sieve quota sieve quota notify replication postmaster_address = postmaster(a)mx1.example.com } protocol lmtp { mail_plugins = quota quota sieve sieve quota notify replication postmaster_address = postmaster(a)mx1.example.com } Thanks in advance for your thoughts. Kind regards, Thom Pol

2 1

Use different log files
by Cristiano Deana 16 May '22

16 May '22

Hi, I have a mailserver with dovecot logging to syslog (by default, to /var/log/maillog) and my MTA (postfix) is doing the same. I use dovecot's services imap/pop3, auth and lmtp and now logs files are hard to read because I havve all together MTA and these services. Is it possibile to have different log with different services? Example: auth logging: /var/log/mail.auth delivery: /var/log/mail.delivery and so on Thank you -- ############################### # Cristiano Deana # # # # Senior Network Engineer # # Digital Response Team # # CittaStudi S.p.a. # # off. +39 015 855 1172 # # cell +39 328 310 6392 # ###############################

3 2

Re: TLS renegotiation issue (CVE-2011-1473) in Dovecot
by Greg Earle 16 May '22

16 May '22

On 13 May 2022, at 19:38, Elisamuel Resto <sam(a)samresto.dev> wrote: > I believe this to be a configuration error, not a dovecot problem. > The > output of dovecot -n (as an attachment; look it over for any data you > do > not want publicized) would help to suggest changes to bring you back > into compliance. Elisamuel, I'm not really sure why you think it's a configuration error, but I'll attach the "dovecot -n" output. Thanks, - Greg

3 2

Dovecot v2.3.19 released
by Aki Tuomi 16 May '22

16 May '22

Hi all! We are pleased to release v2.3.19 of Dovecot. The docker images have been upgraded to use bullseye as base image. https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.19.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy -- + Added mail_user_session_finished event, which is emitted when the mail user session is finished (e.g. imap, pop3, lmtp). It also includes fields with some process statistics information. See https://doc.dovecot.org/admin_manual/list_of_events/ for more information. + Added process_shutdown_filter setting. When an event matches the filter, the process will be shutdown after the current connection(s) have finished. This is intended to reduce memory usage of long-running imap processes that keep a lot of memory allocated instead of freeing it to the OS. + auth: Add cache hit indicator to auth passdb/userdb finished events. See https://doc.dovecot.org/admin_manual/list_of_events/ for more information. + doveadm deduplicate: Performance is improved significantly. + imapc: COPY commands were sent one mail at a time to the remote IMAP server. Now the copying is buffered, so multiple mails can be copied with a single COPY command. + lib-lua: Add a Lua interface to Dovecot's HTTP client library. See https://doc.dovecot.org/admin_manual/lua/ for more information. - auth: Cache lookup would use incorrect cache key after username change. - auth: Improve handling unexpected LDAP connection errors/hangs. Try to fix up these cases by reconnecting to the LDAP server and aborting LDAP requests earlier. - auth: Process crashed if userdb iteration was attempted while auth-workers were already full handling auth requests. - auth: db-oauth2: Using %{oauth2:name} variables caused unnecessary introspection requests. - dict: Timeouts may have been leaked at deinit. - director: Ring may have become unstable if a backend's tag was changed. It could also have caused director process to crash. - doveadm kick: Numeric parameter was treated as IP address. - doveadm: Proxying can panic when flushing print output. Fixes Panic: file ioloop.c: line 865 (io_loop_destroy): assertion failed: (ioloop == current_ioloop). - doveadm sync: BROKENCHAR was wrongly changed to '_' character when migrating mailboxes. This was set by default to %, so any mailbox names containing % characters were modified to "_25". - imapc: Copying or moving mails with doveadm to an imapc mailbox could have produced "Error: Syncing mailbox '[...]' failed" Errors. The operation itself succeeded but attempting to sync the destination mailbox failed. - imapc: Prevent index log synchronization errors when two or more imapc sessions are adding messages to the same mailbox index files, i.e. INDEX=MEMORY is not used. - indexer: Process was slowly leaking memory for each indexing request. - lib-fts: fts header filters caused binary content to be sent to the indexer with non-default configuration. - doveadm-server: Process could hang in some situations when printing output to TCP client, e.g. when printing doveadm sync state. - lib-index: dovecot.index.log files were often read and parsed entirely, rather than only the parts that were actually necessary. This mainly increased CPU usage. - lmtp-proxy: Session ID forwarding would cause same session IDs being used when delivering same mail to multiple backends. - log: Log prefix update may have been lost if log process was busy. This could have caused log prefixes to be empty or in some cases reused between sessions, i.e. log lines could have been logged for the wrong user/session. - mail_crypt: Plugin crashes if it's loaded only for some users. Fixes Panic: Module context mail_crypt_user_module missing. - mail_crypt: When LMTP was delivering mails to both recipients with mail encryption enabled and not enabled, the non-encrypted recipients may have gotten mails encrypted anyway. This happened when the first recipient was encrypted (mail_crypt_save_version=2) and the 2nd recipient was not encrypted (mail_crypt_save_version=0). - pop3: Session would crash if empty line was sent. - stats: HTTP server leaked memory. - submission-login: Long credentials, such as OAUTH2 tokens, were refused during SASL interactive due to submission server applying line length limits. - submission-login: When proxying to remote host, authentication was not using interactive SASL when logging in using long credentials such as OAUTH2 tokens. This caused authentication to fail due to line length constraints in SMTP protocol. - submission: Terminating the client connection with QUIT command after mail transaction is started with MAIL command and before it is finished with DATA/BDAT can cause a segfault crash. - virtual: doveadm search queries with mailbox-guid as the only parameter crashes: Panic: file virtual-search.c: line 77 (virtual_search_get_records): assertion failed: (result != 0)

12 20

Recovering deleted mailbox
by Sean McBride 14 May '22

14 May '22

Hi all, I have a user (coworker) that accidentally deleted a mailbox and all its sub-mailboxes. I use Maildir format storage. I have backups. Is it enough to put the mailbox folder back where it was? I'm talking about the folder that contains 'cur', 'new', 'tmp', 'dovecot-uidlist', etc. Or would this desynchronize or otherwise confuse dovecot? Or is it preferable to use some doveadm command? Or...? Thanks, Sean

6 13

how is the "Total number of known users" reported by doveadm replicator calculted?
by Arnaud Abélard 13 May '22

13 May '22

Hello, I have a question regarding the "Total number of known users" displayed by doveadm replicator status. How is it calculated? Shouldn't it match the number of users reported by doveadm user '*' ? I have 3 servers being replicated, the "total number of known users" a lot higher than the number of users reports by doveadm user '*' why is that? Arnaud -- Arnaud Abélard Responsable Service Infrastructures DSIN Université de Nantes -

2 1