September 2022 - dovecot

Debug logging: dovecot-lda command line?
by EML 20 Sep '22

20 Sep '22

Is there some way to configure logging so that I can see the command line that's passed to dovecot-lda? I'm on 2.3.16. Thanks.

1 1

Replicator Failure
by David Morsberger 20 Sep '22

20 Sep '22

Hello, I recently noticed the following errors in my log file and replicator status shows all accounts failed. I am seeing the same error on both hosts. "dovecot: doveadm(name(a)domain.com): Fatal: connect(192.168.1.250:12345) failed: Interrupted system call” # doveadm replicator status Queued 'sync' requests 0 Queued 'high' requests 0 Queued 'low' requests 0 Queued 'failed' requests 0 Queued 'full resync' requests 0 Waiting 'failed' requests 8 Total number of known users 8 Replication used to work and I do not know when it started failing. I restarted dovecot on both hosts to no avail. Any idea on how to get more information and resolve this issue? I cannot find anything else in the logs David

1 2

doveadm-search finds emails, but IMAP search fails to find any
by Philip Warner 20 Sep '22

20 Sep '22

Using dovecot 2.3.7.2 with solr 8.11.2 when I do: doveadm search -u user mailbox INBOX subject "something" I get multiple mail ID's. When I start a manual IMAP session and login as that user, select INBOX, and try the command: . search subject "something" It returns zero mail ID's; this is consistent across all searches using IMAP - no results returned, no matter what I search for in IMAP. The dovecot -n command returns: # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-125-generic x86_64 Ubuntu 20.04.5 LTS # Hostname: WITHELD mail_location = maildir:~/Mail mail_plugins = " fts fts_solr virtual" 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 { location = virtual:~/Mail/virtual prefix = virtual. separator = . } 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 } mailbox virtual.All { comment = All my messages special_use = \All } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { driver = pam } plugin { fts = solr fts_autoindex = yes fts_enforced = yes fts_solr = url=http://localhost:8983/solr/dovecot/ sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3 sieve" service imap { vsz_limit = 4 G } service index-worker { vsz_limit = 2 G } service indexer-worker { vsz_limit = 2 G } service lmtp { inet_listener lmtp { address = 127.0.0.1 port = 24 } } ssl_cert = </etc/letsencrypt/live/WITHELD/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { driver = passwd } protocol lmtp { mail_plugins = " fts fts_solr virtual sieve" postmaster_address = WITHELD } protocol lda { mail_plugins = " fts fts_solr virtual sieve" } protocol imap { mail_max_userip_connections = 40 } -

2 3

Panic: file mail-index-transaction-finish.c: line 185
by tobisworld＠gmail.com 20 Sep '22

20 Sep '22

Hi list I have weird issue with my Dovecot 2.3.17.1 (476cd46418) When deleting a certain amount of messages from my INBOX via my MUA (Evolution) all over sudden dovecot starts to panic Panic: file mail-index-transaction-finish.c: line 185 (mail_index_transaction_get_uid): assertion failed: (seq <= t->view- >map->hdr.messages_count) imap(REDACTED)<24075><P0/vLkXUNt4KQmMB>: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7f09274d4142] -> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f09274d424e] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf72fe) [0x7f09274e22fe] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf73a1) [0x7f09274e23a1] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0927430e38] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf438d) [0x7f092789d38d] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf43da) [0x7f092789d3da] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_finish+0x177) [0x7f092789da87] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf9ad6) [0x7f09278a2ad6] - > /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit_full+0x9d) [0x7f09278a2fad] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_index_transaction_commit+0x1c) [0x7f09278a306c] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_cache_set_seq_corrupted_reason+0x61) [0x7f092788c921] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_set_mail_cache_corrupted+0xed) [0x7f09277fbbbd] -> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a3e9) [0x7f09278233e9] - > /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a6b0) [0x7f09278236b0] -> /usr/lib64/dovecot/libdovecot- storage.so.0(mail_get_physical_size+0x38) [0x7f09277e8ba8] -> /usr/libexec/dovecot//lib20_mail_log_plugin.so(+0x2465) [0x7f09263dd465] -> /usr/libexec/dovecot//lib15_notify_plugin.so(notify_contexts_mail_copy+ 0x5c) [0x7f09265e13ec] -> /usr/libexec/dovecot//lib15_notify_plugin.so(+0x25d4) [0x7f09265e25d4] -> /usr/libexec/dovecot//lib10_quota_plugin.so(+0x102ae) [0x7f09269f92ae] -> /usr/libexec/dovecot//lib01_acl_plugin.so(+0xef3e) [0x7f0926c10f3e] -> /usr/lib64/dovecot/libdovecot- storage.so.0(+0x50c4c) [0x7f09277f9c4c] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x58) [0x7f09277f9ec8] -> dovecot/imap(+0x1175b) [0x55a2c0ea575b] -> dovecot/imap(command_exec+0x64) [0x55a2c0eb3f04] -> dovecot/imap(+0x1dde2) [0x55a2c0eb1de2] -> dovecot/imap(+0x1de71) [0x55a2c0eb1e71] -> dovecot/imap(+0x1e039) [0x55a2c0eb2039] -> dovecot/imap(client_handle_input+0x205) [0x55a2c0eb22f5] -> dovecot/imap(client_input+0x79) [0x55a2c0eb28d9] imap(REDACTED)<24075><P0/vLkXUNt4KQmMB>: Fatal: master: service(imap): child 24075 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) >From that point on ANY access to INBOX from my MUA causes the error. The only way that I found to get around is to unsubscribe the INBOX folder and subscribe again. Then the error is gone until I delete a bunch of messages again. The error only occurs if I delete the messages within short time or select multiple (about 20msg at once). If I delete them one-by-one always waiting for expunge message in dovecot logs to appear then I can delete as many as I want. I have not verified with other MUA but in Evolution I can reproduce the issue. Cheers and have a good one tobi

