- dovecot - dovecot.org

Input Buffer Full with OAuth login
by Brad Koehn 26 Mar '25

26 Mar '25

I’m running Dovecot 2.3.21.1 using Authentik for OAuth authentication. I’m using SOGo 5.12.0 as a UI, also with OAuth authentication. When SOGo connects to Dovecot and authenticates with OAuth, it fails and the following is logged: imap-login: Info: Disconnected: Input buffer full (no auth attempts in 0 secs): user=<>, rip=10.42.1.1, lip=10.42.1.196, TLS, session=<NZnp7zMxQuMKKgEB> My dovecot-oauth2.conf.ext looks like this: openid_configuration_url = https://auth.koehn.com/application/o/dovecot-oauth2/.well-known/openid-conf… introspection_url = https://auth.koehn.com/application/o/introspect/ introspection_mode = post client_id = [redacted] client_secret = [redacted] username_attribute = email debug = yes rawlog_dir = /tmp/oauth2 And my auth-oauth2.conf.ext looks like this: passdb { driver = oauth2 mechanisms = xoauth2 oauthbearer args = /etc/dovecot/conf.d/dovecot-oauth2.conf.ext } I’m using the Dovecot Debian packages from repo.dovecot.org. I’ve tried auth for introspection_mode, to no avail. There’s nothing extra in the logs when I turn on debug, and there’s nothing logged in the /tmp/oauth2 directory either, FWIW. Any ideas? — Brad I’m running Dovecot 2.3.21.1 using Authentik for OAuth authentication. I’m using SOGo 5.12.0 as a UI, also with OAuth authentication. When SOGo connects to Dovecot and authenticates with OAuth, it fails and the following is logged: imap-login: Info: Disconnected: Input buffer full (no auth attempts in 0 secs): user=<>, rip=10.42.1.1, lip=10.42.1.196, TLS, session=<NZnp7zMxQuMKKgEB> My dovecot-oauth2.conf.ext looks like this: openid_configuration_url = https://auth.koehn.com/application/o/dovecot- oauth2/.well-known/openid-configuration introspection_url = https://auth.koehn.com/application/o/introspect/ introspection_mode = post client_id = [redacted] client_secret = [redacted] username_attribute = email debug = yes rawlog_dir = /tmp/oauth2 And my auth-oauth2.conf.ext looks like this: passdb { driver = oauth2 mechanisms = xoauth2 oauthbearer args = /etc/dovecot/conf.d/dovecot-oauth2.conf.ext } I’m using the Dovecot Debian packages from repo.dovecot.org. I’ve tried auth for introspection_mode, to no avail. There’s nothing extra in the logs when I turn on debug, and there’s nothing logged in the /tmp/ oauth2 directory either, FWIW. Any ideas? — Brad

3 3

Dovecot and IP check at the user connection (auth-worker problems: no IP...)
by ik7xja＠gmail.com 26 Mar '25

26 Mar '25

Hi to all, I'm using Postfix and Dovecot for my little server. I'm experimenting many false user caming fron the entire world to access to my account. I'm only in a country and I would like to restrict accesso to user coming from IPs located in my country. Since the access is granteg by mysql and SQL in passdb and userdb, I've created a table with only the IPs of my country and check the user remote IP. The trick is working well when I try to access to my account beacuse the variable "%r" is not empy... But... But when there is a delivery of a new message, the auth-worker have no IP and the check fail: auth-worker<5>: sql(user(a)my.domain): unknown user and the new message, coming in my box from other servers come back to the sender as "unknown user" There is a way to user a different query in this auth-worker process (I guess is using the same SQL with the IP-check)? Or "force" an IP (like 127.0.0.1) in the auth-worker invocation? Thanks in advance for any advice.

1 1

Indexer-worker panic and killed with signal 6 in 2.4 and Solr 9
by Zakaria 26 Mar '25

26 Mar '25

