- dovecot - dovecot.org

Some folders are not displayed correctly via IMAP protocol
by Lafiel 10 Mar '25

10 Mar '25

Hi. The Bat! email client does not display folder, it will appear as ' Example'. The email client technical support said quotation marks. Log IMAP: ``` C: { ------ TImapUpdateSubscription sta C: 9 LSUB "" "*" S: * LSUB (\Drafts) "." Drafts S: * LSUB (\Sent) "." Sent S: * LSUB (\Junk) "." Junk S: * LSUB (\Trash) "." Trash S: * LSUB () "." [Example] S: * LSUB () "." Example S: 9 OK Lsub completed (0.001 + 0.000 s C: } ------ TImapUpdateSubscription fin ``` I'm using the Dovecot version 2.3.21.1. -- Best regards, Lafiel mailto:lafiel@elven.pw

2 2

Questions about fts_flatcurve in Dovecot 2.4
by Andrea Gabellini 10 Mar '25

10 Mar '25

Hi, I'm testing the fts_flatcurve plugin on Dovecot 2.4. This is my first time using an FTS plugin, and I have a few questions. Below is the configuration I am referring to. - Does the language_filters setting apply by default when a language xx {} section is defined? - If so, within a language section where a filter is declared, should I set filter_name = no to remove it? - The documentation includes this warning: "Using stopwords with multiple languages configured WILL cause some searches to fail. The recommended solution is to NOT use the stopword filter when multiple languages are present in the configuration." Does this mean it's best to avoid the stopwords filter entirely, or can it still be used for at least one language? - Does the attached configuration make sense? :-) language_filters { lowercase = yes normalizer-icu = yes snowball = yes } language it { default = yes filters { lowercase = yes normalizer-icu = yes snowball = yes stopwords = yes } } language en { } language de { } language es { } language fr { filters { lowercase = yes normalizer-icu = yes snowball = yes contractions = yes } } Thanks in advance for your support! 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.

1 0

Dovecot Crash
by Kent Borg 08 Mar '25

08 Mar '25