4 14

Thunderbird can't connect to Dovecot (bad certificate: SSL alert number 42)
by Meikel 19 Sep '22

19 Sep '22

Hi folks, on a Rocky Linux 8.6 based home server I run Dovecot with an account that I use as an archive. Archive means, that from different Thunderbird instances I connect to that Dovecot via IMAPS to move emails there, that I want to keep. Since some days from all Thunderbird instances I can no longer connect to that Dovecot account. In /var/log/maillog of the server I see Sep 14 06:39:54 server3 dovecot[2033173]: imap-login: Disconnected: Connection closed: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 (no auth attempts in 0 secs): user=<>, rip=192.168.177.105, lip=192.168.177.13, TLS handshaking: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42, session=<dL1luJvokK3AqLFp> I found that Openssl alert number 42 might be a problem with the SSL certificate (which certificate?) but also might be an expired SSL certificate (which certificate?). As on the Dovecot installation I work with a self signed certificat. I created a new self signed certificate yesterday with an expiry not before year 2032. That did not help, I see the same messages when I try to connect from Thunderbird. Just to see how Thunderbird is involved in the problem I installed Claws-Mail. From Claws-Mail I do NOT have those problems, I can access to Dovecot via IMAPS as expected. I do not understand why all my Thunderbird installations can no longer access Dovecot via IMAPS. This worked fine for about 18 months. I can't prove but I think on beginning of month it worked fine. Something happened meanwhile. If there is a problem with an SSL certificate (bad certificate: SSL alert number 42), which certificate makes the problem? The certificate used by Dovecot or some certificate used in Thunderbird? About installation: cat /etc/redhat-release Rocky Linux release 8.6 (Green Obsidian) dovecot --version 2.3.16 (7e2e900c1a) sudo dovecot -n # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # OS: Linux 4.18.0-372.19.1.el8_6.x86_64 x86_64 Rocky Linux release 8.6 (Green Obsidian) # Hostname: ....... auth_debug = yes auth_mechanisms = plain login auth_verbose = yes first_valid_uid = 1000 mail_debug = yes mail_gid = vmail mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = vmail mbox_write_locks = fcntl namespace { inbox = yes location = mailbox Archives { special_use = \Archive } prefix = INBOX/ separator = / type = private } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } protocols = imap service imap-login { inet_listener imap { port = 0 } } ssl = required ssl_cert = </etc/dovecot/......crt ssl_cipher_list = PROFILE=SYSTEM ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_proctitle = yes I used the following command to recreate the SSL certificate for Dovecot: sudo openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -keyout /etc/dovecot/......key -out /etc/dovecot/......crt And with the command openssl s_client -crlf -connect .....:993 I can successfully connect to Dovecot and "simulate" a minimal IMAP-Session: * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ AUTH=PLAIN AUTH=LOGIN] Dovecot ready a login meikel.archive@..... topsecret a OK [CAPABILITY IMAP4rev1 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 SNIPPET=FUZZY PREVIEW=FUZZY LITERAL+ NOTIFY SPECIAL-USE] Logged in a logout * BYE Logging out a OK Logout completed (0.001 + 0.000 secs). closed I have the problem with different Thunderbird installations on various operating systems (Windows 10, Fedora Linux 36 XFCE). Regards, Meikel