Hi there, I'm reporting what I think is a bug. I just configured dovecot 2.4 with fts_solr plugin running on solr 9.8 release and it throws this panic and sigfaults one after another. Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website): Panic: settings_get() - event has no SETTINGS_EVENT_ROOT Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website): Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x39) [0x7f2fe692e549] -> libdovecot.so.0(backtrace_get+0x22) [0x7f2fe692e682] -> libdovecot.so.0(+0x13ccbc) [0x7f2fe693ccbc] -> libdovecot.so.0(+0x13cd51) [0x7f2fe693cd51] -> libdovecot.so.0(+0x6bfff) [0x7f2fe686bfff] -> libdovecot.so.0(+0x5ed08) [0x7f2fe685ed08] -> libdovecot.so.0(+0xba555) [0x7f2fe68ba555] -> libdovecot.so.0(settings_get+0x46) [0x7f2fe68bb576] -> libdovecot.so.0(ssl_client_settings_get+0x66) [0x7f2fe69196e6] -> libdovecot.so.0(http_client_init_ssl_ctx+0xa9) [0x7f2fe68d40a9] -> libdovecot.so.0(http_client_host_submit_request+0x9d) [0x7f2fe68d37dd] -> libdovecot.so.0(http_client_request_submit+0x34) [0x7f2fe68c70c4] -> libdovecot.so.0(+0xc7cf0) [0x7f2fe68c7cf0] -> libdovecot.so.0(http_client_request_send_payload+0x2e) [0x7f2fe68c7d3e] -> lib21_fts_solr_plugin.so(solr_connection_post_more+0x39) [0x7f2fe6e3af89] -> lib21_fts_solr_plugin.so(+0x4469) [0x7f2fe6e38469] -> lib20_fts_plugin.so(fts_backend_update_build_more+0x4a) [0x7f2fe6e5930a] -> lib20_fts_plugin.so(+0xa419) [0x7f2fe6e5a419] -> lib20_fts_plugin.so(+0xae8a) [0x7f2fe6e5ae8a] -> lib20_fts_plugin.so(fts_build_mail+0x57) [0x7f2fe6e5b827] -> lib20_fts_plugin.so(+0x119e1) [0x7f2fe6e619e1] -> libdovecot-storage.so.0(mail_precache+0x2c) [0x7f2fe6cd6b1c] -> indexer-worker(+0x3b8a) [0x559c6212fb8a] -> indexer-worker(+0x44b5) [0x559c621304b5] -> indexer-worker(+0x466b) [0x559c6213066b] -> libdovecot.so.0(connection_input_default+0x199) [0x7f2fe6933439] -> libdovecot.so.0(io_loop_call_io+0x67) [0x7f2fe69534d7] -> libdovecot.so.0(io_loop_handler_run_internal+0x12a) [0x7f2fe6954c0a] -> libdovecot.so.0(io_loop_handler_run+0x50) [0x7f2fe6953580] -> libdovecot.so.0(io_loop_run+0x48) [0x7f2fe6953758] Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website): Fatal: master: service(indexer-worker): child 28216 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Mar 24 11:59:13 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 11:59:13 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 29469 Done find . -name "$name" -print0 Mar 24 11:59:13 server dovecot: decode2text: Error: 29470 Done(123) | xargs -0 cat Mar 24 11:59:13 server dovecot: decode2text: Error: 29471 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32540 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32541 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32542 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32555 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32556 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32557 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:49 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:49 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32832 Done find . -name "$name" -print0 Mar 24 12:00:49 server dovecot: decode2text: Error: 32833 Done(123) | xargs -0 cat Mar 24 12:00:49 server dovecot: decode2text: Error: 32834 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:52 server dovecot: imap-login: Login aborted: Connection closed (disconnected during TLS handshake) (tls_handshake_not_finished): user=, rip=20.65.195.124, lip=77.68.117.221, TLS handshaking: Connection closed, session= Mar 24 12:00:53 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:53 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 32955 Done find . -name "$name" -print0 Mar 24 12:00:53 server dovecot: decode2text: Error: 32956 Done(123) | xargs -0 cat Mar 24 12:00:53 server dovecot: decode2text: Error: 32957 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:57 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:57 server dovecot: decode2text: Error: /usr/libexec/dovecot/decode2text.sh: line 59: 33039 Done find . -name "$name" -print0 Mar 24 12:00:57 server dovecot: decode2text: Error: 33040 Done(123) | xargs -0 cat Mar 24 12:00:57 server dovecot: decode2text: Error: 33041 Segmentation fault | $libexec_dir/xml2text These are my relevant fts configuration:- mail_plugins = mail_compress fts fts_solr fts_autoindex = yes fts solr { url = SOLR_URL batch_size = 1000 } fts_decoder_driver = script fts_decoder_script_socket_path = decode2text service indexer-worker { vsz_limit = 4G } service decode2text { executable = script /usr/libexec/dovecot/decode2text.sh user = dovecot unix_listener decode2text { mode = 0666 } } language "en" { default = yes } I think anyone can reproduce the panic using following commands while targeting a mailbox which contains as many emails as possible maybe 20K. Commit and optimise dovecot core. /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/update?commit=true" /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/update?optimize=true" Rescan and index the mailbox. doveadm fts rescan -u hi(a)zakaria.website doveadm index -u hi(a)zakaria.website -q "*" I tested this on dovecot released solrconfig.xml for solr 9. Note, current solr 9 has breaking changes to the config, I rectified using the following, please refer to https://solr.apache.org/guide/solr/latest/upgrade-notes/major-changes-in-so…. Appending n solr deployment configuration following two lines:- SOLR_OPTS="$SOLR_OPTS -Dsolr.config.lib.enabled=true" SOLR_MODULES=extraction,ltr,analysis-extras Also, additional note there are some other minor log warning, but weren't problematic. With thanks. Zak. [https://api.zakaria.website/users/hi@zakaria.website/ f6ebf9ed031e93b5ed35f78ceb338278(a)zakaria.website/30db6adddb640dbc14bfad.png] Hi there, I'm reporting what I think is a bug. I just configured dovecot 2.4 with fts_solr plugin running on solr 9.8 release and it throws this panic and sigfaults one after another. Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website)<28216>: Panic: settings_get() - event has no SETTINGS_EVENT_ROOT Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website)<28216>: Error: Raw backtrace: libdovecot.so.0(backtrace_append+0x39) [0x7f2fe692e549] - > libdovecot.so.0(backtrace_get+0x22) [0x7f2fe692e682] -> libdovecot.so.0 (+0x13ccbc) [0x7f2fe693ccbc] -> libdovecot.so.0(+0x13cd51) [0x7f2fe693cd51] - > libdovecot.so.0(+0x6bfff) [0x7f2fe686bfff] -> libdovecot.so.0(+0x5ed08) [0x7f2fe685ed08] -> libdovecot.so.0(+0xba555) [0x7f2fe68ba555] - > libdovecot.so.0(settings_get+0x46) [0x7f2fe68bb576] -> libdovecot.so.0 (ssl_client_settings_get+0x66) [0x7f2fe69196e6] -> libdovecot.so.0 (http_client_init_ssl_ctx+0xa9) [0x7f2fe68d40a9] -> libdovecot.so.0 (http_client_host_submit_request+0x9d) [0x7f2fe68d37dd] -> libdovecot.so.0 (http_client_request_submit+0x34) [0x7f2fe68c70c4] -> libdovecot.so.0(+0xc7cf0) [0x7f2fe68c7cf0] -> libdovecot.so.0(http_client_request_send_payload+0x2e) [0x7f2fe68c7d3e] -> lib21_fts_solr_plugin.so(solr_connection_post_more+0x39) [0x7f2fe6e3af89] -> lib21_fts_solr_plugin.so(+0x4469) [0x7f2fe6e38469] - > lib20_fts_plugin.so(fts_backend_update_build_more+0x4a) [0x7f2fe6e5930a] - > lib20_fts_plugin.so(+0xa419) [0x7f2fe6e5a419] -> lib20_fts_plugin.so(+0xae8a) [0x7f2fe6e5ae8a] -> lib20_fts_plugin.so(fts_build_mail+0x57) [0x7f2fe6e5b827] - > lib20_fts_plugin.so(+0x119e1) [0x7f2fe6e619e1] -> libdovecot-storage.so.0 (mail_precache+0x2c) [0x7f2fe6cd6b1c] -> indexer-worker(+0x3b8a) [0x559c6212fb8a] -> indexer-worker(+0x44b5) [0x559c621304b5] -> indexer-worker (+0x466b) [0x559c6213066b] -> libdovecot.so.0(connection_input_default+0x199) [0x7f2fe6933439] -> libdovecot.so.0(io_loop_call_io+0x67) [0x7f2fe69534d7] - > libdovecot.so.0(io_loop_handler_run_internal+0x12a) [0x7f2fe6954c0a] - > libdovecot.so.0(io_loop_handler_run+0x50) [0x7f2fe6953580] -> libdovecot.so.0 (io_loop_run+0x48) [0x7f2fe6953758] Mar 24 11:58:48 server dovecot: indexer-worker(hi(a)zakaria.website)<28216>: Fatal: master: service(indexer-worker): child 28216 killed with signal 6 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) Mar 24 11:59:13 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 11:59:13 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 29469 Done find . -name "$name" -print0 Mar 24 11:59:13 server dovecot: decode2text: Error: 29470 Done(123) | xargs - 0 cat Mar 24 11:59:13 server dovecot: decode2text: Error: 29471 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32540 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32541 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32542 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:40 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32555 Done find . -name "$name" -print0 Mar 24 12:00:40 server dovecot: decode2text: Error: 32556 | xargs -0 cat Mar 24 12:00:40 server dovecot: decode2text: Error: 32557 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:49 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:49 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32832 Done find . -name "$name" -print0 Mar 24 12:00:49 server dovecot: decode2text: Error: 32833 Done(123) | xargs - 0 cat Mar 24 12:00:49 server dovecot: decode2text: Error: 32834 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:52 server dovecot: imap-login: Login aborted: Connection closed (disconnected during TLS handshake) (tls_handshake_not_finished): user=<>, rip=20.65.195.124, lip=77.68.117.221, TLS handshaking: Connection closed, session= Mar 24 12:00:53 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:53 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 32955 Done find . -name "$name" -print0 Mar 24 12:00:53 server dovecot: decode2text: Error: 32956 Done(123) | xargs - 0 cat Mar 24 12:00:53 server dovecot: decode2text: Error: 32957 Segmentation fault | $libexec_dir/xml2text Mar 24 12:00:57 server dovecot: decode2text: Error: cat: write error: Broken pipe Mar 24 12:00:57 server dovecot: decode2text: Error: /usr/libexec/dovecot/ decode2text.sh: line 59: 33039 Done find . -name "$name" -print0 Mar 24 12:00:57 server dovecot: decode2text: Error: 33040 Done(123) | xargs - 0 cat Mar 24 12:00:57 server dovecot: decode2text: Error: 33041 Segmentation fault | $libexec_dir/xml2text These are my relevant fts configuration:- mail_plugins = mail_compress fts fts_solr fts_autoindex = yes fts solr { url = SOLR_URL batch_size = 1000 } fts_decoder_driver = script fts_decoder_script_socket_path = decode2text service indexer-worker { vsz_limit = 4G } service decode2text { executable = script /usr/libexec/dovecot/decode2text.sh user = dovecot unix_listener decode2text { mode = 0666 } } language "en" { default = yes } I think anyone can reproduce the panic using following commands while targeting a mailbox which contains as many emails as possible maybe 20K. Commit and optimise dovecot core. /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/update?commit=true" /opt/solr-9.8.1/bin/solr api --solr-url "..../solr/dovecot/ update?optimize=true" Rescan and index the mailbox. doveadm fts rescan -u hi(a)zakaria.website doveadm index -u hi(a)zakaria.website -q "*" I tested this on dovecot released solrconfig.xml for solr 9. Note, current solr 9 has breaking changes to the config, I rectified using the following, please refer to https://solr.apache.org/guide/solr/latest/upgrade- notes/major-changes-in-solr-9.html. Appending n solr deployment configuration following two lines:- SOLR_OPTS="$SOLR_OPTS -Dsolr.config.lib.enabled=true" SOLR_MODULES=extraction,ltr,analysis-extras Also, additional note there are some other minor log warning, but weren't problematic. With thanks. Zak.

2 2

Dovecot 2.4: Segfault for "doveadm proxy kick foo bar"
by Michael Goth 25 Mar '25

25 Mar '25

Hi! The following command segfaults on Dovecot 2.4: #> doveadm proxy kick foo bar Segmentation fault (core dumped) Giving only one user (doveadm proxy kick foo) works: #> doveadm proxy kick foo 0 connections kicked It does not matter if the users actually exist on the server (so the above command can be used verbatim). This used to work in Dovecot 2.3. I'm running Dovecot 2.4 on Ubuntu 24.04, installed from repo.dovecot.org. Regards, Michael

2 1

Re: lost emails - Opened mail because: snippet ?
by Michael Slusarz 24 Mar '25

24 Mar '25

> On 03/24/2025 9:41 AM MDT Arkadiusz Miśkiewicz via dovecot <dovecot(a)dovecot.org> wrote: > > Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail > not cached, highest cached seq=20 uid=31: reset_id=1742577355) > > "Opened mail because: snippet " - what does this mean? It is reading the mail to create the preview text, which is then stored in the indexes. michael

