- dovecot - dovecot.org

Re: 2.4 crashing on macOS with time moving forward?
by John Muccigrosso 04 Mar '25

04 Mar '25

OK, still crashed overnight while the laptop was closed. Here's the log. I had shut the laptop a bit before this first entry: Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds - adjusting timeouts. Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Mar 03 02:33:57 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102d8f120 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102d8f264 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102d9dd54 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102d9c7c4 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102d9c790 fatal_handler_real + 0 -> 5 dovecot 0x0000000102ab3538 master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102d9c940 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102db6724 ioloop_iolist_add + 0 -> 8 libdovecot.0.dylib 0x0000000102db4a3c io_loop_handle_timeouts + 640 -> 9 libdovecot.0.dylib 0x0000000102db7438 io_loop_handler_run_internal + 392 -> 10 libdovecot.0.dylib 0x0000000102db5130 io_loop_handler_run + 224 -> 11 libdovecot.0.dylib 0x0000000102db5000 io_loop_run + 92 -> 12 libdovecot.0.dylib 0x0000000102d0e22c master_service_run + 28 -> 13 dovecot 0x0000000102ab2e28 main + 2952 -> 14 dyld 0x0000000187c9ffd8 start + 2412 Mar 03 02:33:57 log(451): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) .There were a number of "Time moved forward" entries earlier as well. The one here was isolated, but often they occur in pairs with nearly identical amounts of time, differing only by the fractions of a second between them, I suppose. For example (pairs highlighted with the same color): Mar 04 13:12:38 master: Warning: Time moved forward by 9.347642 seconds - adjusting timeouts. Mar 04 13:14:31 imap(12422): Warning: Time moved forward 83.410157 seconds Mar 04 13:14:31 imap(12420): Warning: Time moved forward 83.410166 seconds Mar 04 13:19:44 imap(12422): Warning: Time moved forward 282.970564 seconds Mar 04 13:19:44 imap(12420): Warning: Time moved forward 282.970608 seconds Mar 04 13:19:44 master: Warning: Time moved forward by 366.378919 seconds - adjusting timeouts. Mar 04 13:25:27 imap(12422): Warning: Time moved forward 282.941775 seconds Mar 04 13:25:27 imap(12420): Warning: Time moved forward 282.943614 seconds Mar 04 13:25:27 master: Warning: Time moved forward by 282.937627 seconds - adjusting timeouts. Mar 04 13:30:20 imap(12422): Warning: Time moved forward 263.355743 seconds Mar 04 13:30:20 imap(12420): Warning: Time moved forward 263.350968 seconds Now that I look, I realize that most, but not all, of the imap warnings (vs master) come in pairs. J > On Mar 2, 2025, at 18:18, J wrote: > > OK, done. Will restart. Here's the new pmset info: > > System-wide power settings: > SleepDisabled 0 > Currently in use: > standby 1 > Sleep On Power Button 1 > hibernatefile /var/vm/sleepimage > powernap 1 > networkoversleep 0 > disksleep 10 > sleep 1 (sleep prevented by useractivityd, powerd, sharingd) > hibernatemode 3 > ttyskeepawake 1 > displaysleep 20 > tcpkeepalive 1 > lowpowermode 0 > womp 0 > > J > >> On Mar 2, 2025, at 16:44, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >> >> Hi! >> >> Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? >> >> Aki >> >>> On 02/03/2025 17:30 EET J wrote: >>> >>> >>> Below are the results of "pmset -g". >>> >>> Keep in mind that this >>> >>> >>> J >>> >>> >>>> On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >>>> >>>> >>>> I wonder if this is some power saving feature that pauses dovecot processes? Do >>>> you have power saving enabled? >>> >>> >>> >>> System-wide power settings: >>> SleepDisabled0 >>> Currently in use: >>> standby 1 >>> Sleep On Power Button 1 >>> hibernatefile /var/vm/sleepimage >>> powernap 1 >>> networkoversleep 0 >>> disksleep 10 >>> sleep 1 (sleep prevented by powerd) >>> hibernatemode 3 >>> ttyskeepawake 1 >>> displaysleep 20 >>> tcpkeepalive 1 >>> lowpowermode 1 >>> womp 0 >> >> _______________________________________________ >> dovecot mailing list -- dovecot(a)dovecot.org >> To unsubscribe send an email to dovecot-leave(a)dovecot.org >