In this morning's logwatch e-mail I see a dovecot crash: > Mar 7 20:45:49 la postfix/local[1059550]: 5F068405A88E8: > to=<kentborg(a)mail2.borg.org>, orig_to=<kentborg-lkml(a)borg.org>, > relay=local, delay=0.35, delays=0.35/0/0/0, dsn=2.0.0, status=sent > (delivered to maildir) > Mar 7 20:45:49 la postfix/qmgr[1620]: 5F068405A88E8: removed > Mar 7 20:45:50 la dovecot[1194]: > doveadm(kentborg)<1059554><Dd8IBXzLy2fiKhAAA8+vgQ>: Panic: file > dsync-ibc.c: line 168 (dsync_ibc_send_mail_request): assertion failed: > (request->guid != NULL || request->uid != 0) > Mar 7 20:45:50 la dovecot[1194]: > doveadm(kentborg)<1059554><Dd8IBXzLy2fiKhAAA8+vgQ>: Error: Raw > backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x5c) > [0x7f920106dc] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x24) > [0x7f92010848] -> /usr/lib/dovecot/libdovecot.so.0(+0xfd750) > [0x7f9201d750] -> > /usr/lib/dovecot/libdovecot.so.0(i_syslog_error_handler+0) > [0x7f9201e064] -> /usr/lib/dovecot/libdovecot.so.0(i_unreached+0) > [0x7f91f6698c] -> > dovecot/doveadm-server(dsync_ibc_send_mail_request+0xd8) > [0x558263fb38] -> > dovecot/doveadm-server(dsync_brain_sync_mails+0x\2f0) [0x5582639440] > -> dovecot/doveadm-server(+0x4eea0) [0x558262eea0] -> > dovecot/doveadm-server(+0x4f338) [0x558262f338] -> > dovecot/doveadm-server(+0x5b2b4) [0x558263b2b4] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x74) [0x7f92039d44] > -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x138) > [0x7f9203c488] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) > [0x7f9203c5d4] -> /usr/lib/dovecot/libdo\vecot.so.0(io_loop_run+0x44) > [0x7f9203c898] -> dovecot/doveadm-server(+0x32374) [0x5582612374] -> > dovecot/doveadm-server(+0x32ed4) [0x5582612ed4] -> > dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x610) > [0x5582614514] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x448) > [0x558261ef18] -> dovecot/doveadm-server(+0x4aeac) [0x558262aeac] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x74) [0x7f92039d44] > -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x138) > [0x7f9203c488] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) > [0x7f9203c5d4] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x44) > [0x7f9203c898] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x20) > [0x7f91f99ef0] -> dovecot/doveadm-server(main+0x108) [0x55825fe708] -> > /lib/aarch64-linux-gnu/libc.so.6(+0x27740) [0x7f91cf7740] -> > /lib/aarch64-linux-gnu/libc.so.6(__libc_start_main+0x98) > [0x7f91cf7818] -> dovecot/doveadm-server(_start+0x30) [0x55825fe7b0] > Mar 7 20:45:50 la dovecot[1194]: > doveadm(kentborg)<1059554><Dd8IBXzLy2fiKhAAA8+vgQ>: Fatal: master: > service(doveadm): child 1059554 killed with signal 6 (core dumps > disabled - https://dovecot.org/bugreport.html#coredumps) I am assuming that message 5F068405A88E8 was the one being processed, and it seems to have vanished. It is one thing for me to have dsync glitches that fix themselves, but this is a serious bug if I am losing e-mail. I am running Dovecot 2.3.19.1 (b907e01) with two small changes I've talked about before* (https://github.com/kentborg/dovecot-core on branch kb-replicator_queue_handle_sync_lookups) on Debian 12. -kb * These changes are not up the call chain from this crash. I tried to make a pull request for my changes but got stalled on figuring out how to reference my repository in the github GUI. Do I need to download their custom CLI tools to do it?

1 0

Re: Some folders are not displayed correctly via IMAP protocol
by Lafiel 07 Mar '25

07 Mar '25

Hi, Michael Slusarz. The client developers claim that in practice this approach leads to various problems for users. In one case, the square lines may be treated as a syntax element, and in others as part of the folder name. Predicting what is what is extremely difficult. How can i modify source code in my mail server to force the use of quotes? Michael Slusarz писал(а) 2025-03-07 08:33: > Given the mailbox 'Trash', it's fine for a server to send it back either with or without double quotes (see the RFC 3501 > ABNF). > > Thus, either of these are allowable under the > standard: > > S: * LSUB () "/" > "Trash" > S: * LSUB () "/" > Trash > > Apparently your client is not handling the non-quoted alternative correctly (the 2nd example). So this is a client bug, at least if the client is claiming to be IMAP4rev1 > compliant. > > michael -- Best regards, Lafiel mailto:lafiel@elven.pw

1 0

Re: Some folders are not displayed correctly via IMAP protocol
by Michael Slusarz 07 Mar '25

07 Mar '25

> On 03/06/2025 8:47 PM MST Stephan Bosch via dovecot <dovecot(a)dovecot.org> wrote: > > Can you explain what exactly is wrong in that output? I think it's this: S: * LSUB () "." [Example] Groking ABNF (from RFC 3501): mailbox-data = ... "LSUB" SP mailbox-list ... mailbox-list = "(" [mbx-list-flags] ")" SP (DQUOTE QUOTED-CHAR DQUOTE / nil) SP mailbox // Looking at "mailbox" part... mailbox = "INBOX" / astring astring = 1*ASTRING-CHAR / string ASTRING-CHAR = ATOM-CHAR / resp-specials ATOM-CHAR = <any CHAR except atom-specials> atom-specials = "(" / ")" / "{" / SP / CTL / list-wildcards / quoted-specials / resp-specials list-wildcards = "%" / "*" quoted-specials = DQUOTE / "\" resp-specials = "]" So... for the mailbox "[Example]", the "]" is the character that is troubling, since it is an "atom-special". *However*, "mailbox" is an astring, which can be composed of ASTRING-CHARs, and that element specifically adds the "]" back into the list of allowable characters. Put another way, a "mailbox" only requires quoting (an IMAP "string") if it contains one of the following characters: (){<SP><CTL>%*"\ The mailbox [Example] does not contain any of these forbidden characters, so it can be output without quotes. The Dovecot output you have provided is standards compliant. michael > Op 6-3-2025 om 14:59 schreef Lafiel via dovecot: > > Hi. > > > > The Bat! email client does not display > > folder, it will appear as ' Example'. > > > > The email client technical support said > > quotation marks. > > > > Log IMAP: > > ``` > > C: { ------ TImapUpdateSubscription sta > > C: 9 LSUB "" "*" > > S: * LSUB (\Drafts) "." Drafts > > S: * LSUB (\Sent) "." Sent > > S: * LSUB (\Junk) "." Junk > > S: * LSUB (\Trash) "." Trash > > S: * LSUB () "." [Example] > > S: * LSUB () "." Example > > S: 9 OK Lsub completed (0.001 + 0.000 s > > C: } ------ TImapUpdateSubscription fin > > ``` > > > > I'm using the Dovecot version 2.3.21.1. > > > > > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org

1 0

Issue with mail-crypt plugin on Debian Bookworm and Dovecot 2.4
by Andrea Gabellini 05 Mar '25

05 Mar '25

Hi everyone, I'm trying to use the mail-crypt plugin on Debian Bookworm with Dovecot 2.4. This is my first time using it, so please forgive any basic questions... I've added the following configuration: mail_plugins { mail_crypt = yes } crypt_global_public_key_file = /etc/dovecot/xxx_pub.pem crypt_global_private_key main { crypt_private_key_file = /etc/dovecot/xxx_priv.pem } log_debug = category=debug However, as soon as I try to use it, I see the following log entry: Fatal: dcrypt_initialize(): Plugin 'dcrypt_openssl' not found from directory /usr/lib/x86_64-linux-gnu/dovecot I've searched my file system and checked the available dovecot-* packages, but I couldn't find any trace of the missing library. Am I missing something, or is this library indeed absent from the official packages? Thanks in advance for your help! Best regards, 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 8

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