2 1

lost emails - Opened mail because: snippet ?
by Arkadiusz Miśkiewicz 24 Mar '25

24 Mar '25

Hello. I'm tracking a weird case where dovecot (it's 2.3.21.1) looses incoming emails. Email is delivered over LMTP with full success (in theory). From lmtp raw log: 1742822341.735762 250 2.0.0 <examplelogin@mbox> +LpAG8Vb4Wc9OAAA9fPEKQ Saved 1742822341.735918 221 2.0.0 Bye Log says it got saved: Mar 24 14:19:01 mbox dovecot[22785]: lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, msgid=<XYZ...1611.EURP189.PROD.OUTLOOK.COM>, storage_id=1742822341.M462393P14397.mbox,S=139039,W=141006, delivery_status=saved mail to INBOX There is a file name but # find /var/mail/examplelogin/ -name '1742822341.M462393P14397.mbox*' # nothing. Well, someone could delete or move this email, right? But no, that's not the case, only pop3 sessions around: > Mar 24 14:18:43 mbox dovecot[22785]: pop3(examplelogin): pid=<24041> session=<rX98cRYxIvlTDCet>, Disconnected: Logged out top=0/0, retr=0/0, del=0/20, size=5204114, in=24, out=1002 > Mar 24 14:19:01 mbox dovecot[22785]: lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, msgid=<XYZ...1611.EURP189.PROD.OUTLOOK.COM>, storage_id=1742822341.M462393P14397.mbox,S=139039,W=141006, delivery_status=saved mail to INBOX > Mar 24 14:19:43 mbox dovecot[22785]: pop3-login: Login: user=<examplelogin>, method=PLAIN, rip=1.1.1.1, rport=63799, lip=2.2.2.2, lport=110, mpid=27238, session=<GPgZdRYxN/lTDCet> > Mar 24 14:19:44 mbox dovecot[22785]: pop3(examplelogin): pid=<27238> session=<GPgZdRYxN/lTDCet>, Disconnected: Logged out top=0/0, retr=0/0, del=0/20, size=5204114, in=24, out=1002 Note the same number of total mails in del log before and after problematic mail delivery - "del=0/20", so dovecot doesn't see that new mail (there are few pop3 logins after that - all with del=0/20) So the conclusion is that the file, with email, was not created on the filesystem. LMTP raw session log, debug session log, nothing weird - below. BUT there is one thing: Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail not cached, highest cached seq=20 uid=31: reset_id=1742577355) "Opened mail because: snippet " - what does this mean? Out of 50k mails delivered only 160 have that "Opened mail because: snippet" and by that I mean that logged for lmtp like: Mar 24 07:25:18 lmtp(xyz): pid=<28535> session=<SPx6Ds764Gd3bwAA9fPEKQ>, Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail not cached, highest cached seq=291 uid=4094: reset_id=1579231568) The rest have "UID 0: Opened mail because: mail stream". Started looking at these snipped entries. It seems that almost every mail with this logged is missing on the filesystem(!). Huh, what could be happening here? debug log (is there a way to enable even more detailed/low level log?): > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: auth-master: userdb lookup(examplelogin@mbox): Started userdb lookup > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: auth-master: userdb lookup(examplelogin@mbox): auth USER input: examplelogin home=/var/mail/examplelogin/ mail=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin uid=1234 gid=7890 sieve_enabled=no > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: auth-master: userdb lookup(examplelogin@mbox): Finished userdb lookup (username=examplelogin home=/var/mail/examplelogin/ mail=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin uid=1234 gid=7890 sieve_enabled=no) > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: changed username to examplelogin > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: lmtp-server: conn unix:pid=25252,uid=8 [89]: rcpt examplelogin@mbox: Added userdb setting: mail=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin > Mar 24 14:19:01 lmtp(examplelogin@mbox): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: lmtp-server: conn unix:pid=25252,uid=8 [89]: rcpt examplelogin@mbox: Added userdb setting: plugin/sieve_enabled=no > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Effective uid=1234, gid=7890, home=/var/mail/examplelogin/ > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Calkowita przestrzen dla serwera backend=fs args=group > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Calkowita przestrzen dla serwera bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Twoja przestrzen e-mail backend=fs args=user > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Twoja przestrzen e-mail bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: maildir++: root=/var/mail/examplelogin, index=/var/lib/dovecot/control/examplelogin, indexpvt=, control=/var/lib/dovecot/control/examplelogin, inbox=/var/mail/examplelogin, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota add mailbox dir = /var/mail/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota block device = /dev/mapper/vg_sys-lv_home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount point = /home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount type = xfs > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: fts: Indexes disabled for namespace '' > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota2_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: User session is finished > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Effective uid=1234, gid=7890, home=/var/mail/examplelogin/ > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Calkowita przestrzen dla serwera backend=fs args=group > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Calkowita przestrzen dla serwera bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota root: name=Twoja przestrzen e-mail backend=fs args=user > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Quota grace: root=Twoja przestrzen e-mail bytes=0 (10%) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace inbox: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/mail/examplelogin/:CONTROL=/var/lib/dovecot/control/examplelogin:VOLATILEDIR=/var/lib/dovecot/control/examplelogin:INDEX=/var/lib/dovecot/control/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: maildir++: root=/var/mail/examplelogin, index=/var/lib/dovecot/control/examplelogin, indexpvt=, control=/var/lib/dovecot/control/examplelogin, inbox=/var/mail/examplelogin, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota add mailbox dir = /var/mail/examplelogin > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota block device = /dev/mapper/vg_sys-lv_home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount point = /home > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota-fs: fs quota mount type = xfs > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Namespace : type=private, prefix=, sep=, inbox=no, hidden=yes, list=no, subscriptions=no location=fail::LAYOUT=none > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: fts: Indexes disabled for namespace '' > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: quota: quota_over_flag check: quota2_over_script unset - skipping > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: duplicate db: Initialize > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: sieve: Pigeonhole version 0.5.21.1 (49005e73) initializing > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: sieve: Sieve is disabled for this user > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: duplicate db: Cleanup > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: Mailbox opened > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail not cached, highest cached seq=20 uid=31: reset_id=1742577355) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: Adding field hdr.Subject to cache for the first time (uid=0) > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: Mailbox INBOX: Mailbox opened > Mar 24 14:19:01 lmtp(examplelogin): pid=<14397> session=<+LpAG8Vb4Wc9OAAA9fPEKQ>, Debug: User session is finished ps. logins, uid, gid changed to example values -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