1 0

Re: 2.4 crashing on macOS with time moving forward?
by John Muccigrosso 03 Mar '25

03 Mar '25

OK, first here's a series of warnings while the laptop was closed, 18:43-19:04: Mar 02 18:44:02 imap(1392): Warning: Time moved forward 24.925040 seconds Mar 02 18:44:02 imap(1397): Warning: Time moved forward 24.925062 seconds Mar 02 19:01:24 imap(1397): Warning: Time moved forward 993.009103 seconds Mar 02 19:01:24 imap(1392): Warning: Time moved forward 993.023098 seconds Mar 02 19:04:57 imap(1397): Warning: Time moved forward 182.863245 seconds Mar 02 19:04:57 imap(1392): Warning: Time moved forward 182.871467 seconds But it took until overnight, when the laptop was again closed, for the crash: Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds - adjusting timeouts. Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Mar 03 02:33:57 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102d8f120 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102d8f264 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102d9dd54 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102d9c7c4 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102d9c790 fatal_handler_real + 0 -> 5 dovecot 0x0000000102ab3538 master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102d9c940 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102db6724 ioloop_iolist_add + 0 -> 8 libdovecot.0.dylib 0x0000000102db4a3c io_loop_handle_timeouts + 640 -> 9 libdovecot.0.dylib 0x0000000102db7438 io_loop_handler_run_internal + 392 -> 10 libdovecot.0.dylib 0x0000000102db5130 io_loop_handler_run + 224 -> 11 libdovecot.0.dylib 0x0000000102db5000 io_loop_run + 92 -> 12 libdovecot.0.dylib 0x0000000102d0e22c master_service_run + 28 -> 13 dovecot 0x0000000102ab2e28 main + 2952 -> 14 dyld 0x0000000187c9ffd8 start + 2412 Mar 03 02:33:57 log(451): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) A couple of observations: 1. There are often two warnings within a second, for time periods that are nearly, but not quite identical. 2. The time periods in question are long, minutes or tens of minutes. J > On Mar 2, 2025, at 18:18, J wrote: > > OK, done. Will restart. Here's the new pmset info: > > System-wide power settings: > SleepDisabled 0 > Currently in use: > standby 1 > Sleep On Power Button 1 > hibernatefile /var/vm/sleepimage > powernap 1 > networkoversleep 0 > disksleep 10 > sleep 1 (sleep prevented by useractivityd, powerd, sharingd) > hibernatemode 3 > ttyskeepawake 1 > displaysleep 20 > tcpkeepalive 1 > lowpowermode 0 > womp 0 > > J > >> On Mar 2, 2025, at 16:44, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >> >> Hi! >> >> Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? >> >> Aki >> >>> On 02/03/2025 17:30 EET J wrote: >>> >>> >>> Below are the results of "pmset -g". >>> >>> Keep in mind that this >>> >>> >>> J >>> >>> >>>> On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: >>>> >>>> >>>> I wonder if this is some power saving feature that pauses dovecot processes? Do >>>> you have power saving enabled? >>> >>> >>> >>> System-wide power settings: >>> SleepDisabled0 >>> Currently in use: >>> standby 1 >>> Sleep On Power Button 1 >>> hibernatefile /var/vm/sleepimage >>> powernap 1 >>> networkoversleep 0 >>> disksleep 10 >>> sleep 1 (sleep prevented by powerd) >>> hibernatemode 3 >>> ttyskeepawake 1 >>> displaysleep 20 >>> tcpkeepalive 1 >>> lowpowermode 1 >>> womp 0 >> >> _______________________________________________ >> dovecot mailing list -- dovecot(a)dovecot.org >> To unsubscribe send an email to dovecot-leave(a)dovecot.org > OK, first here's a series of warnings while the laptop was closed, 18:43-19:04: Mar 02 18:44:02 imap(1392): Warning: Time moved forward 24.925040 seconds Mar 02 18:44:02 imap(1397): Warning: Time moved forward 24.925062 seconds Mar 02 19:01:24 imap(1397): Warning: Time moved forward 993.009103 seconds Mar 02 19:01:24 imap(1392): Warning: Time moved forward 993.023098 seconds Mar 02 19:04:57 imap(1397): Warning: Time moved forward 182.863245 seconds Mar 02 19:04:57 imap(1392): Warning: Time moved forward 182.871467 seconds But it took until overnight, when the laptop was again closed, for the crash: Mar 03 00:43:13 master: Warning: Time moved forward by 4451.650853 seconds - adjusting timeouts. Mar 03 02:33:57 master: Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) Mar 03 02:33:57 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x0000000102d8f120 backtrace_append + 72 -> 1 libdovecot.0.dylib 0x0000000102d8f264 backtrace_get + 44 -> 2 libdovecot.0.dylib 0x0000000102d9dd54 default_fatal_finish + 72 -> 3 libdovecot.0.dylib 0x0000000102d9c7c4 default_error_handler + 0 -> 4 libdovecot.0.dylib 0x0000000102d9c790 fatal_handler_real + 0 -> 5 dovecot 0x0000000102ab3538 master_fatal_callback + 248 -> 6 libdovecot.0.dylib 0x0000000102d9c940 i_fatal + 0 -> 7 libdovecot.0.dylib 0x0000000102db6724 ioloop_iolist_add + 0 -> 8 libdovecot.0.dylib 0x0000000102db4a3c io_loop_handle_timeouts + 640 -> 9 libdovecot.0.dylib 0x0000000102db7438 io_loop_handler_run_internal + 392 -> 10 libdovecot.0.dylib 0x0000000102db5130 io_loop_handler_run + 224 -> 11 libdovecot.0.dylib 0x0000000102db5000 io_loop_run + 92 -> 12 libdovecot.0.dylib 0x0000000102d0e22c master_service_run + 28 -> 13 dovecot 0x0000000102ab2e28 main + 2952 -> 14 dyld 0x0000000187c9ffd8 start + 2412 Mar 03 02:33:57 log(451): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) A couple of observations: 1. There are often two warnings within a second, for time periods that are nearly, but not quite identical. 2. The time periods in question are long, minutes or tens of minutes. J On Mar 2, 2025, at 18:18, J wrote: OK, done. Will restart. Here's the new pmset info: System-wide power settings: SleepDisabled 0 Currently in use: standby 1 Sleep On Power Button 1 hibernatefile /var/vm/sleepimage powernap 1 networkoversleep 0 disksleep 10 sleep 1 (sleep prevented by useractivityd, powerd, sharingd) hibernatemode 3 ttyskeepawake 1 displaysleep 20 tcpkeepalive 1 lowpowermode 0 womp 0 J On Mar 2, 2025, at 16:44, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: Hi! Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? Aki On 02/03/2025 17:30 EET J wrote: Below are the results of "pmset -g". Keep in mind that this J On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: I wonder if this is some power saving feature that pauses dovecot processes? Do you have power saving enabled? System-wide power settings: SleepDisabled0 Currently in use: standby 1 Sleep On Power Button 1 hibernatefile /var/vm/sleepimage powernap 1 networkoversleep 0 disksleep 10 sleep 1 (sleep prevented by powerd) hibernatemode 3 ttyskeepawake 1 displaysleep 20 tcpkeepalive 1 lowpowermode 1 womp 0 _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Re: 2.4 crashing on macOS with time moving forward?
by Aki Tuomi 02 Mar '25

