- dovecot - dovecot.org

Logging for doveadm index?
by Shawn Heisey 15 Sep '23

15 Sep '23

I have dovecot using Solr for FTS. Dovecot version is 2:2.3.20-3+ubuntu20.04 pulled from the official APT repo. This is my reindex script: https://paste.elyograg.org/view/74accd23 The reindex script kicks off the indexing process in the background. Dovecot logs to syslog, and those logs ultimately end up in mail.log. I have not seen any logging for the FTS reindexing. Specifically I would like to see how long the process took. Getting that info from the solr logs is a manual process and I can't think of a way to properly automate it. Is this something I can easily have dovecot log? Or is there a way to have 'doveadm index' run in the foreground instead of the background so the time can be calculated by my script? Thanks, Shawn

1 0

Pigeonhole v0.5.21 released
by Aki Tuomi 15 Sep '23

15 Sep '23

Hi all! We are pleased to release v0.5.21 of Pigeonhole. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.21.t… https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.21.t… Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot Regards, Aki Tuomi Open-Xchange oy --- - sieve: Using the deleteheader action on a message with a broken/invalid header can cause the Sieve interpreter to crash with an assert panic. This can happen e.g. when the message is missing the empty EOH line between the headers and the body of the message. Fixes: Panic: file edit-mail.c: line 820 (edit_mail_headers_parse): assertion failed: (body_offset > 0). - sieve: Pigeonhole added an extra Message-ID header during mail forwarding when the existing one was invalid. Now it adds the Message-ID only if it is entirely missing. Existing Message-ID(s) are left unchanged.

1 0

Dovecot v2.3.21 released
by Aki Tuomi 15 Sep '23

15 Sep '23

Hi all! We are pleased to release v2.3.21 of Dovecot. https://dovecot.org/releases/2.3/dovecot-2.3.21.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.21.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 --- * lib-oauth2: Allow JWT tokens to be validated with missing typ field. The typ field is left out by some key issuers to conserve space, notably kubernetes. Now missing typ is tolerated, but if present, it still must be "jwt". + auth: Auth passdb and userdb reply can contain "event_<name>=value" which will be added to login event and mail user event respectively. + lib-master: Set process title during various initialization stages to clearly describe what the process is waiting on. + lib-storage: The mail_temp_scan_interval is now fuzzed incrementing it by 0..30% based on username's hash to reduce the chance of load spikes . + lib-storage: The temp file scan has been moved from the open of the mailbox to the close, to reduce the latency perceived by users. + stats: If metric has fields specified, all these fields are exported as counters to prometheus exposition. See https://doc.dovecot.org/configuration_manual/stats/openmetrics/. - *-login: Processes might have crashed when a SSL connection disconnect s uncleanly. - acl: When plugin was loaded \HasChildren and \HasNoChildren flags were calculated incorrectly for mailboxes containing '*' and '%' in their names. - auth: Crash occured if a connection to PostgreSQL database server failed during startup. - auth: Logins with invalid passwords (e.g. unknown scheme) in passdb were failing with "password mismatch" instead of "internal error". - auth: XOAUTH2 and OAUTHBEARER mechanisms were not giving out protocol specific error message on all errors. This especially broke OIDC discovery. - dbox: When last_temp_file_scan header wasn't set (especially after dsync migration), the next mailbox open always triggers the temp file scan. This could have caused a load spike after migrations. Fixed by using the mailbox directory's atime when the header isn't set, which usually moves the scan time into the future. - dict-redis: A crash would occur on transaction rollback. - dsync: Infinite loop causing out of memory would occur when handling mailbox deletion from remote end and hierarchy separators would differ. - dsync: Incremental dsync failed for folder names ending with '%', unless BROKENCHAR was set. Also folder names with '%' elsewhere in them caused each incremental dsync to unnecessarily rename the folder to a temporary name and back. v2.3.19 regression. - imap-hibernate: If an IMAP client unhibernation timed out with "(version received)", the unhibernation could still have successfully finished later on and continued working normally. This was rather confusing, because imap-hibernate already logged that the client got disconnected. Avoid this by forcing the connection to shutdown on unhibernation timeout. - imapc: Crashed when a folder mapped through the virtual plugin disappears from the storage. - imapc: EXPUNGE, EXISTS or FETCH replies from a server for a previously selected mailbox could have been processed as if they belonged to the new mailbox currently being selected. This could have caused warnings. - lib-http: Dovecot HTTP server (doveadm, stats/openmetrics) may have disconnected HTTP clients before the response is fully sent. This happened only on busy servers where kernel's socket buffers were rather full. - lib-http: Fixed a potential crash on http-server if a client disconnected early. v2.3.18 regression. - lib-index: Index file corruption could have caused a crash. Fixes: Panic: file mail-transaction-log-view.c: line 165 (mail_transaction_log_view_set): assertion failed: (min_file_seq <= max_file_seq). - lib-index: Purging an existing >1GB cache file can crash. Now cache files still above 1GB after purging are removed. Fixes: Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000) - lib-lua: A HTTP client could not resolve DNS names in mail processes, because it expected "the dns-client" socket to exist in the current directory. - lib-oauth2: Dovecot would send client_id and client_secret as POST parameters to the introspection server. These need to be optionally in Basic auth instead. - lib-oauth2: JWT aud validation was not performed if aud was missing from a token, but was configured on Dovecot. - lib-oauth2: JWT key type check was too strict. - lib-oauth2: JWT token audience was not validated against client_id as required by the specification. - lib-ssl-iostream: Using the ssl_require_crl=yes setting may have caused CRL check failures for outgoing SSL/TLS connections, although it was supposed to affect checking CRLs only for client-side SSL certificates. v2.3.17 regression. - lib-sql: MySQL driver leaked memory when connection failed. - lib-storage: Various fixes when running into out of disk space. - master: Service idle_kill setting didn't work properly on busy servers. It was very unlikely that any process was idling long enough to become killed. Also the idle_kill handling code was using quite a lot of CPU on the master process when there were a lot of processes (e.g. imap). The new behavior is to track the lowest number of idling processes every idle_kill time interval and then kill that many idling processes. - mdbox: Temp file scan was done for always empty directories. - mdbox: The fdatasync() call was done in wrong parent directory when writing mails. Also on a failure it crashed instead of logging an error. - notify_status: The plugin crashes if any user initialization fails. - pop3: Sending command with the ':' character caused an assert-crash. v2.3.18 regression. Fixes: Panic: event_reason_code_prefix(): name has ':' - stats: Fix panic when a nonexistent event exporter was referenced while adding a new metric dynamically via doveadm stats add. This produces a proper error now. - stats: If process exported a lot of events and then exited, some of the last events may have become lost. - stats: Invalid Prometheus label names were created with specific histogram group_by configurations. Prometheus rejected these labels. - welcome: The plugin didn't execute in some situations that created INBOX but didn't open it, e.g. if GETMETADATA was used before the INBOX was opened.