1 0

Cannot retrieve private key from LDAP
by luis.neapolis＠gmail.com 22 Mar '25

22 Mar '25

Hello, I have a problem setting the mail-crypt plugin using global keys. First of all I prepare keys: penssl ecparam -genkey -name secp521r1 | openssl pkey -aes-256-cbc -passout pass:foobar | base64 -w0 >ecprivkey.pem cat ecprivkey_b64.pem | openssl ec -pubout > ecpubkey.pem Now I would like to pass these values using the LDAP passdb. My conf is: userdb ldap { driver = ldap ldap_filter = ... ldap filter ... fields { ... other fields ... crypt_global_public_key_file = inline:%{ldap:pubkey_in_pem_base64} crypt_global_private_key/main/crypt_private_key_file=inline:%{ldap:key_in_pem_base64} crypt_global_private_key/main/private_key_password=foobar } } mail_plugins { mail_crypt = yes } crypt_global_private_key main { # create the filter, but leave its settings empty } when I receive an email I have: lmtp(127004): Fatal: Raw user initialization failed: mail_crypt_plugin: main: Couldn't parse private key : Unknown key format I want to let you know that if I give same keys, without base64 encoding, to configuration: crypt_global_private_key main { crypt_private_key_file= /path/to/key } and: userdb ldap { ..... fields { ... other fields ... # crypt_global_private_key/main/crypt_private_key_file=inline:%{ldap:key_in_pem_base64} ... other fields ... } } all works. If I try to retrieve values from LDAP all is ok with: doveadm user user@domain Any suggestion? Thank you.

1 0

dovecot 2.4 : quota config help
by ollie＠ik.me 20 Mar '25

20 Mar '25

Hello ! My dovecot config seems to work ok for managing email, using sieve filters or encrypting emails, but I can't figure out how to use the new quota config. I'm scratching my head over that one since last week and I don't see where I have done a mistake. The quota is properly reported in sql, but when I cross the percentage limit that is supposed to trigger the quota-warning, nothing happens. And I can see that too in the logs compared to my previous 2.3 install where lmtp-server was doing its job to check the quota and trigger the warning. I'm sure that I've forgotten something quite stupid, but at that point I'm not sure if I ever will be able to spot it (and I'm also wondering if that could be a bug... in that case I could scratch my head forever without any hope of finding what's wrong). I'd post my dovecot config if some of you feel like helping, but there are so many posts with configs that do not have answer that I'm wondering if it's useful. So, should I post it or not ?

1 2

Dovecot 2.4.0 local_name wildcard matching regression
by Julius Kriukas 19 Mar '25

19 Mar '25

Hi, Using a wildcard host name in the `local_name` filter no longer works in Dovecot 2.4.0. This is useful for wildcard certificates. Example `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 "*.example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } local_name "example.com" { ssl_server_cert_file = /etc/dovecot/example.com.cert ssl_server_key_file = /etc/dovecot/example.com.key } ``` The configuration is tested with: ``` openssl s_client -connect mail.example.com:993 openssl s_client -connect example.com:993 ``` The first connection to mail.example.com fails because Dovecot uses the default `global.cert` file. The second test with the exact host name match works as expected. Dovecot uses the `example.com.cert` file. Similar to the previously reported multiple hosts on the same line discrepancy, it seems that the `doveconf` tool still has the wildcard matching support: ``` # 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 } ``` Is there a new way to achieve the wildcard matching behaviour of the local_name filter in Dovecot 2.4.0? Thanks. -- Julius Kriukas

3 3

LDAP quota is ignored
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded from dovecot 2.3.x to 2.4.0. I converted the configuration files and all is ok, but there is this strange thing about quota. I have quota limit from LDAP: quota_storage_size = %{ldap:quota}G Value is correctly retrieved from LDAP, with "doveadm user user@domain": quota_storage_size 10G In configuration files of dovecot I have nothing about quota definitions. If I check in webmail I have undefined value. If I set manually in configuration files: quota "User quota" { storage_size = 1G } quota is correctly shown in webmail, but only with this default value. It appears it ignores values from ldap userdb. How can I debug this? Thanks.

2 2

USERDB/LDAP fails if attribute doesn't exist
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded to 2.4 dovecot version from 2.3.x. I converted the configurations and now I have the following problem: I have a userdb with LDAP: userdb ldap { driver = ldap ldap_filter = (&(objectClass=Emails) (mail=%{user}) ) fields { quota_rule = %{ldap:quota} quota_over_status_current = %{ldap:quota_over} ....... and so on } } As, not all the users have quota_over set in ldap, quota_over doesn't always exist. With 2.3 version there was no problem even if it doesn't exist. Now I have the following error and userdb reports failed: dovecot dovecot[107831]: auth(user@domain): Debug: ldap: result: [..... others attributes .....] quota_over missing dovecot dovecot[107831]: auth(user@domain): Error: ldap: auth_userdb_post settings: Failed to parse configuration: Failed to expand userdb_fields/quota_over_status_current setting variables: No such LDAP attribute 'quota_over' dovecot dovecot[107831]: auth(user@domain): Debug: ldap: Finished userdb lookup dovecot dovecot[107831]: auth: Debug: userdb out: FAIL#0111 I tried to add a default value: quota_over_status_current = %{ldap:quota_over:TRUE} but it seems that it supposes that the name of the attribute is quota_over:TRUE and fails. Any suggestions? Thank you.

2 3

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 18 Mar '25

18 Mar '25

Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any dove command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use any dove command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf. dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } I get this output below from the command line and I have this diagnostic attached. Hopefully that can help someone help me. # 2.4.0 (daeb6bc59c): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) doveconf: Error: managesieve-login: dump-capability process killed with signal 11 zsh: segmentation fault /usr/local/Cellar/dovecot/2.4.0/bin/doveconf Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel

1 0

USERDB/LDAP fails if attribute doesn't exist
by luis.neapolis＠gmail.com 18 Mar '25

18 Mar '25

Hello, I have just upgraded to 2.4 dovecot version from 2.3.x. I converted the configurations and now I have the following problem: I have a userdb with LDAP: userdb ldap { driver = ldap ldap_filter = (&(objectClass=Emails) (mail=%{user}) ) fields { quota_rule = %{ldap:quota} quota_over_status_current = %{ldap:quota_over} ....... and so on } } As, not all the users have quota_over set in ldap, quota_over doesn't always exist. With 2.3 version there was no problem even if it doesn't exist. Now I have the following error and userdb reports failed: dovecot dovecot[107831]: auth(user@domain): Debug: ldap: result: [..... others attributes .....] quota_over missing dovecot dovecot[107831]: auth(user@domain): Error: ldap: auth_userdb_post settings: Failed to parse configuration: Failed to expand userdb_fields/quota_over_status_current setting variables: No such LDAP attribute 'quota_over' dovecot dovecot[107831]: auth(user@domain): Debug: ldap: Finished userdb lookup dovecot dovecot[107831]: auth: Debug: userdb out: FAIL#0111 I tried to add a default value: quota_over_status_current = %{ldap:quota_over:TRUE} but it seems that it supposes that the name of the attribute is quota_over:TRUE and fails. Any suggestions? Thank you.

1 0

Help: Configuration example conversion from 2.3 to 2.4 ?
by ollie＠ik.me 17 Mar '25

17 Mar '25

Hello ! Like many people who are posting here, I'm a bit in "trouble" to convert my actual v2.3 config that is perfectly functional to the new v2.4 I've read the doc, searched on this list and everywhere I could find something among search engine results, and I still can't figure out how to solve my problem. The lack of examples right now is probably what is blocking me, so.. can anyone here with sharp knowledge of v2.4 configuration "translate" this official v2.3 example into a working v2.4 example ? ( ref: https://doc.dovecot.org/2.3/configuration_manual/quota/quota_dict/ ) Server-based Dictionaries -------------------------------------- plugin { # SQL backend: quota = dict:User quota::proxy::sqlquota # Redis backend (v2.1.9+): quota = dict:User quota::redis:host=127.0.0.1:prefix=user/ quota_rule = *:storage=10M:messages=1000 } dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } ============================ Example dovecot-dict-sql.conf.ext: -------------------------------------------------- connect = host=localhost dbname=mails user=sqluser password=sqlpass map { pattern = priv/quota/storage table = quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = username value_field = messages } Thanks a million times to whoever can do that ! :) Lon.

2 2

RFC header to plain address(es)
by Jochen Bern 14 Mar '25

14 Mar '25