02 Mar '25

Hi! Can you try disabling "low power mode" and see if that makes any difference? I don't have a mac, but try to go System Settings > Battery, select the drop-down menu next to Low Power Mode, and choose Never? Aki > On 02/03/2025 17:30 EET John Muccigrosso <muccigrosso(a)icloud.com> wrote: > > > Below are the results of "pmset -g". > > Keep in mind that this > > > J > > > > On Mar 2, 2025, at 15:51, Aki Tuomi via dovecot <dovecot(a)dovecot.org> wrote: > > > > > > I wonder if this is some power saving feature that pauses dovecot processes? Do > > you have power saving enabled? > > > > System-wide power settings: > SleepDisabled0 > Currently in use: > standby 1 > Sleep On Power Button 1 > hibernatefile /var/vm/sleepimage > powernap 1 > networkoversleep 0 > disksleep 10 > sleep 1 (sleep prevented by powerd) > hibernatemode 3 > ttyskeepawake 1 > displaysleep 20 > tcpkeepalive 1 > lowpowermode 1 > womp 0

1 0

2.4 crashing on macOS with time moving forward?
by John Muccigrosso 02 Mar '25

02 Mar '25

After last week's struggle with the new version and my conf file, I got everything working. Now however dovecot crashes on me every few hours. The logs show a bunch of this kind of warning, which I find mention of on the internets: > Feb 07 15:13:47 imap(58317): Warning: Time moved forward 48.803640 seconds > Feb 07 16:30:27 master: Warning: Time moved forward by 694.039203 seconds - adjusting timeouts. > Feb 07 16:52:47 imap(61246): Warning: Time moved forward 293.443011 seconds > Feb 07 16:52:47 master: Warning: Time moved forward by 1279.423507 seconds - adjusting timeouts. > Feb 07 17:25:39 imap(61286): Warning: Time moved forward 1942.575589 seconds > Feb 07 17:25:39 imap(61288): Warning: Time moved forward 172.563346 seconds > Feb 07 17:25:39 master: Warning: Time moved forward by 1912.666999 seconds - adjusting timeouts. > Feb 07 17:49:32 imap(61286): Warning: Time moved forward 1402.761862 seconds > Feb 07 17:51:13 master: Warning: Time moved forward by 1473.582569 seconds - adjusting timeouts. > Feb 07 17:51:13 imap(61286): Warning: Time moved forward 70.823888 seconds > Feb 07 17:53:07 master: Warning: Time moved forward by 53.843767 seconds - adjusting timeouts. > Feb 07 18:44:22 imap(61286): Warning: Time moved forward 1386.259444 seconds > Feb 07 19:11:41 master: Warning: Time moved forward by 615.609964 seconds - adjusting timeouts. Note the very large jump dovecot claims is happening in all of these, up to half an hour, with a minimum of 48 seconds in this bunch. You can see that it even does a pair of these in rapid succession, like at 17:25:39 above, and will do >10 within the space of an hour. These seem eventually to be followed by a crash ("eventually" because I'm running this on my laptop which isn't always open and running). The crash log entries all start with something like this: > Feb 07 16:17:53 imap(58315): Panic: file ./time-util.h: line 40 (timeval_add_usecs): assertion failed: (usecs >= 0) The reports will end with one of these: > Feb 06 17:45:07 log(48089): Warning: Killed with signal 15 (by pid=1 uid=0 code=unknown 0) > Feb 07 16:17:53 imap(58317): Fatal: master: service(imap): child 58317 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) One more detail, I usually do `sudo brew services start dovecot` to run dovecot and this results in the crashes. When I was testing this on Saturday, I started it with `sudo dovecot -F` instead, so that I would see problems in the terminal. It went all day without crashing and I finally stopped and restarted it with the brew method. That's not a rigorous test, but it is suggestive. Happy to provide more info, but I'm hoping this is sufficient to suggest a course of action. dovecot 2.4.0 installed via homebrew macOS 13.6.9 J