10 13

Bug report: TLS SNI for LDAP userdb/passdb
by Tobias Wolter 18 Sep '22

18 Sep '22

Cheers, Dovecot 2.3.4.1 (Debian stable) here, and the changelog does not offer any hope of salvation, so a bug report it is. The LDAP connections for userdb/passdb do not support SNI via TLS. Simple construct to reproduce this: 0.) Have a.pem with SAN `foo.example.com`, b.pem with `bar.example.com` 1.) Configure haproxy frontend with `bind *:636 ssl crt /foo/a.pem ssl crt /foo/b.pem` 2.) Try to use ldaps://bar.example.com/ in passdb, receive "auth: Error: LDAP: Can't connect to server: ldaps://bar.example.com" Expectation, of course, would be for this to work; most libraries should support it, it's probably just a matter of convincing the appropriate binding. Kind regards, -towo

4 4

Client for a Windows User ?
by White, Daniel E. (GSFC-770.0)[AEGIS] 13 Sep '22

13 Sep '22

Specifically, Windows 2016 server I suggested Thunderbird. Is there anything else ? Is this current ? https://wiki.dovecot.org/Clients

6 6

Overquota flag and auth caching
by Christian Rößner 13 Sep '22

13 Sep '22

Hello, I like the over quota flag mechanism in Dovecot. I found out that I get in trouble if a user gets over quota and I have turned on auth caching, because the cache does not automatically invalidate a user while toggling the flag. The cache still serves the old state. The result is that mails are still accepted, even a user went over quota resulting in bounces. Workaround is to flush a user from inside the toggle script, which solves the bounce problem, but it prevents the user from getting under quota before the user is flushed from the cache again. What is the correct way to use the over quota flag and which solutions can be taken to invalidate the user? Is it possible to do this in a Lua user backend? Any other method? Thanks in advance Christian Rößner -- Rößner-Network-Solutions Zertifizierter ITSiBe / CISO Karl-Bröger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

2 1

Re: Sieve Symlink Creation
by dovecot＠ptld.com 13 Sep '22

13 Sep '22

> On 09-12-2022 12:16 pm, hi(a)zakaria.website wrote: > > It seems that dovecot doesn't understand the relative format and requires absolute format, per the documentation example. Perhaps find the code which parses the absolute path, and compile your own dovecot build, which can understand the path format you want? I did not find that. I want to learn more, can you link me the dovecot documentation you found explaining how absolute paths are required for sieve? > On 2022-08-25 13:32, dovecot(a)ptld.com wrote: >> The first time when the sieve files and folders get created, the active symlink is created as a full absolute path >> >> .active_sieve -> /mnt/email/domain/user/_sieve/filters.sieve >> >> After that, if you disable and enable the rule set the symlink gets recreated as relative >> >> .active_sieve -> filters.sieve >> >> How can i have the symlink always created as a relative path even on first time creation? >> Having a full absolute path over a mounted NSF is fragile. >> >> Dovecot 2.3.16 >> Pigeonhole 2.3.16 >> >> mail_home = /mnt/email/%d/%n/_dovecot >> mail_location = maildir:/mnt/email/%d/%n/_folders:INDEX=/mnt/email/%d/%n/_dovecot:CONTROL=/mnt/email/%d/%n/_dovecot >> plugin { >> sieve = file:~/../_sieve;active=~/../_sieve/.active_sieve >> sieve_max_script_size = 1M >> sieve_max_actions = 32 >> sieve_max_redirects = 4 >> sieve_quota_max_scripts = 20 >> sieve_quota_max_storage = 5M >> sieve_vacation_min_period = 1d >> sieve_vacation_use_original_recipient = no >> sieve_vacation_dont_check_recipient = no >> sieve_vacation_send_from_recipient = no >> sieve_redirect_envelope_from = sender >> sieve_user_email = %u >> }

2 1

real duplicates of some e-mails / dovecot-2.3.19
by Götz Reinicke 13 Sep '22

13 Sep '22

Hi, we have the issue, that some(!) e-mails we receive are duplicated when processed by dovecot and stored to the users inbox. The mails are binary identical, same message ID, same size etc. diff sees no difference …. For now we only see that it happens do small mails max. +- 5k in size. And in dose not happen for all mails, but some are spam, some are internal mails some are newsletter which are expected…. and it happens for different users. Dose anyone have/had a similar issue? Any suggestion or idea would be helpful. Thanks . Götz

2 1