This has got to be one of the most stupid questions I've ever asked online ... I have a need of a "helper function" that takes a string someone would "want to send an e-mail to", i.e., something like an RFC 5322 "address" token, as used in a "To:" header, and extract just the actual e-mail address(es) from it. (The capability to deal with lists of *several* recipients is likely optional.) I found a certain number of *libraries* for various programming languages that offer such a functionality¹, but I would prefer an executable from some run-of-the-mill Linux/UNIX package to be called by shell command. Considering that pretty much every MTA and MUA must contain such functionality (to construct an SMTP envelope for a mail to be sent), and then some (I looked into, e.g., procmail), I'm surprised that apparently none of them *expose* it. (I seem to remember that the original "sendmail -bt" came somewhat close at least ...) Does anyone have an idea what tool I could (ab)use for that purpose? ¹ Namely: -- parseaddr() for python https://documentation.help/Python-PEP/module-email.Utils.html -- maildrop for C https://www.courier-mta.org/maildrop/rfc822.html -- mail_parser for Rust https://docs.rs/mail-parser/latest/mail_parser/ -- address-rfc2822 for JavaScript https://www.npmjs.com/package/address-rfc2822 -- mailparse-rfc822-parse-addresses for PHP https://www.php.net/manual/en/function.mailparse-rfc822-parse-addresses.php -- mail-header-parse-address for LISP https://www.gnu.org/software/emacs/manual/html_node/emacs-mime/Interface-Fu… -- and I suppose you could try to stuff the syntax definition into some parser code generator, too https://www.rfc-editor.org/rfc/rfc5322#section-3.4 Thanks in advance, -- Jochen Bern Systemingenieur Binect GmbH

2 1

Build error without ldap support
by Lafiel 14 Mar '25

14 Mar '25

Hi. Cannot build Dovecot without LDAP support. Configure flags: --with-ldap=no Error: In file included from db-ldap-settings.c:9: ../../src/lib-ldap/ldap-settings-parse.h:4:10: fatal error: ldap.h: No such file or directory 4 | #include <ldap.h> | ^~~~~~~~ compilation terminated. make[3]: *** [Makefile:2138: auth-db-ldap-settings.o] Error 1 Dovecot version: 2.4.0 -- Best regards, Lafiel mailto:lafiel@elven.pw

3 4

Instructions for upgrading to a newer version returns 404
by Jose Celestino 14 Mar '25

14 Mar '25

Hi, https://doc.dovecot.org/2.4.0/installation/upgrading.html returns a 404. Best regards, José Celestino

3 2

2.3 -> 2.4 segmentation fault
by Emmanuel Bardet 13 Mar '25

13 Mar '25

Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use the doveadm command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf if anyone can help 🙏 dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel Hello there, First, thanks for the terrific job you're doing. Dovecot rocks! I installed some time ago Dovecot on my macbook with Homebrew, that was Dovecot v2.3.18. I recently upgraded everything I installed with Homebrew to the latest which brought Dovecot to v2.4.0. I then modified my dovecot.conf file to make it work with this latest version but now, I constantly get a segmentation fault when I use the doveadm command : zsh: segmentation fault doveadm Also, while it looks like Dovecot is listening at the specified port, my email client cannot connect anymore complaining the server refused the connection. tcp4 0 0 127.0.0.1.10143 *.* LISTEN 662 PID TTY TIME CMD 662 ?? 0:06.66 /usr/local/sbin/dovecot -F Here is my 2.4 conf if anyone can help 🙏 dovecot_config_version = 2.4.0 log_path = /var/log/dovecot # mail_debug = yes default_vsz_limit = 0 default_internal_user = _dovecot default_login_user = _dovenull default_internal_group = mail mail_home=/var/mail/%{user} mail_path=sdbox:~/Mail ## this is sometimes needed # first_valid_uid = 500 last_valid_gid = 100 # if you want to use system users passdb pam { driver = pam } userdb passwd-file { driver = passwd-file # args = blocking=no # override_fields = uid=214 gid=vmail } protocols imap { } service imap-login { inet_listener imap { # address = 127.0.0.1 port = 10143 } } ssl=no # ssl_cert=</path/to/cert.pem # ssl_key=</path/to/key.pem # if you are using v2.3.0-v2.3.2.1 (or want to support non-ECC DH algorithms) # since v2.3.3 this setting has been made optional. #ssl_dh=</path/to/dh.pem namespace inbox { inbox = yes separator = / } Thanks a lot. Emmanuel PS : If I’m using the wrong mailing list, please point me to the right channel

1 0

Bug: Logout counters reset after recreating hibernated process
by Eirik Rye 12 Mar '25

12 Mar '25

Hello, # dovecot --version 2.3.20 (80a5ac675d) When using hibernation (`imap_hibernate_timeout = 10s`), counters such as deleted/expunged messages, appear to be reset after the user process is recreated. Steps to reproduce: 1. Configure IMAP hibernation 2. Login with IMAP client 3. Delete+expunge a message 4. IDLE, and wait 10s for process to be hibernated 5. Unhibernate process (`DONE`), and log out 6. Observe the logged line: 2023-09-05T17:36:26+0200 imap(<redacted>)<776933><jA2nYJ4EPdcqAVtAAADwAAutur4AAAAB>: Info: Disconnected: Logged out in=9 out=88 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 The expected output is "deleted=1 expunged=1", not "deleted=0 expunged=0". If you follow the steps above, but skip the IDLE/hibernate step, the output is as expected. Interestingly, if the client is disconnected during hibernation (without recreating the process), the output from `imap-hibernate` is still as expected: 2023-09-05T17:45:15+0200 imap-hibernate(<redacted>)<770540><0qE0gJ4Emt8qAVtAAADwAAutur4AAAAB>: Info: Disconnected: Connection closed in=97 out=1020 deleted=1 expunged=1 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 This leads me to believe the counters are lost during process recreation, not during hibernation. This is an issue as customers will often come to us asking why messages have disappeared in their inbox, or asking for help to identify which client is expunging messages. Right now, this information is lost if hibernation is used and the client is hibernated after expunging. Best regards, Eirik Rye

2 2

SELinux blocking dovecot from writing to passwd.db
by jcalvert＠crystal3.com 11 Mar '25

11 Mar '25

Greetings, I'm running dovecot 2.3.21.1 (Plesk says up-to-date) on AlmaLinux 8.10, Plesk Obsidian 18.0.67 #3. I'm getting this repeated error in /var/log/messages... "SELinux is preventing /usr/libexec/dovecot/auth from write access on the file passwd.db." (I think passwd.db is the one in /var/lib/plesk/mail/auth/) This causes... "Activating via systemd: service name='org.fedoraproject.Setroubleshootd'" which is taking a lot of CPU. This error is happening continuously, about 1-3 times per minute. Am I correct in thinking that an email client or webmail client is trying to change an email account password via IMAP? If so, I would like to know how to disable this ability in dovecot. (I would like to change email account passwords only via Plesk.) If not, why is dovecot trying to write to the passwd.db file? The fact that SELinux is blocking this is concerning. thanks, JC