3 8

Pigeonhole: sieve_redirect_envelope_from orig_recipient results in mail bombs
by doobry 28 Feb '25

28 Feb '25

Dear Dovecot community, we changed `sieve_redirect_envelope_from` to `orig_recipient` recently to fix sieve redirects in case the forwarded mail comes from a DMARC-enabled domain. While this works well, it creates a new problem: if the receiving mail server (the one in charge of the redirect destination) reacts with a bounce mail, the bounce now will go to `orig_recipient` - the mail address that has the redirect in place, which means no less than creating a mail bomb (endless mail loop). See the following example: 1. alice(a)sender.org sends mail to jane(a)our-domain.org 2. jane(a)our-domain.org has a sieve redirect to jane(a)redirect-target.org 3. jane(a)redirect-target.org replies with a bounce because their mailbox is full. 4. The bounce mail gets sent to jane(a)our-domain.org. 5. The loop starts again at step 2. Is it possible to configure dovecot/pigeonhole to *not* forward the bounce mails from step 4 again? Probably it would work to add manual extra checks to the sieve redirect rules, but that would need to be followed by any user who configures a redirect. So I'm more looking for a server-wide configuration change that fixes this problem. Looking forward to hear about your thoughts on the problem. Kind regards doobry

3 3

Dovecot 2.4.0 multiple hosts SNI configuration regression
by Julius Kriukas 27 Feb '25

