- dovecot - dovecot.org

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 26 Feb '25

26 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

dovecot Panic
by Jakob 23 Feb '25

23 Feb '25

Hi! I face in short intervals (every few minutes) such error-messages in dovecot Feb 24 01:36:26 mail dovecot[699699]: imap(user.name)<711331><0D3Ch9guy6UufflE>: Panic: file mail-index-view.c: line 165 (view_lookup_full): assertion failed: (seq > 0 && seq <= mail_in dex_view_get_messages_count(view)) Feb 24 01:36:26 mail dovecot[699699]: imap(user.name)<711331><0D3Ch9guy6UufflE>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fb1e519f662] -> /usr/l ib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb1e519f77e] -> /usr/lib/dovecot/libdovecot.so.0(+0x1043db) [0x7fb1e51ac3db] -> /usr/lib/dovecot/libdovecot.so.0(+0x104471) [0x7fb1e51ac471 ] -> /usr/lib/dovecot/libdovecot.so.0(+0x566a0) [0x7fb1e50fe6a0] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x4fe26) [0x7fb1e52cae26] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x102116) [0x7fb1e537d116] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x10514c) [0x7fb1e538014c] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x105ff5) [0x7fb1e5380ff5] -> /usr/lib/dovecot/libdovec ot-storage.so.0(+0x101d14) [0x7fb1e537cd14] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_keyword_indexes+0x6b) [0x7fb1e535027b] -> /usr/lib/dovecot/libdovecot-storage.so.0(inde x_mail_get_keywords+0x6d) [0x7fb1e53502fd] -> /usr/lib/dovecot/modules/lib20_mail_log_plugin.so(+0x2ef9) [0x7fb1e4ba4ef9] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(notify_contexts_m ail_copy+0x5f) [0x7fb1e4cbd50f] -> /usr/lib/dovecot/modules/lib15_notify_plugin.so(+0x24f8) [0x7fb1e4cbe4f8] -> /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xf863) [0x7fb1e4eab863] -> /usr /lib/dovecot/libdovecot-storage.so.0(+0x6508f) [0x7fb1e52e008f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_move+0x5e) [0x7fb1e52e024e] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x13ef8) [0x55766c74aef8] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](command_exec+0xa4) [0x55766c7595b4] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x20 52f) [0x55766c75752f] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x205da) [0x55766c7575da] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](+0x208ed) [0x55766c7578ed] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](client_handle_input+0x1b5) [0x55766c757ab5] -> dovecot/imap [user.name 46.125.249.68 UID MOVE](client_input+0x70) [0x55766c758020] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7fb1e51c2609] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x132) [0x7fb1e51c3cf2] -> /usr/lib/dovecot/libdov ecot.so.0(io_loop_handler_run+0x50) [0x7fb1e51c26b0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7fb1e51c2870] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f b1e51348e3] Feb 24 01:36:26 mail dovecot[699699]: imap(user.name)<711331><0D3Ch9guy6UufflE>: Fatal: master: service(imap): child 711331 killed with signal 6 (core dumped) I run this # dpkg -l|grep dovecot ii dovecot-core 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - LDAP support ii dovecot-lmtpd 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - LMTP server ii dovecot-lucene 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - Lucene support ii dovecot-managesieved 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-pop3d 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - Sieve filters support ii dovecot-solr 2:2.3.21.1-2+debian11 amd64 secure POP3/IMAP server - Solr support on debian bookworm. The client, the user uses is maybe apples mail-app on ios... but I'm not sure. And i don't know, what he is doing. Can not interpret this message. Best regards Jakob

1 0

User authentication for shared mailbox
by sveyret＠gmail.com 23 Feb '25

23 Feb '25

Hi, I’m using Dovecot 2.3.21.1. I have mailboxes for the family members and some shared mailboxes, all of them available with IMAP protocol. Users are authenticating using PAM, and shared mailboxes appear as sub-folders of user accounts. Because it is easier to use with some clients, I’m looking for a way to use the shared mailboxes as independent accounts. This would mean that, on a client, I would like to create an account to access to `family@mydomain`, but using my own username and password. I thought of a way to do this by tricking the password, setting it, for example, to `myname+mysecretpassword`, then split it in dovecot configuration in order to override the username and password. But not only didn’t I found a way to split the string, but also, if I understand correctly, setting another user to PAM module will override the name of the mailbox I want to open. What would you suggest me to do in order to get this desired behavior? Thank you.

2 2

Mail locations must use the same hierarchy separator
by Mike 21 Feb '25

21 Feb '25

Hello, First post, and yes Ive searched the archives and didn't find an answer. Sorry if this is old hat but... I am trying build a new mailserver (iredmail) and import messages from the old server (old old iredmail), and convert from dbox to maildir in the process. I have previously used doveadm sync successfully several years/versions ago with a master user and imapc:. Now however, Im getting errors that don't make sense to me. doveadm -D -c /etc/dovecot/dovecot.conf sync -1 -R -u example(a)example.com imapc: results in: dsync(example(a)example.com): Info: imapc(mail.example.com:993): Connected to 192.0.2.1:993 (local 192.0.2.1:51732) dsync(example(a)example.com): Error: Mail locations must use the same hierarchy separator (specify namespace prefix="" { separator } explicitly) I have tried all sorts of chicanery including testing every combination of "" and / and . for each of prefix and separator in dovecot.conf, no dice. I am refraining from providing full debug dump/config files since this seems excessive if this is a config file issue, but will do so upon your advice if requested. Thank you. Hello, First post, and yes Ive searched the archives and didn't find an answer. Sorry if this is old hat but... I am trying build a new mailserver (iredmail) and import messages from the old server (old old iredmail), and convert from dbox to maildir in the process. I have previously used doveadm sync successfully several years/versions ago with a master user and imapc:. Now however, Im getting errors that don't make sense to me. doveadm -D -c /etc/dovecot/dovecot.conf sync -1 -R -u example(a)example.com imapc: results in: dsync(example(a)example.com): Info: imapc(mail.example.com:993): Connected to 192.0.2.1:993 (local 192.0.2.1:51732) dsync(example(a)example.com): Error: Mail locations must use the same hierarchy separator (specify namespace prefix="" { separator } explicitly) I have tried all sorts of chicanery including testing every combination of "" and / and . for each of prefix and separator in dovecot.conf, no dice. I am refraining from providing full debug dump/config files since this seems excessive if this is a config file issue, but will do so upon your advice if requested. Thank you.

2 1

Unable to debug sieve
by Roberto Puzzanghera 20 Feb '25

20 Feb '25

I'm trying to enable sieve debug with no success on dovecot 4.0. I would like to know what it is doing when taking decisions if running a script or not and what it does when a script is executed These settings do not enable the trace sieve_trace_debug = yes sieve_trace_dir = /tmp (I also tried any other world writable dir and also ~/.sieve while testing trace for personal scripts) nor this one is enabling the debug log_debug = category=sieve sieve is working perfectly for personal but not for global scripts. Any hint appreciated. Thanks in advance, Roberto

1 0