4 8

How to configure director
by akshay＠deeproot.in 11 Mar '25

11 Mar '25

Hi, I am testing instance with 1 director and 2 nodes. followed instructions in https://doc.dovecot.org/2.3/configuration_manual/director_settings/ but the authentication happens within the director server. Director does not forward connections to configured mail servers. LDAP is my user backend. How do i configure director ? Following is my director configuration # Director.conf director_servers = 10.22.13.164 director_mail_servers = 10.22.13.11 10.22.13.244 director_user_expire = 15 min service director { user = dovecot group = dovecot unix_listener login/director { mode = 0666 user = dovecot group = dovecot } fifo_listener login/proxy-notify { mode = 0666 } unix_listener director-userdb { mode = 0600 } inet_listener { port = 9090 } unix_listener director-admin { mode = 0666 } } service imap-login { executable = imap-login director #executable = director imap-login user = dovecot group = dovecot } service pop3-login { #executable = pop3-director } service submission-login { #executable = submission-login director } protocol lmtp { auth_socket_path = director-userdb } #### Thanks, Akshay

2 2

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

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

dovecot Panic
by Jakob 24 Feb '25

24 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

autoexpunge
by Doug Hardie 20 Feb '25

20 Feb '25

I have the following in 15-mailboxes.config: mailbox Trash { special_use = \Trash autoexpunge = 30 days } I thought that would empty the deleted emails after 30 days. However, I find that in .Deleted Messages/cur there are over 18K messages dating back to the 90's. What do I need to set to make the autoexpunge work? -- Doug

6 9

iOS Mail.app Network error POSIX 54: is there a workaround?
by Gerben Wierda 19 Feb '25

19 Feb '25

I understand that this error that appears on iOS 18 devices is an iOS bug. Is this indeed the case and is there anything I can do about it on th server side as a workaround? Thanks, Gerben

1 0

Preventing message deletion
by dovecot＠iotti.biz 19 Feb '25

19 Feb '25

Hi all How may I disable message deletions via IMAP for some or all of my users? I read on the net that a possible solution would be to use the ACL IMAP plugin. But the examples I found were not so clear to me. We do not use shared mailboxes or namespaces. Only simple virtual users, each with it's own private mailbox. I would like to use the global acl file both for administration simplicity and because as I understood, global acl enrties take preference over any user setting. In the ACL page example there is a line: * user=foo lrw But in the comment it tells that doing so, every user' mailbox would be shared with the foo user, with the lrw permissions. Which is not what I would want. I don't need to share anything, just to restrict what the user, foo here, can do on his mailbox. Thank you, Luigi

2 4

IMAP dovecot\postgres low authentication performance
by Anatoliy Zhestov 19 Feb '25

19 Feb '25

Hi. We have a performance problem with imap authentication through postgresql. Our servers(modoboa based) have a big amount of permanent imap connections(5000-50000). Current performance is about 3000 successful authentications per hour. No visible reasons for such low speed. Accordingly, after a network failure or server restart, all clients try to reconnect, but restoring the connection pool takes hours and even tens of hours. Judging by the logs after the restart, a huge number of auth requests closed by timeout after 70-90 seconds. The postgresql database is not overloaded at the restore connections process and the postgresql connection pool (100) does not overflow. Manually started sql auth queries work fast, tables have indexes. So I guess there is a bottleneck somewhere in dovecot auth service or postgresql driver. I couldn't find any settings in the documentation that are directly responsible for regulating the number of connections to PostgreSQL from the auth service or performance of the driver. Is there any way to manage this? Does it make sense to use pgbouncer in front of the base? What else can be a bottleneck in our configuration and how to regulate the number of possible simultaneous authentications via PostgreSQL? I would be happy for any advice on how to increase the performance to at least 100 authentications per second. Thanks in advance for your help. Anatoliy Zhestov. ---------------- configs of server with 48 core, 184 gb mem --------------- dovecot 2.3.16 # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.15.0-126-generic x86_64 Ubuntu 22.04.5 LTS # Hostname: imap.ourcompany.net auth_cache_negative_ttl = 0 auth_cache_size = 20 M auth_cache_ttl = 3 hours auth_master_user_separator = * auth_mechanisms = plain login default_client_limit = 131072 default_process_limit = 131072 dict { quota = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } mail_location = maildir:~/Maildir mail_plugins = quota managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mai lbox date index ihave duplicate mime foreverypart extracttext editheader imapflags notify vnd.dovecot.pipe vnd.dovecot.execute namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { quota = dict:User quota::proxy::quota sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_execute_socket_dir = . sieve_extensions = +notify +imapflags +editheader +body +vnd.dovecot.execute +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-execute sieve_pipe_socket_dir = . sieve_plugins = sieve_extprograms } protocols = " imap lmtp sieve" service anvil { client_limit = 393219 } service auth { client_limit = 524288 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-radicale { group = radicale mode = 0666 user = radicale } unix_listener auth-userdb { user = vmail } } service config { vsz_limit = 1 G } service dict { unix_listener dict { mode = 0600 user = vmail } } service imap { executable = imap postlogin process_limit = 131072 vsz_limit = 1 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } vsz_limit = 512 M } service pop3 { executable = pop3 postlogin } service postlogin { executable = script-login /usr/local/bin/postlogin.sh service_count = 1000 process_min_avail = 5 user = modoboa } service send-to-click-frontapp1 { executable = script /usr/lib/dovecot/sieve-execute/clickhouse_log_frontapp1.sh unix_listener send-to-click-frontapp1 { group = vmail mode = 0666 user = vmail } user = dovenull vsz_limit = 2 G } service send-to-click { executable = script /usr/lib/dovecot/sieve-execute/clickhouse_log.sh unix_listener send-to-click { group = vmail mode = 0666 user = vmail } user = dovenull vsz_limit = 2 G } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } vsz_limit = 2 G } ssl_cert = </etc/letsencrypt/live/imap.ourcompany.net/fullchain.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4 ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1 stats_writer_socket_path = userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)imap.ourcompany.net } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota imap_quota } /etc/dovecot/dovecot-sql-master.conf.ex driver = pgsql connect = host=127.0.0.1 port=5432 dbname=modoboa user=modoboa password=XXXXXXXXXXXXXXXXX password_query = SELECT email AS user, password FROM core_user WHERE email='%u' and is_active and master_user /etc/dovecot/dovecot-sql.conf.ext driver = pgsql connect = host=127.0.0.1 port=5432 dbname=modoboa user=modoboa password=XXXXXXXXXXXXXXXXX user_query = SELECT '/srv/vmail/%d/%n' AS home, 1003 as uid, 1003 as gid, '*:bytes=' || mb.quota || 'M' AS quota_rule FROM admin_mailbox mb INNER JOIN admin_domain dom ON mb.domain_id=dom.id INNER JOIN core_user u ON u.id=mb.user_id WHERE (mb.is_send_only IS NOT TRUE OR '%s' NOT IN ('imap', 'pop3', 'lmtp')) AND mb.address='%n' AND dom.name='%d' password_query = SELECT email AS user, password, '/srv/vmail/%d/%n' AS userdb_home, 1003 AS userdb_uid, 1003 AS userdb_gid, CONCAT('*:bytes=', mb.quota, 'M') AS userdb_quota_rule FROM core_user u INNER JOIN admin_mailbox mb ON u.id=mb.user_id INNER JOIN admin_domain dom ON mb.domain_id=dom.id WHERE (mb.is_send_only IS NOT TRUE OR '%s' NOT IN ('imap', 'pop3')) AND email='%u' AND is_active AND dom.enabled iterate_query = SELECT email AS user FROM core_user /usr/local/bin/postlogin.sh #!/bin/sh PATH="/usr/bin:/usr/local/bin:/bin" psql -c "UPDATE core_user SET last_login=now() WHERE username='$USER'" > /dev/null exec "$@" /usr/lib/dovecot/sieve-execute/clickhouse_log_frontapp1.sh #!/bin/bash cd /tmp logger -i -t SIEVE_TEST "$1,$2,$3,$4" clickhouse-client -h XXXXXXXXXXXXXXXXX -d default -u some_user --password XXXXXXXXXXXXXXXXX \ --param_origin_from="$1" \ --param_origin_to="$2" \ --param_message_id="$3" \ --param_forward="$4" \ -q "INSERT INTO frontapp1_redirects (origin_from_email,origin_to_email,message_id,forward_email) VALUES ({origin_from:String},{origin_to:String},{message_id:String},{forward:String})" /usr/lib/dovecot/sieve-execute/clickhouse_log.sh #!/bin/bash cd /tmp logger -i -t SIEVE_TEST "$1,$2,$3,$4" clickhouse-client -h XXXXXXXXXXXXXXXXX -d default -u some_user --password XXXXXXXXXXXXXXXXX \ --param_origin_from="$1" \ --param_origin_to="$2" \ --param_message_id="$3" \ --param_forward="$4" \ -q "INSERT INTO frontapp_redirects (origin_from_email,origin_to_email,message_id,forward_email) VALUES ({origin_from:String},{origin_to:String},{message_id:String},{forward:String})"