1 0

config: Error: Conflict in setting ssl_cert found from filter
by Ján Ondrušek 15 Sep '23

15 Sep '23

Hi! I see this intermittent error with my dovecot setup. The most puzzling part is that it sometimes works and sometimes rejects connections, spitting out the log I attached in systeport (DNS). I am binding both ipv4 (TLS+SNI) and ipv6 (dedicated addresses). TLS certificates for corresponding DNS are shared across ipv4 / ipv6. Thank you, Best regards, Jan

2 3

ACL management from SQL
by cyril.leclerc＠mantiq.com 14 Sep '23

14 Sep '23

Hello, we are facing issue, we manage the shared folder from SQL table, but it was never working as we have to manage acl permission from the server itself, we want to manage permissions (read or write) from the same application we can share user mailbox but it is written in dovecot documentation that is not supported now, we tried to find a mail client that could manage it at least, but only thunderbird was able to do it (but in version 60) and not more today. We saw that roundcube could handle it but we use rainloop. 1. It is really not possible at all to manage acl permissions fron SQL like the shared box itself ? 2. I tried to set acl permissions from old version of thunderbird, when i made modification it tried to update the sharedbox table, i did not see the query executed but as we were working on a view, the update failed. Do you know what it tried to do ?

3 8

Shared mailbox listing not working
by exactoph 14 Sep '23

14 Sep '23

Hi there, Having trouble with shared mailboxes. Followed the documentation, but the IMAP LIST doesn't work for mailboxes besides "INBOX" etc. In the meantime I've switched from file based acl_shared_dict to DB based as some people had problems with it. However still no success. I can see entries in the DB, doveadm acl get ... returns that the mailbox is shared, but it is not listed in doveadm mailbox list ... My configuration: https://pastebin.com/aWnMXJ4J Help would be very appreciated!

3 2

Roundcube
by joe a 13 Sep '23

13 Sep '23

Any known issues with installing/running roundcube and dovecot on the same server?