27 Feb '25

Hello everyone. We are testing out Dovecot 2.4.0 and noticed a regression in how the `local_name` filter with multiple space-separated host names works. For example, having the following dovecot.conf: ``` ... ssl_server_cert_file = /etc/dovecot/global.cert ssl_server_key_file = /etc/dovecot/global.key ssl_server_dh_file = /etc/dovecot/dh.pem ... local_name "server.example.com mail.example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } local_name "good.example.org" { ssl_server_cert_file = /etc/dovecot/example.org.cert ssl_server_key_file = /etc/dovecot/example.org.key } ... ``` Connection to server.example.com:993 (with SNI support) does not work as expected. The global certificate from the `global.cert` file is used, and validation fails. However, connection to good.example.org:993 (with SNI support) works fine. The `example.org.cert` file is used. The `doveconf` tool thinks the example configuration should work, hinting that this is likely to be a bug. Example: ``` # doveconf -f local_name=mail.example.com ssl_server ssl_server { cert_file = /etc/dovecot/example.com.cert dh_file = /etc/dovecot/dh.pem key_file = /etc/dovecot/example.com.key } ``` The results show correct file paths, but the `dovecot` server is not using them. Any confirmation if this is really a bug, or maybe an intended configuration syntax change (to force repeating the local_name blocks for each hostname) would be really appreciated. Thanks. -- Julius

3 3

Issue with ACLs in Dovecot 2.4
by Andrea Gabellini 27 Feb '25

27 Feb '25

Hi, I'm trying to migrate my setup to Dovecot 2.4, but I'm experiencing an unusual issue with ACLs. After multiple tests, I’ve stripped the configuration down to the bare minimum to pinpoint the root cause of the problem. Basically, if I set "owner lr" as the permissions for a folder, I am unable to move any messages, yet I can still create subfolders. Here’s the relevant configuration: ini Copia Modifica protocol imap { mail_plugins { acl = yes } } acl_driver = vfile acl_globals_only = yes namespace inbox { inbox = yes separator = / mailbox Test { acl owner { rights = lr } } } Am I missing any configuration, or have I encountered a bug? Thanks, Andrea -- TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 2

Strange problem with iPhone Mail
by Simon Hoffmann 27 Feb '25

27 Feb '25

Hey list, I am experiencing a strange problem where I don't even know where to begin to debug. I am running my own email server in my office. The server itself works fine. In my office firewall, I have set up DNAT/port forwarding to be able to access the server from outside. With my Android phone and my iPad I have no problems accessing the mails from anywhere, including my home WiFi. However with my iPhone, I have problems accessing my inbox when I am on my home WiFi. The problems only started a few weeks ago, it worked fine for years before. I have not changed any network related settings. Now, when I am on my home WiFi, I cannot use the "pull down to refresh" gesture. It just is not fetching any emails. The automatic sync/fetching is also not fetching the newest emails. Eventually, some emails will come through, but they are from ~6-7 hours ago. Same WiFi as my other devices that work fine. As soon as I disable WiFi on my iPhone and switch to mobile data and do the "pull down to refresh" gesture, all mails from the last 6-7 hours immediately come in. Has anyone ever experienced something like this and can help me analyse the problem? root@mx01:~# uname -a Linux mx01 5.10.0-33-amd64 #1 SMP Debian 5.10.226-1 (2024-10-03) x86_64 GNU/Linux root@mx01:~# cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 11 (bullseye)" NAME="Debian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@mx01:~# dpkg -l dovecot* ||/ Name Version Architektur Beschreibung +++-======================-========================-============-=============================================== un dovecot-abi-2.3.abiv13 <keine> <keine> (keine Beschreibung vorhanden) un dovecot-common <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-core 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - core files un dovecot-gssapi <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-imapd 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - IMAP daemon un dovecot-ldap <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-lmtpd 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - LMTP server un dovecot-lucene <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-managesieved 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - ManageSieve server un dovecot-mysql <keine> <keine> (keine Beschreibung vorhanden) un dovecot-pgsql <keine> <keine> (keine Beschreibung vorhanden) un dovecot-pop3d <keine> <keine> (keine Beschreibung vorhanden) ii dovecot-sieve 1:2.3.13+dfsg1-2+deb11u2 amd64 secure POP3/IMAP server - Sieve filters support un dovecot-solr <keine> <keine> (keine Beschreibung vorhanden) un dovecot-sqlite <keine> <keine> (keine Beschreibung vorhanden) un dovecot-submissiond <keine> <keine> (keine Beschreibung vorhanden) Thanks! Cheers, Simon