6 30

auth_userdb_iterate
by Luigi Trovato 19 Feb '25

19 Feb '25

Hello, I have a doubt: is the lua function "auth_userdb_iterate" expected to always return the whole list of users no matter what, or it should evaluate if a specific virtual domain is provided as req argument and only list the users in that specific domain? And should the returned user list be in the format "username(a)domain.tld" or "username" ? -- Ciao, Luigi

1 1

lua API and returning reason and CONTACTADMIN
by Arkadiusz Miśkiewicz 19 Feb '25

19 Feb '25

Hello. Trying to pass reason response via lua by passing it at dovecot.auth.PASSDB_RESULT_USER_DISABLED like: function auth_password_verify(request, password) return dovecot.auth.PASSDB_RESULT_USER_DISABLED, "reason=custom_message" end function auth_userdb_lookup(request) return dovecot.auth.PASSDB_RESULT_OK, "uid=428671 gid=9726 home=/var/mail/existusertest" end function script_init() return 0 end function script_deinit() end Unfortunately returned result contains no custom message and also returns AUTHENTICATIONFAILED instead of CONTACTADMIN: NO [AUTHENTICATIONFAILED] Authentication failed. while I would expect something like: NO [CONTACTADMIN] custom_message: Any reason for such behaviour and how to get reason passed and proper CONTACTADMIN? Tests done on 2.3.21.1. passdb { driver = lua mechanisms = login plain args = file=/etc/dovecot/lua_auth_script_test_fail.lua blocking=yes } userdb { driver = lua args = file=/etc/dovecot/lua_auth_script_test_fail.lua blocking=yes } -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )

2 6

Can someone explain this to me, please?
by Ken Wright 19 Feb '25

19 Feb '25

The last time I checked my mail.log I found the following line: 2025-02-18T22:41:31.175798-05:00 grace dovecot: imap-login: Login aborted: Connection closed (auth failed, 1 attempts in 8 secs) (auth_failed): user=<wizard(a)koalatyworks.com>, method=PLAIN, rip=192.168.1.1, lip=192.168.1.10, TLS, session=<wTMBiHYu5pXAqAEB> Is this a password error or something more? Ken

2 1

Doveadm Backup
by Doug Hardie 18 Feb '25

18 Feb '25

I tried the backup again tonight. I am now getting a new error: mail# doveadm backup -f -u doug remote:checkout dsync-remote(doug)<1c8BDo4xtGe74wAA+dxtXQ>: Warning: Deleting mailbox 'INBOX': UID=92440 GUID=1465118975.V4eI7cfa32M232845.mail is missing locally dsync-remote(doug)<1c8BDo4xtGe74wAA+dxtXQ>: Error: Couldn't delete mailbox INBOX: INBOX can't be deleted. dsync-local(doug)<N0q9NI0xtGf4vgAAZU03Dg>: Error: Remote command returned error 65: ssh checkout doveadm dsync-server -udoug -U Anytime I run it now generates the same error messages. However on the backup machine the .cur directory is empty. I presume that is the INBOX referred to in the messages. All the other directories appear to be intact. -- Doug

2 3

2.4.0: managesieve: sieve_script_path setting variables: Unknown variable 'user'
by Bjoern Franke 18 Feb '25

18 Feb '25

Hi, I have the following (manage)sieve-related parts in my 2.4.0 config: within the namespace inbox: mailbox Junk { auto = subscribe autoexpunge = 14d sieve_script junk { type = before cause = copy driver = file path = /data/mail/sieve/report-spam.sieve } special_use { "\Junk" = yes } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { } sieve_script personal { active_path = /data/mail/%{user}/dovecot.sieve driver = file path = /data/mail/%{user}/sieve } Accessing via managesieve fails: Error: sieve: file storage: sieve_file_storage settings: Failed to parse configuration: Failed to expand sieve_script_path setting variables: Unknown variable 'user' But the sieve rules in general work. Regards Bjoern

2 2