11 22

Trouble with SMTP, TLS and dovecot.org.
by Ralph Seichter 07 Sep '23

07 Sep '23

Hello, I cannot seem to send STARTTLS protected mail to talvi.dovecot.org, and I was wondering if anybody else sees similar problems: Sep 6 22:29:10 ra postfix/smtp[15748]: SSL_connect error to talvi.dovecot.org[94.237.105.223]:25: -1 Sep 6 22:29:10 ra postfix/smtp[15748]: warning: TLS library problem: error:0A000417:SSL routines::sslv3 alert illegal parameter:../openssl-3.0.9/ssl/record/rec_layer_s3.c:1586:SSL alert number 47: Sep 6 22:29:10 ra postfix/smtp[15748]: 1AAE4BE0031: Cannot start TLS: handshake failure Sep 6 22:29:10 ra postfix/smtp[15748]: SSL_connect error to talvi.dovecot.org[2a04:3545:1000:720:acc1:5bff:fe5e:459]:25: -1 Sep 6 22:29:10 ra postfix/smtp[15748]: warning: TLS library problem: error:0A000417:SSL routines::sslv3 alert illegal parameter:../openssl-3.0.9/ssl/record/rec_layer_s3.c:1586:SSL alert number 47: Sep 6 22:29:10 ra postfix/smtp[15748]: 1AAE4BE0031: to=<dovecot(a)dovecot.org>, relay=talvi.dovecot.org[2a04:3545:1000:720:acc1:5bff:fe5e:459]:25, delay=1.6, delays=0.02/0.01/1.6/0, dsn=4.7.5, status=deferred (Cannot start TLS: handshake failure) Sep 6 22:30:05 ra postfix/smtpd[15616]: timeout after END-OF-MESSAGE from localhost[127.0.0.1] Sep 6 22:30:05 ra postfix/smtpd[15616]: disconnect from localhost[127.0.0.1] ehlo=1 xforward=1 mail=1 rcpt=1 data=1 commands=5 The originating server uses Postfix 3.8.2 and OpenSSL library 3.0.9. To be able to send messages to dovecot.org at all, I had to use Postfix's "smtp_tls_policy_maps" setting to explicitly disable TLS for this destination domain. -Ralph

3 5

Fwd: DOvecot requires both IPv4 and IPV6 to start
by Stephen Satchell 06 Sep '23

06 Sep '23

Damn. Forgot to hit "reply all" -- my bad -------- Forwarded Message -------- Subject: Re: DOvecot requires both IPv4 and IPV6 to start Date: Mon, 4 Sep 2023 15:35:51 -0700 From: Stephen Satchell <list(a)satchell.net> Reply-To: list(a)satchell.net To: Arjen de Korte <build+dovecot(a)de-korte.org> On 9/4/23 2:40 PM, Arjen de Korte wrote: > This document was written something like two decades ago and pretty much > all arguments against IPv6 are no longer relevant anymore. In most cases > nowadays, the user experience for IPv6 will be far superior over CGNAT > connections which unfortunately become the standard due to the > increasing cost of IPv4 addresses. Running services over IPv6 may have > been experimental and prone with not so fun problems to diagnose in > 2013, but today this is no longer the case. Running a business? Subscribing to business Internet? Are IPv6 address blocks available? Does IPv6 routing work properly? OK, even though the service desk doesn't know how to answer the above questions about IPv6 correctly, the information *is* available if you dig hard enough. And it seems to work. Can you get a PTR6 record for your mail server? No. At least, not from my upstream. Begins with "A" and ends with "T". Don't even ask about reverse delegations, the blank stare will scare you. (I apologize to everyone on this list. The above diatribe more correctly lives on mailing lists for Sendmail, Postfix, Exim, and other packages that actually originate mail exchanges.)

2 1

DOvecot requires both IPv4 and IPV6 to start
by TWHG Technical 06 Sep '23

06 Sep '23

I think we are off topic. We have a network policy that until such time as we have fully implemented the same security we have on our IPV4 network we simply do not allow IPV6 as it is another attack vector we are not fully upto speed on. So we block all IPV6 at the perimeter and on all switches, firewalls and routers. So if you connect to our network with a device no IP6 is configured and only IPV4 is allowed. We will get there! But that is not this issue. The issue is that dovecot is assuming that IPV6 is there and crashes out if it's not. Hacking the config to only listen on IP4 solves the problem but not while installing from standard repos to install the currently supported version. Cheers Spart

9 13