2 1

Fwd: Re: Thunderbird IMAP Problem
by Felix Zielcke 26 Feb '25

26 Feb '25

Forgot to CC list. -------- Weitergeleitete Nachricht -------- Von: Felix Zielcke <fzielcke(a)z-51.de> An: wertstoffe(a)nurfuerspam.de Betreff: Re: Thunderbird IMAP Problem Datum: 26.02.2025 14:43:36 > Am Mittwoch, dem 26.02.2025 um 13:47 +0100 schrieb Jakob: > > Ok... > > > > And does imap-login with thunderbird also work with this patch? > > > > Will this patch be merged in a further release from dovecot? > > I don't like selfcompiling... > > > > Jakob > > > > It's a patch for exim4 not dovecot. So it only fixes SMTP > authentication with it. > Timo said that there will probable be some sort of workaround in > dovecot 2.4.1. included. > > So no it won't fix imap-login. > I don't use Thunderbird so I have no clue why it fails for you. > Maybe it would have been useful to have your dovecot config?

2 1

Thunderbird IMAP Problem
by wertstoffe＠nurfuerspam.de 26 Feb '25

26 Feb '25

Hi there! I upgraded to dovecot 2.4 from dovecot repo on my debian bookworm. I modified the config for the needs for 2.4. My Fairemail could connect to dovecot and receive emails via imap. But thunderbird did not work. I activated the debug-logging for thunderbird in shell and got this |2025-02-26 07:46:15.775740 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770954ef3f00] 2025-02-26 07:46:15.776145 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770957d74600] 2025-02-26 07:46:15.776820 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776853 UTC - [Parent 677248: Main Thread]: I/IMAP queuing url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776869 UTC - [Parent 677248: Main Thread]: I/IMAP considering playing queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776881 UTC - [Parent 677248: Main Thread]: I/IMAP creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776897 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776909 UTC - [Parent 677248: Main Thread]: I/IMAP failed creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.777125 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777217 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777302 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777317 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777348 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/discoverallboxes: = currentUrl 2025-02-26 07:46:15.777362 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777404 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777420 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/select%3E/INBOX: = currentUrl 2025-02-26 07:46:15.822761 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823122 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823329 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823509 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/discoverallboxes) 2025-02-26 07:46:15.823573 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823816 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/select%3E/INBOX) 2025-02-26 07:46:15.824515 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824529 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824723 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00:imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824748 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770954ef3f00] 2025-02-26 07:46:15.824760 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600:imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824785 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770957d74600] Dovecot-log shows only this two lines on a login-try with thunderbird. ||Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<ryQk2gYvMp+sHgAB> Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<zR8k2gYvIp+sHgAB> Other logins had a user and auth attempts... only from thunderbird it does not work. I also use dovecot-login for my exim4. And smtp-login was also not able. Not even directly via openssl s_client. I could connect, send ehlo, and when i sent AUTH LOGIN <base64-username-passwor-string> and then it hangs. I went back to dovecot 2.3, and thunderbird could login again, also smtp-login works. There seems something wrong in dovecot 2.4. Have ldap-authentication. My bad, i deinstalled dovecot 2.4 and now i can not create a conf with doveconf to add it here. Hope you can help me. Jakob | Hi there! I upgraded to dovecot 2.4 from dovecot repo on my debian bookworm. I modified the config for the needs for 2.4. My Fairemail could connect to dovecot and receive emails via imap. But thunderbird did not work. I activated the debug-logging for thunderbird in shell and got this 2025-02-26 07:46:15.775740 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770954ef3f00] 2025-02-26 07:46:15.776145 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop entering [this=770957d74600] 2025-02-26 07:46:15.776820 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/ Synoptic/Rechnungen 2025-02-26 07:46:15.776853 UTC - [Parent 677248: Main Thread]: I/IMAP queuing url:imap://my.user@imap.domain.tld:143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776869 UTC - [Parent 677248: Main Thread]: I/IMAP considering playing queued url:imap://my.user@imap.domain.tld:143/ folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776881 UTC - [Parent 677248: Main Thread]: I/IMAP creating protocol instance to play queued url:imap://my.user@imap.domain.tld:143/ folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.776897 UTC - [Parent 677248: Main Thread]: I/IMAP exceeded connection cache limit:imap://my.user@imap.domain.tld:143/folderstatus>/ Synoptic/Rechnungen 2025-02-26 07:46:15.776909 UTC - [Parent 677248: Main Thread]: I/IMAP failed creating protocol instance to play queued url:imap://my.user@imap.domain.tld: 143/folderstatus>/Synoptic/Rechnungen 2025-02-26 07:46:15.777125 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777217 UTC - [Parent 677248: Main Thread]: I/IMAP 770954ef3f00:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777302 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupWithUrlCallback: clearing IMAP_CONNECTION_IS_OPEN 2025-02-26 07:46:15.777317 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777348 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/ discoverallboxes: = currentUrl 2025-02-26 07:46:15.777362 UTC - [Parent 677248: Main Thread]: I/IMAP 770957d74600:imap.domain.tld:NA:SetupSinkProxy: got m_imapMailFolderSink 2025-02-26 07:46:15.777404 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:ProcessCurrentURL: entering 2025-02-26 07:46:15.777420 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:ProcessCurrentURL:imap://my.user@imap.domain.tld:143/ select%3E/INBOX: = currentUrl 2025-02-26 07:46:15.822761 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823122 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:CreateNewLineFromSocket: * OK [CAPABILITY +SPECIAL-USE STARTTLS AUTH=PLAIN] Dovecot ready. 2025-02-26 07:46:15.823329 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823509 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/discoverallboxes) 2025-02-26 07:46:15.823573 UTC - [Parent 677248: IMAP]: D/IMAP SetConnectionStatus(0x80004005) 2025-02-26 07:46:15.823816 UTC - [Parent 677248: IMAP]: D/IMAP URL failed with code 0x80004005 (imap://my.user@imap.domain.tld:143/select%3E/INBOX) 2025-02-26 07:46:15.824515 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824529 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:ProcessCurrentURL: aborting queued urls 2025-02-26 07:46:15.824723 UTC - [Parent 677248: IMAP]: I/IMAP 770954ef3f00: imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824748 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770954ef3f00] 2025-02-26 07:46:15.824760 UTC - [Parent 677248: IMAP]: I/IMAP 770957d74600: imap.domain.tld:NA:TellThreadToDie: close socket connection 2025-02-26 07:46:15.824785 UTC - [Parent 677248: IMAP]: D/IMAP ImapThreadMainLoop leaving [this=770957d74600] Dovecot-log shows only this two lines on a login-try with thunderbird. Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<ryQk2gYvMp+sHgAB> Feb 26 08:52:16 mail dovecot[204586]: imap-login: Login aborted: Connection closed (no auth attempts in 0 secs) (no_auth_attempts): user=<>, rip=172.30.0.1, lip=172.30.0.9, session=<zR8k2gYvIp+sHgAB> Other logins had a user and auth attempts... only from thunderbird it does not work. I also use dovecot-login for my exim4. And smtp-login was also not able. Not even directly via openssl s_client. I could connect, send ehlo, and when i sent AUTH LOGIN <base64-username- passwor-string> and then it hangs. I went back to dovecot 2.3, and thunderbird could login again, also smtp-login works. There seems something wrong in dovecot 2.4. Have ldap-authentication. My bad, i deinstalled dovecot 2.4 and now i can not create a conf with doveconf to add it here. Hope you can help me. Jakob

2 1