- dovecot - dovecot.org

Missing IMAP METADATA Plugin
by Adam Miller 23 Aug '25

23 Aug '25

OS: Ubuntu 22.04.1 Dovecot: 2.3.16 (7e2e900c1a) When trying to enable the “imap_metadata” plugin, I get the following error: Plugin 'imap_metadata' not found from directory /usr/lib/dovecot/modules I have searched high and low via Google, StackOverflow and even ChatGPT (haha) but I cannot seem to find the package that provides the plugin. Does Dovecot have to be built from source for this plugin to be included? Any help is appreciated. Thank you!

8 8

getpwnam() failed: Resource temporarily unavailable
by Hauke Fath 22 Aug '25

22 Aug '25

Hi, I see a very peculiar Dovecot (2.3.21.1) authentication failure that concerns exactly one user: Aug 20 02:08:05 Bounce dovecot: auth-worker(13245): Debug: conn unix:auth-worker (pid=3029,uid=81): auth-worker<24>: Handling PASSV request Aug 20 02:08:05 Bounce dovecot: auth-worker(13245): Debug: conn unix:auth-worker (pid=3029,uid=81): auth-worker<24>: passwd(REDACTED_UID,84.136.89.217,<yZxQxMA8uL1UiFnZ>): Performing passdb lookup Aug 20 02:08:05 Bounce dovecot: auth-worker(13245): Debug: conn unix:auth-worker (pid=3029,uid=81): auth-worker<24>: passwd(REDACTED_UID,84.136.89.217,<yZxQxMA8uL1UiFnZ>): lookup Aug 20 02:08:05 Bounce dovecot: auth-worker(13245): Error: conn unix:auth-worker (pid=3029,uid=81): auth-worker<24>: passwd(REDACTED_UID,84.136.89.217,<yZxQxMA8uL1UiFnZ>): getpwnam() failed: Resource temporarily unavailable Aug 20 02:08:05 Bounce dovecot: auth-worker(13245): Debug: conn unix:auth-worker (pid=3029,uid=81): auth-worker<24>: passwd(REDACTED_UID,84.136.89.217,<yZxQxMA8uL1UiFnZ>): Finished passdb lookup Aug 20 02:08:05 Bounce dovecot: auth-worker(13245): Debug: conn unix:auth-worker (pid=3029,uid=81): auth-worker<24>: Finished: internal_failure This used to work, until a few months ago it stopped. The user can still authenticate to send mail through the same server. Changing the password didn't make a difference. Any ideas? Cheerio, Hauke -- The ASCII Ribbon Campaign Hauke Fath () No HTML/RTF in email Institut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344

3 3

How to remove non-existent virtual mailbox from index
by Ákos Szőts 21 Aug '25

21 Aug '25

Hi everyone, During experimentation I created a "Test1" mailbox under a virtual namespace: mailbox "Test1" { auto = no special_use = \All } I commented it out before restarting Dovecot, and it's never been subscribed to either. I see the Test1 directory is still within my "index" directory and there's a "dovecot.index.log" in it. When I try to force resync all my virtual mailboxes, doveadm complains about it: $ doveadm -D force-resync -A Virtual/* Debug: Namespace virtual-virtual: [...]/virtual/Test1 doesn't exist yet, using default permissions Debug: Namespace virtual-virtual: Using permissions from [...]/virtual: mode=0755 gid=default Error: Mailbox Virtual/Test1: mkdir_parents([...]/virtual/Virtual/Test1) failed: Permission denied Error: Mailbox Virtual/Test1: Failed to create path: [...]/virtual/Virtual/Test1 for mailbox Virtual/Test1: mkdir_parents([...]/virtual/Virtual/Test1) failed: Permission denied What is the proper command to remove it from the index? I tried "cache purge", but that fails, too. I can "rm -rf" the whole index directory and that solves this issue. However, I think there should be a more gentle solution. Thank you, Ákos

1 0

"imap-login" crashes at lib-ssl-iostream/iostream-ssl.c:55
by Ákos Szőts 21 Aug '25

21 Aug '25

Hi all, When I start "imap-login" without arguments, it crashes: gdb -ex run --args /usr/lib/dovecot/imap-login (gdb) thread apply all bt full Thread 1 (Thread 0x7f5bd50c6740 (LWP 625) "imap-login"): #0 0x00007f5bd545fe97in io_stream_ssl_global_init(set=0x56205ca355c8, error_r=0x7ffdf0e669a8) at ../lib-ssl-iostream/iostream-ssl.c:55 No locals. #1 0x00007f5bd558d15bin login_ssl_init() at /usr/src/debug/dovecot-2.4.1-4/src/login-common/main.c:343 ssl_set= 0x56205ca355c8 error= 0xc00000<error: Cannot access memory at address 0xc00000> #2 main_preinit() at /usr/src/debug/dovecot-2.4.1-4/src/login-common/main.c:355 max_fds= <optimized out> __func__= <optimized out> #3 login_binary_run(binary=<optimized out>, argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/dovecot-2.4.1-4/src/login-common/main.c:528 service_flags= <optimized out> login_socket= 0x7f5bd5590b66"login" error= 0x1000000<error: Cannot access memory at address 0x1000000> c= <optimized out> input= {config_path= 0x0, config_fd= 0, preserve_environment= false, preserve_user= false, preserve_home= false, no_service_filter= false, check_full_config= false, hide_obsol ete_warnings= false, no_protocol_filter= false, no_key_validation= false, reload_config= false, never_exec= false, always_exec= false, return_config_fd= false, use_sysexits= false, pr otocol= 0x562033d837ac"imap"} output= {specific_protocols= 0x56205ca15398, config_fd= -1, permission_denied= false} #4 0x00007f5bd51662aein __libc_start_call_main() from /lib64/libc.so.6 No symbol table info available. #5 0x00007f5bd5166379in __libc_start_main_impl() from /lib64/libc.so.6 No symbol table info available. #6 0x0000562033d79885in _start() at ../sysdeps/x86_64/start.S:115 No locals. Probably "ssl_vfuncs->[...]" is a NULL dereference? I'm debugging a crash within Dovecot and this was one of my findings. Dovecot version: 2.4.1. Ákos

1 1

dovecot RHEL 10 packages
by burnzerog＠gmail.com 19 Aug '25

19 Aug '25

Hi, I see only RHEL 8 and 9 packages but not for RHEL 10 in repo.dovecot.org. Do you think it can be released soon? Thank you.

3 2

quota_clone + dict_file_path wound up being somewhat cumbersome on 2.4
by Andy Baugh 19 Aug '25

19 Aug '25

The quota_clone syntax is rather cumbersome in comparison to 2.3 when using a flat file dictionary. I found I needed to make a "bogus" config block first: quota_clone { dict file { path = ${userdb:mail_path}/dovecot-quota } } Bogus, as the code path which actually deals with that doesn't have the ${userdb:*} vars available (visible by stracing the dovecot process, and seeing it fail to make /dovecotquota for obvious reasons). That said, if you don't include *some* value, it will explode even when you provide the *correct* value via userdb unless you initialize quota clone earlier there in the config. In this case for the 'luser' user: quota_clone/dict/file/path: /home/luser/mail/dovecot-quota wound up being the param I needed in order to get that logged in the right place for that specific user. None of how to format this properly was remotely clear to me from the documentation when looking at the quota_clone page: https://doc.dovecot.org/main/core/config/dict.html#flat-files As such I made an educated guess after reading the quota_clone code and testing a few things out. This actually works, so I'm happy with it for now. Not sure what this means RE the documentation, as even though it's not exactly obvious, I clearly was able to piece it together for the most part just by reading other documentation pages which mentioned things like separating namespaces by slashes, etc. I don't know how to properly convey "hey here's the list of where all these vars are actually able to be set and not set," as there's clearly some context there that's missing unless you go digging in the code. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV 713-384-8831 andy.baugh(a)webpros.com www.webpros.com

1 0

On Dovecot 2.4, auth-legacy setting for the auth service appears to be no-op when using lua passdb
by Andy Baugh 19 Aug '25

19 Aug '25

So, I used https://doc.dovecot.org/main/installation/upgrade/2.3-to-2.4.html#exim-auth… to ensure exim still worked. Unfortunately, that doesn't seem to be the case. Sender verification, auth, etc. *will* fail until you specifically start sending back those old params as well as the updated ones. I am using lua for the passdb/userdb however, so presumably it's just not documented that this is an "exercise for the reader" when using lua. In particular you need to deliver the 'mail' and 'quota' fields as they previously existed (colon separated) alongside the new dovecot params. Hope this helps someone else out there. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

2 2

'duplicate listener' on port 465
by William David Edwards 17 Aug '25

17 Aug '25

Hi, When configuring SMTPS as described on https://doc.dovecot.org/main/core/config/submission.html#smtps, Dovecot says there is a 'duplicate listener'. MRE: ``` root@dovecot24-test:/etc/dovecot/conf.d# doveconf -n # 2.4.1-4+debian12 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.1-4+debian12 (0a86619f) # OS: Linux 6.1.0-29-amd64 x86_64 Debian 12.11 # Hostname: dovecot24-test.cyberfusion.nl # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 dovecot_storage_version = 2.4.0 protocols = submission service submission-login { inet_listener submission_465 { port = 465 } } doveconf: Error: duplicate listener: 465:* doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: duplicate listener: 465:* ``` Can anyone help me understand why this listener would be 'duplicate'? This setup worked on 2.3.21.1. Thanks! William David Edwards

2 1

github: minimal dovecot 2.4 setup for testing in docker
by Rory Campbell-Lange 15 Aug '25

15 Aug '25

Hi Everyone I've made a simple dovecot.conf and accompanying users.db file suitable for running in Docker. At the moment this simply shows how to force the default domain using the "auth_default_domain" setting. I'm hoping this will be a helpful jumping off point if you need to upgrade your Dovecot config ... and want to test outside of production. Instructions and the minimal conf and db file are here: https://github.com/rorycl/dovecot-config Feel free to improve the setup by submitting a PR. If you'd like to add some other scenarios please also submit PRs. My suggested arrangement for that is in a directory named by feature, with a README.md, minimal conf file, support files (only if necessary) and log.txt showing the expected output. Cheers Rory

1 0

function 'dovecot_lua_notify_event_message_new' in my lua script when I use push_notification_lua_driver
by 3825634＠qq.com 14 Aug '25

14 Aug '25

I need to push a message notification to external system when they receive new emails from their mailbox，so I used the push_notification_lua plugin. My dovecot configuration file is as follows： plugin {     ....     push_notification_driver = dlog     push_notification_driver2 = lua:file=/etc/dovecot/custom-lua/push-notification.lua     push_lua_url = http://localhost:10421/internal/dovecot/email-notification/receive } protocol lda {     mail_plugins = $mail_plugins sieve last_login push_notification mail_lua push_notification_lua     .... } ============= I print the 'event' param's value log in function 'dovecot_lua_notify_event_message_new' in my lua script: function dovecot_lua_notify_event_message_new(ctx, event)   dovecot.i_info("lua-push: event=" .. cjson.encode(event)) end However, when I send a mail with multiple recivers, the notification event info seems to work abnormally. Sender: wangzx(a)hxtmailtest.avicnet.cn Receivers: zhaoqb(a)hxtmailtest.avicnet.cn , wangzx7110(a)hxtmailtest.avicnet.cn I found the two event object's field 'to_address' and 'to_display_name' value are same in /var/log/dovecot/lda.log. Please help me confirm if this is a bug? The log in /var/log/dovecot/lda.log like bellow: 2025-08-06T09:38:11.383536+08:00 hxtmailtest-server dovecot: lda(wangzx7110(a)hxtmailtest.avicnet.cn)<548522><EkAeFgOykmiqXggAfhwsfQ>: lua-push: event={"snippet":"test!!","date":1754444290,"keywords":{},"to_display_name":"Zhaoqb","uid":19,"subject":"test","from_display_name":"","to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","tz":480,"mailbox":"INBOX","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","from":"wangzx(a)hxtmailtest.avicnet.cn","message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>","uid_validity":1752827738,"flags":{},"from_address":"wangzx(a)hxtmailtest.avicnet.cn","name":"MessageNew"} 2025-08-06T09:38:11.423272+08:00 hxtmailtest-server dovecot: lda(zhaoqb(a)hxtmailtest.avicnet.cn)<548524><znZfFwOykmisXggAfhwsfQ>: lua-push: event={"subject":"test","mailbox":"INBOX","flags":{},"snippet":"test!!","from":"wangzx(a)hxtmailtest.avicnet.cn","date":1754444290,"from_address":"wangzx(a)hxtmailtest.avicnet.cn","keywords":{},"uid_validity":1752634929,"to_display_name":"Zhaoqb","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","name":"MessageNew","from_display_name":"","tz":480,"to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","uid":39,"message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>"} Thanks! 3825634(a)qq.com 3825634(a)qq.com I need to push a message notification to external system when they receive new emails from their mailbox**so I used the push_notification_lua plugin. My dovecot configuration file is as follows** plugin { .... push_notification_driver = dlog push_notification_driver2 = lua:file=/etc/dovecot/custom-lua/push-notification.lua push_lua_url = http://localhost:10421/internal/dovecot/email-notification/receive } protocol lda { mail_plugins = $mail_plugins sieve last_login push_notification mail_lua push_notification_lua .... } ============= I print the 'event' param's value log in function 'dovecot_lua_notify_event_message_new' in my lua script: function dovecot_lua_notify_event_message_new(ctx, event) dovecot.i_info("lua-push: event=" .. cjson.encode(event)) end However, when I send a mail with multiple recivers, the notification event info seems to work abnormally. Sender: wangzx(a)hxtmailtest.avicnet.cn Receivers: zhaoqb(a)hxtmailtest.avicnet.cn , wangzx7110(a)hxtmailtest.avicnet.cn I found the two event object's field 'to_address' and 'to_display_name' value are same in /var/log/dovecot/lda.log. Please help me confirm if this is a bug? The log in /var/log/dovecot/lda.log like bellow: 2025-08-06T09:38:11.383536+08:00 hxtmailtest-server dovecot: lda(wangzx7110(a)hxtmailtest.avicnet.cn)<548522><EkAeFgOykmiqXggAfhwsfQ>: lua-push: event={"snippet":"test!!","date":1754444290,"keywords":{},"to_display_name":"Zhaoqb","uid":19,"subject":"test","from_display_name":"","to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","tz":480,"mailbox":"INBOX","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","from":"wangzx(a)hxtmailtest.avicnet.cn","message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>","uid_validity":1752827738,"flags":{},"from_address":"wangzx(a)hxtmailtest.avicnet.cn","name":"MessageNew"} 2025-08-06T09:38:11.423272+08:00 hxtmailtest-server dovecot: lda(zhaoqb(a)hxtmailtest.avicnet.cn)<548524><znZfFwOykmisXggAfhwsfQ>: lua-push: event={"subject":"test","mailbox":"INBOX","flags":{},"snippet":"test!!","from":"wangzx(a)hxtmailtest.avicnet.cn","date":1754444290,"from_address":"wangzx(a)hxtmailtest.avicnet.cn","keywords":{},"uid_validity":1752634929,"to_display_name":"Zhaoqb","to":"Zhaoqb <zhaoqb(a)hxtmailtest.avicnet.cn>, Wangzx7110\n <wangzx7110(a)hxtmailtest.avicnet.cn>","name":"MessageNew","from_display_name":"","tz":480,"to_address":"zhaoqb(a)hxtmailtest.avicnet.cn","uid":39,"message_id":"<6e3a1265476c8197372afb7a1ac5ebbb(a)hxtmailtest.avicnet.cn>"} Thanks! [1][IMG] [2]3825634(a)qq.com 3825634(a)qq.com References Visible links 1. https://wx.mail.qq.com/home/index?t=readmail_businesscard_midpage&nocheck=t… 2. https://wx.mail.qq.com/home/index?t=readmail_businesscard_midpage&nocheck=t…

2 4

Re: Fw: upgrade mail paths (Debian 1:2.4.1)
by Rory Campbell-Lange 12 Aug '25

12 Aug '25

On 12/08/25, Andy Baugh (andy.baugh(a)webpros.com) wrote: > Colon separated vars need to be exploded into different params, sadly. This gets more complicated when dealing with things that are not mail opts. > > In your case you'll want to break down what used to be positional args thusly: > > mail_driver:mail_path:mail_inbox_path:mail_index_path > > Of course the "INBOX="/"INDEX=" part is assumed by the named param now, so can be left off the value. > > For example, with what used to be dsync or with quotas, things become rather painful to convert: ... Thank you very much for the confirmation, Andy. Exploding the configuration as you suggest works fine, although I had to quickly change my SQL table to suit. Fortunately I don't use quotas or dsync. I'm very grateful for your research into the configuration changes (which sound extensive) -- thanks again for sharing your insights. Let's hope the Debian stable upgrade doesn't cause too much pain. Best wishes, Rory

1 0

upgrade mail paths (Debian 1:2.4.1)
by rory＠campbell-lange.net 12 Aug '25

12 Aug '25

Dear Dovecot Users I guess there may be a storm of questions from users of Dovecot on Debian who are upgrading to the latest Debian stable, which uses Dovecot 1:2.4.1 [1] with the concomitant configuration changes. The issue I have encountered a problem translating my previous configuration for "mail_location" to "mail_path". The mail_location string returned from my database was mbox:/home/<user>/Mail/:INBOX=/var/mail/<user>:INDEX=/home/<domain>/Mailindexes/<user> Reading the mail location docs [2] I'm unclear if the colon separated configuration still works or if the configuration items should be separated into separate fields, presumably: mail_path mail_inbox_path mail_index_path Thanks for any insight. Regards, Rory [1] https://packages.debian.org/trixie/dovecot-core [2] https://doc.dovecot.org/main/core/config/mail_location.html

1 0

dovecot-sieve failed large mail
by Benoît PELISSIER 12 Aug '25

12 Aug '25

Hi, I noticed errors in the incoming emails with large attachments (>10MB). Its only with sieve filters enables. I use dovecot-lda and exim. Logs error : Error: program exec:/usr/sbin/sendmail (1295385): Execution timed out (> 30000 msecs) Error: program exec:/usr/sbin/sendmail (1295385): Failed to send SIGTERM signal to program Error: sieve: msgid=<**@**>: redirect action: failed to redirect message to <**@**>: Failed to execute sendmail (temporary failure) Error: sieve: Execution of script **/.dovecot.sieve was aborted due to temporary failure (user logfile **/.dovecot.sieve.log may reveal additional details) * i replaced private data by ** Regards, Benoît dovecot --version 2.3.13 (89f716dc2)

4 7

[Patch] Allow sieve redirects to specified domains only
by Kadlecsik József 10 Aug '25

10 Aug '25

Hello, The use case is simple: we have to forbid sieve redirects to outside, but should be able to redirect inside. The patch below adds a new sieve configuration option sieve_allowed_redirects to list the domains to which redirects are permitted and otherwise are not allowed. Please consider it. diff --git a/pigeonhole/doc/example-config/conf.d/90-sieve.conf b/pigeonhole/doc/example-config/conf.d/90-sieve.conf index 238bcf4..3b4ac65 100644 --- a/pigeonhole/doc/example-config/conf.d/90-sieve.conf +++ b/pigeonhole/doc/example-config/conf.d/90-sieve.conf @@ -126,6 +126,10 @@ plugin { # script execution. If set to 0, no redirect actions are allowed. #sieve_max_redirects = 4 + # The comma/space separated list of email domains where redirection is allowed. + # If the list is empty, there is no restriction. + sieve_allowed_redirects = + # The maximum number of personal Sieve scripts a single user can have. If set # to 0, no limit on the number of scripts is enforced. # (Currently only relevant for ManageSieve) diff --git a/pigeonhole/src/lib-sieve/cmd-redirect.c b/pigeonhole/src/lib-sieve/cmd-redirect.c index 6a3b0a4..17e9031 100644 --- a/pigeonhole/src/lib-sieve/cmd-redirect.c +++ b/pigeonhole/src/lib-sieve/cmd-redirect.c @@ -107,6 +107,24 @@ const struct sieve_action_def act_redirect = { .commit = act_redirect_commit, }; +static bool +cmd_redirect_allowed(struct sieve_instance *svinst, + const struct smtp_address *to_address) +{ + const char **domain; + bool result = TRUE; + + if (!svinst->allowed_redirects) + return TRUE; + for (domain = svinst->allowed_redirects; *domain != NULL; ++domain) { + if (strcasecmp(*domain, to_address->domain) == 0) { + return TRUE; + } + result = FALSE; + } + return result; +} + /* * Validation */ @@ -127,6 +145,12 @@ cmd_redirect_validate(struct sieve_validator *validator, if (!sieve_validator_argument_activate(validator, cmd, arg, FALSE)) return FALSE; + if (svinst->max_redirects == 0) { + sieve_command_validate_error(validator, cmd, + "local policy prohibits the use of a redirect action"); + return FALSE; + } + /* We can only assess the validity of the outgoing address when it is * a string literal. For runtime-generated strings this needs to be * done at runtime. @@ -148,14 +172,17 @@ cmd_redirect_validate(struct sieve_validator *validator, } } T_END; + if (!result && + !cmd_redirect_allowed(svinst, + sieve_address_parse_str(raw_address, &error))) { + sieve_command_validate_error(validator, cmd, + "local policy prohibits the use of a redirect action"); + return FALSE; + } + return result; } - if (svinst->max_redirects == 0) { - sieve_command_validate_error(validator, cmd, - "local policy prohibits the use of a redirect action"); - return FALSE; - } return TRUE; } @@ -238,6 +265,11 @@ cmd_redirect_operation_execute(const struct sieve_runtime_env *renv, "local policy prohibits the use of a redirect action"); return SIEVE_EXEC_FAILURE; } + if (!cmd_redirect_allowed(svinst, to_address)) { + sieve_runtime_error(renv, NULL, + "local policy prohibits the use of a redirect action"); + return SIEVE_EXEC_FAILURE; + } if (sieve_runtime_trace_active(renv, SIEVE_TRLVL_ACTIONS)) { sieve_runtime_trace(renv, 0, "redirect action"); diff --git a/pigeonhole/src/lib-sieve/sieve-common.h b/pigeonhole/src/lib-sieve/sieve-common.h index e79fb4d..d980c9d 100644 --- a/pigeonhole/src/lib-sieve/sieve-common.h +++ b/pigeonhole/src/lib-sieve/sieve-common.h @@ -209,6 +209,7 @@ struct sieve_instance { const struct smtp_address *user_email, *user_email_implicit; struct sieve_address_source redirect_from; unsigned int redirect_duplicate_period; + const char **allowed_redirects; }; /* diff --git a/pigeonhole/src/lib-sieve/sieve-settings.c b/pigeonhole/src/lib-sieve/sieve-settings.c index 47f70da..70addc7 100644 --- a/pigeonhole/src/lib-sieve/sieve-settings.c +++ b/pigeonhole/src/lib-sieve/sieve-settings.c @@ -267,4 +267,10 @@ void sieve_settings_load(struct sieve_instance *svinst) svinst->user_email = address; } } + svinst->allowed_redirects = NULL; + str_setting = sieve_setting_get(svinst, "sieve_allowed_redirects"); + if (str_setting != NULL && *str_setting != '\0') { + svinst->allowed_redirects = + (const char **)p_strsplit_spaces(svinst->pool, str_setting, ", "); + } } Best regards, Jozsef -- E-mail : kadlecsik.jozsef(a)wigner.hun-ren.hu PGP key: https://wigner.hu/~kadlec/pgp_public_key.txt Address: Wigner Research Centre for Physics H-1525 Budapest 114, POB. 49, Hungary

2 1

Empty "from:" on certain sieve rule
by Ciprian M. Vizitiu [FDT] 10 Aug '25

10 Aug '25

Hello everyone, Running a Dovecot 2.3.13 (Debian 11 native package) configured to deliver to Postfix lmtp and using dovecot-sieve. Setting-up a simple vacation responder works as expected but trying to catch a missing header e.g. if allof (not exists "X-GitLab-NotificationReason") { vacation :days 1 :addresses"SOME-NOTIFICATION(a)example.com" :subject "Message sent to an automated address " :from"some-sender(a)example.com" text: Hello, This is an automated reply to let you know thatSOME-NOTIFICATION(a)example.com is an automated address and is not read by a human operator. If you're trying to contact EXAMPLECOM please send your emails toexample(a)example.com . ; } ... will result in an empty "from:" field instead of the required "some-sender(a)example.com" e.g. Aug 06 09:41:45 email-001.example.com postfix/smtpd[1974551]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Aug 06 09:41:45 email-001.example.com dovecot[1174421]: lmtp(some-notification(a)email.example.com)<1974562><uTh/ITkHk2giIR4AdMz+wA>: sieve: msgid=<941c2ff0-56f1-493f-973e-871f446e060b(a)anotherexample.com>: vacation action: sent vacation response to <some.user(a)anotherexample.com> Aug 06 09:41:45 email-001.example.com postfix/pickup[1956559]: B7BF8207C9: uid=18018 from=<> Aug 06 09:41:45 email-001.example.com postfix/cleanup[1974554]: B7BF8207C9: message-id=<dovecot-sieve-1754466105-562992-0(a)email-001.example.com> Aug 06 09:41:45 email-001.example.com postfix/qmgr[1171599]: B7BF8207C9: from=<>, size=979, nrcpt=2 (queue active) Aug 06 09:41:45 email-001.example.com postfix/smtp[1974565]: B7BF8207C9: to=<some.user(a)anotherexample.com>, relay=smtpconnector.upper.relay[192.168.2.14]:25, delay=0.12, delays=0.06/0.01/0.03/0.02, dsn=5.7.1, status=bounced (host smtpconnector.upper.relay[192.168.2.14] said: 554 5.7.1 <>: Sender address rejected: Access denied (in reply to RCPT TO command)) I tried forcing sieve_user_email = some-sender(a)example.com ... but to no avail. I'm well aware that I could try and fix the problem at Postfix level but blindly catching ALL mails with an empty "from:" field feels bad: one miss-configured daemon and we spam everyone plus we already do some intricate rewriting. Any ideas? Hello everyone, Running a Dovecot 2.3.13 (Debian 11 native package) configured to deliver to Postfix lmtp and using dovecot-sieve. Setting-up a simple vacation responder works as expected but trying to catch a missing header e.g. if allof (not exists "X-GitLab-NotificationReason") { vacation :days 1 :addresses [1]"SOME-NOTIFICATION(a)example.com" :subject "Message sent to an automated address " :from [2]"some-sender(a)example.com" text: Hello, This is an automated reply to let you know that [3]SOME-NOTIFICATION(a)example.com is an automated address and is not read by a human operator. If you're trying to contact EXAMPLECOM please send your emails to [4]example(a)example.com . ; } ... will result in an empty "from:" field instead of the required [5]"some-sender(a)example.com" e.g. Aug 06 09:41:45 email-001.example.com postfix/smtpd[1974551]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5 Aug 06 09:41:45 email-001.example.com dovecot[1174421]: lmtp([6]some-notification(a)email.example.com)<1974562><uTh/ITkHk2giIR4AdMz+wA>: sieve: msgid=[7]<941c2ff0-56f1-493f-973e-871f446e060b(a)anotherexample.com>: vacation action: sent vacation response to [8]<some.user(a)anotherexample.com> Aug 06 09:41:45 email-001.example.com postfix/pickup[1956559]: B7BF8207C9: uid=18018 from=<> Aug 06 09:41:45 email-001.example.com postfix/cleanup[1974554]: B7BF8207C9: message-id=[9]<dovecot-sieve-1754466105-562992-0(a)email-001.example.com> Aug 06 09:41:45 email-001.example.com postfix/qmgr[1171599]: B7BF8207C9: from=<>, size=979, nrcpt=2 (queue active) Aug 06 09:41:45 email-001.example.com postfix/smtp[1974565]: B7BF8207C9: to=[10]<some.user(a)anotherexample.com>, relay=smtpconnector.upper.relay[192.168.2.14]:25, delay=0.12, delays=0.06/0.01/0.03/0.02, dsn=5.7.1, status=bounced (host smtpconnector.upper.relay[192.168.2.14] said: 554 5.7.1 <>: Sender address rejected: Access denied (in reply to RCPT TO command)) I tried forcing sieve_user_email = [11]some-sender(a)example.com ... but to no avail. I'm well aware that I could try and fix the problem at Postfix level but blindly catching ALL mails with an empty "from:" field feels bad: one miss-configured daemon and we spam everyone plus we already do some intricate rewriting. Any ideas? References Visible links 1. mailto:SOME-NOTIFICATION@example.com 2. mailto:some-sender@example.com 3. mailto:SOME-NOTIFICATION@example.com 4. mailto:example@example.com 5. mailto:some-sender@example.com 6. mailto:some-notification@email.example.com 7. mailto:941c2ff0-56f1-493f-973e-871f446e060b@anotherexample.com 8. mailto:some.user@anotherexample.com 9. mailto:dovecot-sieve-1754466105-562992-0@email-001.example.com 10. mailto:some.user@anotherexample.com 11. mailto:some-sender@example.com

2 1

Unable to specify home directory for mail_location
by jrmu＠ircnow.org 05 Aug '25

05 Aug '25

Greetings Dovecot team/users, I am trying to use Dovecot to serve Maildir files. The users' email is located in ~/Maildir (in each user's home directory). I tried specifying mail_location = maildir:~/Maildir but I get this error: Aug 4 00:06:34 ch dovecot: imap(username): Error: Relative home directory paths not supported: 0 Are relative home directory paths not supported? Here is the output of dovecot -n: # dovecot -n # 2.3.21.1 (d492236fa0): /etc/dovecot/dovecot.conf # OS: OpenBSD 7.7 amd64 # Hostname: ch.ircnow.org auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = sha1 first_valid_uid = 1000 listen = 104.244.78.185, 2605:6400:c8b7::1 mail_debug = yes mail_location = maildir:~/Maildir mbox_write_locks = fcntl mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = scheme=blf-crypt username_format=%u /etc/dovecot/passwd driver = passwd-file } ssl_cert = </etc/ssl/ch.ircnow.org.crt ssl_key = # hidden, use -P to show it userdb { args = username_format=%u /etc/dovecot/passwd default_fields = quota_rule=*:storage=1G driver = passwd-file } verbose_ssl = yes 1375 bytes received in 0.00 seconds (5.18 MB/s) -- Aaron Lin jrmu(a)ircnow.org IRCNow (https://ircnow.org)

3 5

Dovecot fails to "initialize SSL server context"
by jaap＠jbril.net 04 Aug '25

04 Aug '25

I am configuring a new mailserver. Postfix works and is getting configured according to our wishes. Dovecot is more stubborn: for some reason I'm not able to understand, it refuses to "initialize SSL server context". complaining that "Can't load SSl Certificate". I believe I have configured the same certificate (and accompanying key) for imap-login that I use for https. But dovecot does not agree. I looked at error:14187180. All I found were errors on the configuration for the Certs cq Keys which I think I am avoiding . Two questions: Please correct me if I'm wrong. Can you clarify dovecot's error message? Jaap Server: * Rocky Linux 9.6 kernel 5.14.0-570.28.1 * Dovecot 2.3.21.1 * Openssl 3.2.2 * Certbot 3.1.0 Https is functioning as expected: ssl-config: * Include /etc/letsencrypt/options-ssl-apache.conf * SSLCertificateFile /etc/letsencrypt/live/radicale.camelopardus.nl/fullchain.pem * SSLCertificateKeyFile /etc/letsencrypt/live/radicale.camelopardus.nl/privkey.pem * ssl_cert = </etc/letsencrypt/live/iris.camelopardus.nl/fullchain.pem test from client: openssl s_client -connect radicale.camelopardus.nl:https reply: *CONNECTED(00000003)* *depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1* *verify return:1* *depth=1 C = US, O = Let’s Encrypt, CN = E6* *verify return:1* *depth=0 CN = radicale.camelopardus.nl* *verify return:1* Dovecot responds differently (for Thunderbird as well as) for openssl: conf.d/10-ssl.conf: * ssl_cert = </etc/letsencrypt/live/radicale.camelopardus.nl/fullchain.pem * ssl_key = </etc/letsencrypt/live/radicale.camelopardus.nl/privkey.pem test: openssl s_client -connect radicale.camelopardus.nl:imaps reply: CONNECTED(00000003) write:errno=104 no peer certificate available For both there is the same error in dovecot's log: imap-login: Error: Failed to initialize SSL server context: Can't load SSL certificate (ssl_cert setting): error:14187180: SSL routines:ssl_do_config:bad value: section=system_default, cmd=Groups, arg=X25519:secp256r1:X448:secp521r1:secp384r1:ffdhe2048:ffdhe3072:ffdhe4096:ffdhe6144:ffdhe8192: user=<>, rip=2a10:3781:5ab:1:ff51:cbd1:4d54:fb7b, lip=2a10:3781:5ab:10::aaf,

4 4

migrate to virtual mailboxes before upgrading to 2.4
by roughnecks 04 Aug '25

04 Aug '25

Hello, I was thinking about, maybe, migrating my postfix/dovecot server to virtual mailboxes, before upgrading Debian to Trixie. So, atm, I have system users with ~/Maildir but it's not so convenient anymore. I am looking for some documentation/guide on how to migrate everything to virtual mailboxes. Of course I searched by myself, but didn't find many results. Thanks -- roughnecks

2 1

sieve script is not exescuted
by Kamil Jońca 30 Jul '25

30 Jul '25

I have scripts in 2 places: sieve_script personal { path = ~/.dovecot.sieve } sieve_script before { path = /etc/dovecot/sieve } /etc/dovecot/sieve is directory with (currently) one script. This script add header to message. And it seems, that "before" script is not executed. Any hints? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ "Linux: the operating system with a CLUE... Command Line User Environment". (seen in a posting in comp.software.testing)

6 11

doveadm force-resync crashes at list/mailbox-list-fs-iter.c:507
by Ákos Szőts 29 Jul '25

29 Jul '25

Hi All, In Dovecot 2.4.1 if I start doveadm force-resync with a non-existent mailbox that ends in a slash, the command crashes: gdb -ex run --args doveadm force-resync -A test/ Thread 1 (Thread 0x7f9e5cc4a980 (LWP 442) "doveadm"): #0 fs_list_next_root(ctx=ctx@entry=0x55d248df6898) at list/mailbox-list-fs-iter.c:507 roots= <error reading variable roots (Cannot access memory at address 0x0)> count= <error reading variable count (Cannot access memory at address 0x8)> __func__= "fs_list_next_root" #1 0x00007f9e5dc417c2in fs_list_iter_reset(ctx=0x55d248df6898) at list/mailbox-list-fs-iter.c:830 __func__= <optimized out> #2 fs_list_iter_next(_ctx=0x55d248df6898) at list/mailbox-list-fs-iter.c:912 ctx= <optimized out> ret= 0 __func__= "fs_list_iter_next" #3 0x00007f9e5dc4f8ddin mailbox_list_iter_next_call(ctx=0x55d248df6898) at list/mailbox-list-iter.c:1009 info= <optimized out> set= 0x148d86ee0 ret= <optimized out> #4 mailbox_list_iter_next(ctx=0x55d248df6898) at list/mailbox-list-iter.c:1098 _data_stack_cur_id= 5 info= <optimized out> #5 0x00007f9e5dc50899in mailbox_list_ns_iter_try_next(_ctx=0x55d248df6488, info_r=<synthetic pointer>) at list/mailbox-list-iter.c:616 ctx= 0x55d248df6488 ns= <optimized out> info= <optimized out> suffix= <optimized out> has_children= <optimized out> __func__= <optimized out> #6 mailbox_list_ns_iter_next(_ctx=0x55d248df6488) at list/mailbox-list-iter.c:678 info= 0x0 #7 0x00007f9e5dc4f8ddin mailbox_list_iter_next_call(ctx=0x55d248df6488) at list/mailbox-list-iter.c:1009 info= <optimized out> set= 0x2fffffffd0 ret= <optimized out> #8 mailbox_list_iter_next(ctx=0x55d248df6488) at list/mailbox-list-iter.c:1098 _data_stack_cur_id= 4 info= <optimized out> #9 0x000055d20bc81a20in cmd_force_resync_run(_ctx=0x55d248db57a8, user=0x55d248dc6318) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:369 ctx= 0x55d248db57a8 iter_flags= (MAILBOX_LIST_ITER_RAW_LIST| MAILBOX_LIST_ITER_NO_AUTO_BOXES| MAILBOX_LIST_ITER_STAR_WITHIN_NS| MAILBOX_LIST_ITER_RETURN_NO_FLAGS| MAILBOX_LIST_ITER_FORCE_RESYNC) ns_mask= (MAIL_NAMESPACE_TYPE_PRIVATE| MAIL_NAMESPACE_TYPE_SHARED| MAIL_NAMESPACE_TYPE_PUBLIC) iter= 0x55d248df6488 info= <optimized out> ret= <optimized out> patterns= {0x55d248db5300"test/", 0x0} #10 0x000055d20bc856c2in doveadm_mail_next_user(ctx=ctx@entry=0x55d248db57a8, error_r=error_r@entry=0x7ffdbc3f0778) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:506 _data_stack_cur_id= 3 cctx= 0x55d248db39b8 input= {event_parent= 0x0, service= 0x55d20bcbd810"doveadm", protocol= 0x0, username= 0x55d248db81a0"akos(a)szots.dev", session_id= 0x0, session_id_prefix= 0x0, session_create_ time= 0, local_ip= {family= 0, u= {ip6= {__in6_u= {__u6_addr8= '\000' <repeats 15 times>, __u6_addr16= {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32= {0, 0, 0, 0}}}, ip4= {s_addr= 0}}, sco pe_id= 0}, remote_ip= {family= 0, u= {ip6= {__in6_u= {__u6_addr8= '\000' <repeats 15 times>, __u6_addr16= {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32= {0, 0, 0, 0}}}, ip4= {s_addr= 0}}, scope_id= 0}, local_port= 0, remote_port= 0, local_name= 0x0, userdb_fields= 0x0, code_override_fields= 0x0, forward_fields= 0x0, set_instance= 0x0, flags_override_add= 0, flags_over ride_remove= 0, no_userdb_lookup= false, debug= false, end_client_tls_secured= false, autocreated= false, no_free_init_failure= false} error= 0x0 ip= <optimized out> ret= <optimized out> dropping_privs= true cur_uid= 0 cur_cwd= 0x55d248d86df8"/" cur_ctx= 0x55d248dc2c80 reason= 0x55d248df57f0 __func__= "doveadm_mail_next_user" #11 0x000055d20bc87525in doveadm_mail_all_users(ctx=0x55d248db57a8, wildcard_user=0x55d20bcc015d "*") at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:584 _data_stack_cur_id= 2 cctx= 0x55d248db39b8 user_idx= 0 ip= <optimized out> user= 0x55d248db81a0"akos(a)szots.dev" error= 0x55d248d8e7d8"\t\350\330H\322U" ret= 1 #12 doveadm_mail_cmd_exec(ctx=0x55d248db57a8, wildcard_user=0x55d20bcc015d "*") at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:721 cctx= <optimized out> cli= <optimized out> ret= <optimized out> error= 0x55d248d8e7d8"\t\350\330H\322U" #13 doveadm_cmd_ver2_to_mail_cmd_wrapper(cctx=<optimized out>) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:1039 mctx= 0x55d248db57a8 mail_cmd= {alloc= 0x55d20bc803f0<cmd_force_resync_alloc>, name= 0x55d20bcbe92d"force-resync", usage_args= 0x55d20bcc5008"[-u <user>|-A] [-S <socket_path>] [-f] <mailbox mask>"} wildcard_user= 0x55d20bcc015d"*" #14 0x000055d20bc9ba77in doveadm_cmdline_run(argc=<optimized out>, argv=0x55d248d8e7c8, cctx=cctx@entry=0x55d248db39b8) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-cmd-parse.c:451 prefix= <optimized out> pargv= {arr= {buffer= 0x55d248db4388, element_size= 112}, v= 0x55d248db4388, v_modifiable= 0x55d248db4388} pargc= 8 pool= 0x55d248db4350 ptr_count= <optimized out> ptr= <optimized out> ptr_end= <optimized out> ptr_last_non_kv= <optimized out> #15 0x000055d20bc9bc2cin doveadm_cmdline_try_run(cmd_name=cmd_name@entry=0x55d248d8e7f9 "force-resync", argc=<optimized out>, argv=<optimized out>, cctx=cctx@entry=0x55d248db39b8) at /usr/s rc/debug/dovecot-2.4.1-4/src/doveadm/doveadm-cmd.c:160 cmd= <optimized out> #16 0x000055d20bc74fdein main(argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm.c:386 service_flags= <optimized out> cmd_name= 0x55d248d8e7f9"force-resync" i= <optimized out> quick_init= false c= <optimized out> longopts= {{name= 0x7f9e5dadb7a8"help", has_arg= 0, flag= 0x0, val= 0}, {name= 0x0, has_arg= 0, flag= 0x0, val= 0}} help_requested= <optimized out> longopt= 0x0 cctx= 0x55d248db39b8 Ákos Hi All, In Dovecot 2.4.1 if I start doveadm force-resync with a non-existent mailbox that ends in a slash, the command crashes: gdb -ex run --args doveadm force-resync -A test/ Thread 1 (Thread 0x7f9e5cc4a980 (LWP 442) "doveadm"): #0 fs_list_next_root (ctx=ctx@entry=0x55d248df6898) at list/mailbox-list-fs-iter.c:507 roots = <error reading variable roots (Cannot access memory at address 0x0)> count = <error reading variable count (Cannot access memory at address 0x8)> __func__ = "fs_list_next_root" #1 0x00007f9e5dc417c2 in fs_list_iter_reset (ctx=0x55d248df6898) at list/mailbox-list-fs-iter.c:830 __func__ = <optimized out> #2 fs_list_iter_next (_ctx=0x55d248df6898) at list/mailbox-list-fs-iter.c:912 ctx = <optimized out> ret = 0 __func__ = "fs_list_iter_next" #3 0x00007f9e5dc4f8dd in mailbox_list_iter_next_call (ctx=0x55d248df6898) at list/mailbox-list-iter.c:1009 info = <optimized out> set = 0x148d86ee0 ret = <optimized out> #4 mailbox_list_iter_next (ctx=0x55d248df6898) at list/mailbox-list-iter.c:1098 _data_stack_cur_id = 5 info = <optimized out> #5 0x00007f9e5dc50899 in mailbox_list_ns_iter_try_next (_ctx=0x55d248df6488, info_r=<synthetic pointer>) at list/mailbox-list-iter.c:616 ctx = 0x55d248df6488 ns = <optimized out> info = <optimized out> suffix = <optimized out> has_children = <optimized out> __func__ = <optimized out> #6 mailbox_list_ns_iter_next (_ctx=0x55d248df6488) at list/mailbox-list-iter.c:678 info = 0x0 #7 0x00007f9e5dc4f8dd in mailbox_list_iter_next_call (ctx=0x55d248df6488) at list/mailbox-list-iter.c:1009 info = <optimized out> set = 0x2fffffffd0 ret = <optimized out> #8 mailbox_list_iter_next (ctx=0x55d248df6488) at list/mailbox-list-iter.c:1098 _data_stack_cur_id = 4 info = <optimized out> #9 0x000055d20bc81a20 in cmd_force_resync_run (_ctx=0x55d248db57a8, user=0x55d248dc6318) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:369 ctx = 0x55d248db57a8 iter_flags = (MAILBOX_LIST_ITER_RAW_LIST | MAILBOX_LIST_ITER_NO_AUTO_BOXES | MAILBOX_LIST_ITER_STAR_WITHIN_NS | MAILBOX_LIST_ITER_RETURN_NO_FLAGS | MAILBOX_LIST_ITER_FORCE_RESYNC) ns_mask = (MAIL_NAMESPACE_TYPE_PRIVATE | MAIL_NAMESPACE_TYPE_SHARED | MAIL_NAMESPACE_TYPE_PUBLIC) iter = 0x55d248df6488 info = <optimized out> ret = <optimized out> patterns = {0x55d248db5300 "test/", 0x0} #10 0x000055d20bc856c2 in doveadm_mail_next_user (ctx=ctx@entry=0x55d248db57a8, error_r=error_r@entry=0x7ffdbc3f0778) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:506 _data_stack_cur_id = 3 cctx = 0x55d248db39b8 input = {event_parent = 0x0, service = 0x55d20bcbd810 "doveadm", protocol = 0x0, username = 0x55d248db81a0 [1]"akos(a)szots.dev", session_id = 0x0, session_id_prefix = 0x0, session_create_ time = 0, local_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}, sco pe_id = 0}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}, scope_id = 0}, local_port = 0, remote_port = 0, local_name = 0x0, userdb_fields = 0x0, code_override_fields = 0x0, forward_fields = 0x0, set_instance = 0x0, flags_override_add = 0, flags_over ride_remove = 0, no_userdb_lookup = false, debug = false, end_client_tls_secured = false, autocreated = false, no_free_init_failure = false} error = 0x0 ip = <optimized out> ret = <optimized out> dropping_privs = true cur_uid = 0 cur_cwd = 0x55d248d86df8 "/" cur_ctx = 0x55d248dc2c80 reason = 0x55d248df57f0 __func__ = "doveadm_mail_next_user" #11 0x000055d20bc87525 in doveadm_mail_all_users (ctx=0x55d248db57a8, wildcard_user=0x55d20bcc015d "*") at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:584 _data_stack_cur_id = 2 cctx = 0x55d248db39b8 user_idx = 0 ip = <optimized out> user = 0x55d248db81a0 [2]"akos(a)szots.dev" error = 0x55d248d8e7d8 "\t\350\330H\322U" ret = 1 #12 doveadm_mail_cmd_exec (ctx=0x55d248db57a8, wildcard_user=0x55d20bcc015d "*") at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:721 cctx = <optimized out> cli = <optimized out> ret = <optimized out> error = 0x55d248d8e7d8 "\t\350\330H\322U" #13 doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-mail.c:1039 mctx = 0x55d248db57a8 mail_cmd = {alloc = 0x55d20bc803f0 <cmd_force_resync_alloc>, name = 0x55d20bcbe92d "force-resync", usage_args = 0x55d20bcc5008 "[-u <user>|-A] [-S <socket_path>] [-f] <mailbox mask>"} wildcard_user = 0x55d20bcc015d "*" #14 0x000055d20bc9ba77 in doveadm_cmdline_run (argc=<optimized out>, argv=0x55d248d8e7c8, cctx=cctx@entry=0x55d248db39b8) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm-cmd-parse.c:451 prefix = <optimized out> pargv = {arr = {buffer = 0x55d248db4388, element_size = 112}, v = 0x55d248db4388, v_modifiable = 0x55d248db4388} pargc = 8 pool = 0x55d248db4350 ptr_count = <optimized out> ptr = <optimized out> ptr_end = <optimized out> ptr_last_non_kv = <optimized out> #15 0x000055d20bc9bc2c in doveadm_cmdline_try_run (cmd_name=cmd_name@entry=0x55d248d8e7f9 "force-resync", argc=<optimized out>, argv=<optimized out>, cctx=cctx@entry=0x55d248db39b8) at /usr/s rc/debug/dovecot-2.4.1-4/src/doveadm/doveadm-cmd.c:160 cmd = <optimized out> #16 0x000055d20bc74fde in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/dovecot-2.4.1-4/src/doveadm/doveadm.c:386 service_flags = <optimized out> cmd_name = 0x55d248d8e7f9 "force-resync" i = <optimized out> quick_init = false c = <optimized out> longopts = {{name = 0x7f9e5dadb7a8 "help", has_arg = 0, flag = 0x0, val = 0}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} help_requested = <optimized out> longopt = 0x0 cctx = 0x55d248db39b8 Akos References Visible links 1. mailto:akos@szots.dev 2. mailto:akos@szots.dev

2 2

"lock/disable" user's mailbox
by roughnecks 29 Jul '25

29 Jul '25

Hello, not sure if relevant here, but I'm in need of disabling or locking down an user's mailbox, without completely removing the related system account. It would be nice if said account was not able to receive emails anymore, or "better", until it was re-enabled. Would also be cool if the sender received a warning back, upon the failed dispatch. Does that even make sense? :D I'm running postfix and dovecot on a debian bookworm VPS. Thanks -- roughnecks

2 2

When does dovecot use sendmail_path?
by Joseph Tam 29 Jul '25

29 Jul '25

I'm trying to plug up all the holes where local mail leaves our mail system without a DKIM signature. One avenue is bounce messages. I wrote a small sendmail wrapper to add DKIM signatures, and defined it as the value for dovecot's sendmail_path. I presume Dovecot invokes this executable when it has to send a send message. Under what circumstances does this happen? I tried to provoke a mailout by sending messages to recipients with full quotas and permission locked mailbox files, but could not generate any mail back. Joseph Tam <jtam.home(a)gmail.com>

2 2

'doveadm' error
by Andreas Kossack 28 Jul '25

28 Jul '25

Hi, are there anywhere recommendations or 'best practices' for compiling dovecot-2.4.x at IBMs AIX7.3? With some own patches i can compile it, but one unexpected result is # /usr/local/bin/doveadm mailbox list -u <user> /usr/local/bin/doveconf: invalid option -- u What's wrong? -- Mit freundlichen Grüßen / Best regards / Salutations / Cordialmente ___________________________________________________________________ Brandenburgische Technische Universität Cottbus – Senftenberg E Andreas.Kossack(a)B-TU.De

1 0

one-off doveadm commands broken in 2.4.1 when using docker
by jlh 28 Jul '25

28 Jul '25

Hi all In 2.3, I could use doveadm from the docker image as a standalone tool, but this no longer works in 2.4: $ docker run --rm -ti dovecot/dovecot:2.3-latest doveadm usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A] [-S <socket_path>] [-r] <search query> [...snip...] $ docker run --rm -ti dovecot/dovecot:latest-2.4 doveadm doveconf: Fatal: Cannot expand variable %{env:USER_PASSWORD This was useful for hashing passwords with "doveadm pw". I assume this wasn't an intentional change in how doveadm works. For now I'll just use the old image when hashing passwords. Thank you! Jean-Luc

2 1

siebe settings in 2.4.0
by Helmut K. C. Tessarek 23 Jul '25

23 Jul '25

I've been reading the docs and the migration docs for hours, but the sieve config is a mess. In 2.3.x I am using: plugin { sieve = ~/.sieve sieve_dir = ~/.sieve_storage } and this is how it looks in my home dir: $ ls -la .sie* lrwxrwxrwx 32 a b c d .sieve -> .sieve_storage/MailFilters.sieve .rw------- 0 a b c d .sieve.log .rw------- 17,414 a b c d 2025-07-08 03:00 .sieve.svbin So How do I do the same in 2.4.x? I've come so far as: sieve_script personal { driver = file } But then there are path, bin_path, active_path, name, and a bunch of other settings. Sorry to be a little bit frustrated, but my old settings are not out of the ordinary (2 freaking parameters), but there is no documentation on how to migrate these 2 very simple settings to the new format. The upgrade docs explain the new var expansion and a matrix with old and new parameters. But this info is completely missing for sieve. The doc only points to "script storage". Really? You couldn't have added these 2 parameters to the old-new matrix? I am not asking you to do this for every single sieve parameter, but at least for the 2 or 3 most used ones. Sorry for my rant, but I had to get it out there to not go insane. Cheers, K. C. -- regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944 Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944 /* Thou shalt not follow the NULL pointer for chaos and madness await thee at its end. */

4 6

discarded vacation reply to own address <xxxx> (as specified using :addresses argument)
by Marc 23 Jul '25

23 Jul '25

Did I configure this? Or is this default behaviour of dovecot? How can I turn this off if this is a standard config?

2 1

Re: Strange mailq errors
by Xavier Humbert 23 Jul '25

23 Jul '25

Le 22/07/2025 16:28, Odhiambo Washington a écrit : > > > On Tue, Jul 22, 2025 at 4:42 PM Xavier Humbert via dovecot > <dovecot(a)dovecot.org> wrote: > > Hi, > > I recently experienced strange errors in mailq : > > [root@numenor ~]# mailq > -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- > 56BF31C9391 2320 Fri Jul 18 03:42:33 info(a)quora.com > (temporary failure. Command output: lda(postfix): Error: > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission > denied) > postfix(a)groumpf.org > > All other messages are getting in without error. > Furthermore these are probably spam which shouldn't get in, since > postfix@ is not in the authorized recipients > > When it happens, it is always spam for postfix@ > > Any idea ? > > > Check your dovecot config for the permissions: Postfix user needs > access to /var/run/dovecot/stats-writer > > V2.4: > service stats { > unix_listener stats-writer { > mode = 0660 > user = ?? > } > } > > v2.3 > unix_listener stats-writer { > user = ?? > group = ?? > mode = 0660 > } > } > > > -- > Best regards, > Odhiambo WASHINGTON, > Nairobi,KE > +254 7 3200 0004/+254 7 2274 3223 > In an Internet failure case, the #1 suspect is a constant: DNS. > "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) > [How to ask smart questions: > http://www.catb.org/~esr/faqs/smart-questions.html] Here is the relevant part of dovecot config : service stats { unix_listener stats-reader { user = $default_internal_user group = $default_internal_user mode = 0660 } unix_listener stats-writer { user = $default_internal_user group = $default_internal_user mode = 0660 } } All other mails get in without problem. I suspect it gets in, then confuses the mail system because of proxy:unix:passwd.byname in postfix config local_recipient_maps I don't need this btw. Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr Le 22/07/2025 16:28, Odhiambo Washington a ecrit : On Tue, Jul 22, 2025 at 4:42PM Xavier Humbert via dovecot <[1]dovecot(a)dovecot.org> wrote: Hi, I recently experienced strange errors in mailq : [root@numenor ~]# mailq -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- 56BF31C9391 2320 Fri Jul 18 03:42:33 [2]info(a)quora.com (temporary failure. Command output: lda(postfix): Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied) [3]postfix(a)groumpf.org All other messages are getting in without error. Furthermore these are probably spam which shouldn't get in, since postfix@ is not in the authorized recipients When it happens, it is always spam for postfix@ Any idea ? Check your dovecot config for the permissions: Postfix user needs access to /var/run/dovecot/stats-writer V2.4: service stats { unix_listener stats-writer { mode = 0660 user = ?? } } v2.3 unix_listener stats-writer { user = ?? group = ?? mode = 0660 } } -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' -\_(Tu)_/- :-) [How to ask smart questions: [4]http://www.catb.org/~esr/faqs/smart-questions.html] Here is the relevant part of dovecot config : service stats { unix_listener stats-reader { user = $default_internal_user group = $default_internal_user mode = 0660 } unix_listener stats-writer { user = $default_internal_user group = $default_internal_user mode = 0660 } } All other mails get in without problem. I suspect it gets in, then confuses the mail system because of proxy:unix:passwd.byname in postfix config local_recipient_maps I don't need this btw. Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer [5]https://www.amdh.fr References Visible links 1. mailto:dovecot@dovecot.org 2. mailto:info@quora.com 3. mailto:postfix@groumpf.org 4. http://www.catb.org/~esr/faqs/smart-questions.html 5. https://www.amdh.fr/

2 1

Anyone have working examples of how one might go about *debugging* a userdb/passdb LUA script for authentication?
by Andy Baugh 22 Jul '25

22 Jul '25

Howdy, I've been working on upgrading the version cPanel ships to Dovecot 2.4. It appears that the "dict" driver for passdb/authdb has been removed per your documentation, with a recommendation to use a lua script instead. As such I've followed the online documentation to do so and wound up with a userdb/passdb section that looks like so: passdb cpauthd { driver = lua lua_file = /usr/local/cpanel/etc/dovecot/cpauthd.lua lua_settings { socket = /usr/local/cpanel/var/cpdoveauthd.sock } result_internalfail = continue result_failure = return-fail } userdb cpauthd { driver = lua lua_file = /usr/local/cpanel/etc/dovecot/cpauthd.lua } My prospective lua script only takes from the socket arg passed in and reads from the socket, delivering back the same kind of answer we would have previously got from the auth dict driver (converting password_key/user_key to auth_passdb/userdb_get_cache_key in script as appears to be suggested). Unfortunately, I'm thinking that this entire setup is being ignored, as when I do: doveadm -D -o auth_debug=yes auth lookup for a user I know to be valid on the system with the previous 2.3 setup, I don't even see any indication that the lua authentication database is even consulted. Jul 18 12:32:30 Debug: auth-master: passdb lookup(zippy(a)cptest.local): Started passdb lookup Jul 18 12:32:30 Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb: Connecting Jul 18 12:32:30 Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb (pid=800187,uid=0): Client connected (fd=9) Jul 18 12:32:30 Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb (pid=800187,uid=0): auth input: Jul 18 12:32:30 Error: auth-master: passdb lookup(zippy(a)cptest.local): Auth PASS lookup failed Jul 18 12:32:30 Debug: auth-master: passdb lookup(zippy(a)cptest.local): auth PASS input: Jul 18 12:32:30 Debug: auth-master: passdb lookup(zippy(a)cptest.local): Passdb lookup failed Jul 18 12:32:30 Error: cmd auth lookup: passdb lookup failed for zippy(a)cptest.local Jul 18 12:32:30 Debug: auth-master: conn unix:/var/run/dovecot/auth-userdb (pid=800187,uid=0): Disconnected: Connection closed (fd=9) Similarly, in my lua script, I try to use the "dovecot.auth.log_debug/log_info" etc. functions in documentation within the scope of auth_passdb_lookup or auth_userdb_lookup, yet I never see any debug prints even if I add a debug line to the start of the function to indicate entry. What I would like to know is whether there is some debug flag I'm missing to see the routing from config -> lua script. Does this actually exist? I didn't see anything enlightening in the man pages or online documentation. Hopefully I'm just missing something simple. Cheers, -- Thomas "Andy" Baugh | Software Development Engineer IV andy.baugh(a)webpros.com www.webpros.com

1 1

Strange mailq errors
by Xavier Humbert 22 Jul '25

22 Jul '25

Hi, I recently experienced strange errors in mailq : [root@numenor ~]# mailq -Queue ID- --Size-- ----Arrival Time---- -Sender/Recipient------- 56BF31C9391 2320 Fri Jul 18 03:42:33 info(a)quora.com (temporary failure. Command output: lda(postfix): Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied) postfix(a)groumpf.org All other messages are getting in without error. Furthermore these are probably spam which shouldn't get in, since postfix@ is not in the authorized recipients When it happens, it is always spam for postfix@ Any idea ? Regards, Xavier -- Xavier HUMBERT - Unix/Win/MacOSX Sysadmin/Network Engineer https://www.amdh.fr

1 0

dovecot internal auth cache expires soon
by Burn Zero 21 Jul '25

21 Jul '25

Hi, I am new to dovecot and I am trying to prepare a POC environment. I have dovecot installed with postfix to perform SASL authentication. I'm using postgresql as auth backend which is working fine. But I am facing an issue with dovecot's internal auth cache. The internal auth cache just expires in 5 minutes. There is only one login (it's me testing) and there are no other logins. OS version: Almalinux 10 Postfix: postfix-3.8.5-8.el10.x86_64 system memory: 4 GB CPU: 2 auth_cache_size = 10M auth_cache_ttl = 1800secs auth_cache_negative_ttl = 300secs ( I have tried this setting to 0 but it does not change anything ) Here's the dovecot -n: # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # OS: Linux 6.12.0-55.9.1.el10_0.x86_64 x86_64 AlmaLinux release 10.0 (Purple Lion) # Hostname: localhostvm auth_cache_size = 10 M auth_cache_verify_password_with_worker = yes auth_debug = yes auth_mechanisms = plain login auth_verbose = yes login_log_format = %$: %s %f passdb { args = /etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } protocols = service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = PROFILE=SYSTEM ssl_key = # hidden, use -P to show it userdb { driver = prefetch } Here's the cache hit log: Jul 14 11:53:35 localhostvm postfix/submission/smtpd[107852]: connect from remote-server Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: client in: AUTH#0112#011LOGIN#011service=smtp#011nologin#011lip=192.168.100.12#011rip=192.168.100.25 Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: client passdb out: CONT#0112#011VXNlcm5hbWU6 Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: client in: CONT<hidden> Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: client passdb out: CONT#0112#011UGFzc3dvcmQ6 Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: client in: CONT<hidden> Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: sql(user(a)tld,192.168.100.25): Performing passdb lookup Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: sql(user(a)tld,192.168.100.25): cache hit: <hidden>#011user=user@tld Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: sql(user(a)tld,192.168.100.25): cache: validating password on worker Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: Loading modules from directory: /usr/lib64/dovecot/auth Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: sqlpool(pgsql): Creating new connection Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: sqlpool(pgsql): Creating new connection Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: conn unix:auth-worker (pid=107856,uid=97): Server accepted connection (fd=15) Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: conn unix:auth-worker (pid=107856,uid=97): Sending version handshake Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: conn unix:auth-worker (pid=107856,uid=97): auth-worker<1>: Handling PASSW request Jul 14 11:53:36 localhostvm dovecot[107739]: auth-worker(107886): Debug: conn unix:auth-worker (pid=107856,uid=97): auth-worker<1>: Finished Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: sql(user(a)tld,192.168.100.25): Finished passdb lookup Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: auth(user(a)tld,192.168.100.25): Auth request finished Jul 14 11:53:36 localhostvm dovecot[107739]: auth: Debug: client passdb out: OK#0112#011user=user@tld Jul 14 11:53:37 localhostvm postfix/submission/smtpd[107852]: 81GFE2083CH9: client=remote-server[192.168.100.25], sasl_method=LOGIN, sasl_username=user@tld I am not sure what is causing the cache to disappear in 5 min although I have set it to 1800s. Thank you.

3 2

GhettoForge is Moving
by Peter 20 Jul '25

20 Jul '25

For those of you who get dovecot from the GhettoForge repository please note that GhettoForge is moving to a new domain, GhettoForge.net. You will need to take some action in order to continue to receive dovecot updates from GhetttoForge. For further information please see: http://www.ghettoforge.net/index.php/Moving Peter

1 0

Building failures with 2.4.0 and 2.4.1 on MacOS: var_expand_crypt
by rmfuhrer＠optonline.net 18 Jul '25

18 Jul '25

I'm trying to build dovecot, both at tags 2.4.0 and 2.4.1, both failing with the same undefined-symbols link error. I've pulled the source from GitHub onto an Apple M2 Ultra Mac Studio running Sonoma 14.6.1. FWIW, I'm picking up various dependencies as packages from Homebrew via the CFLAGS and LDFLAGS args below. The prep steps before "make": $ ./autogen.sh $ CFLAGS="-I/opt/homebrew/include" LDFLAGS="-L/opt/homebrew/lib" ./configure --prefix=/opt/homebrew --with-bzlib --with-ldap --with-mysql --with-pam --with-sqlite --without-icu $ PATH="/opt/homebrew/opt/bison/bin:$PATH" make ... N.B.: The PATH tweak is solely intended to pick up a usable version (3.8.2) of bison, since the Xcode-supplied binary is too old (v2.3), and doesn't recognize certain cmdline flags. Also, getting even this far with 2.4.0 requires the "touch build-aux/config.rpath" workaround, and the 2-line patch to src/lib-http/http-server.h suggested on this thread: https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/thread/MFHSI…. Anyway, here's an excerpt of the build stdout/stderr. $ PATH="/opt/homebrew/opt/bison/bin:$PATH" make ... CCLD var_expand_crypt.la Undefined symbols for architecture arm64: "_binary_to_hex_append", referenced from: _var_expand_encrypt in var-expand-crypt.o _var_expand_encrypt in var-expand-crypt.o "_buffer_append", referenced from: _var_expand_crypt_settings in var-expand-crypt.o _var_expand_crypt_settings in var-expand-crypt.o "_buffer_append_c", referenced from: _str_append_c in var-expand-crypt.o ... ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: *** [var_expand_crypt.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 $ Hopefully this is enough info to go on, but LMK if not.

3 6

Endless cycle of delete/expunge Outlook flagged messages.
by Mart Pirita 18 Jul '25

18 Jul '25

Hi, Suddenly I have a strange problem with the latest Outlook 365 (version 2506, build 16.0.1.18925.20076 64-bit) clients. When a user flags a message, they cannot remove the flag because Outlook gives an error message "The action cannot be performed because the message has been modified". One solution is to make the message unread and then remove the flag. However, since the moment a user flags a message for the first time, the maillog contains delete/expunge loop endlessly, for example: Jul 18 09:50:25 server dovecot: imap(user): delete: box=INBOX.Euro Brand, uid=2108, msgid=<GV1P195MB16414FAC3D4BAC6326F956048351A(a)GV1P195MB1641.EURP195.PROD.OUTLOOK.COM>, size=7597602, vsize=7698181, from="Masked User" <masked.user(a)somedomain.com>, subject=testing Jul 18 09:50:25 server dovecot: imap(user): expunge: box=INBOX.Euro Brand, uid=2108, msgid=<GV1P195MB16414FAC3D4BAC6326F956048351A(a)GV1P195MB1641.EURP195.PROD.OUTLOOK.COM>, size=7597602, vsize=7698181, from="Masked User" <masked.user(a)somedomain.com>, subject=testing Jul 18 09:50:27 server dovecot: imap(user): delete: box=INBOX.Euro Brand, uid=2109, msgid=<GV1P195MB16414FAC3D4BAC6326F956048351A(a)GV1P195MB1641.EURP195.PROD.OUTLOOK.COM>, size=7597628, vsize=7698214, from="Masked User" <masked.user(a)somedomain.com>, subject=testing Jul 18 09:50:27 server dovecot: imap(user): expunge: box=INBOX.Euro Brand, uid=2109, msgid=<GV1P195MB16414FAC3D4BAC6326F956048351A(a)GV1P195MB1641.EURP195.PROD.OUTLOOK.COM>, size=7597628, vsize=7698214, from="Masked User" <masked.user(a)somedomain.com>, subject=testing Jul 18 09:50:28 server dovecot: imap(user): delete: box=INBOX.Euro Brand, uid=2110, msgid=<GV1P195MB16414FAC3D4BAC6326F956048351A(a)GV1P195MB1641.EURP195.PROD.OUTLOOK.COM>, size=7597654, vsize=7698247, from="Masked User" <masked.user(a)somedomain.com>, subject=testing Jul 18 09:50:28 server dovecot: imap(user): expunge: box=INBOX.Euro Brand, uid=2110, msgid=<GV1P195MB16414FAC3D4BAC6326F956048351A(a)GV1P195MB1641.EURP195.PROD.OUTLOOK.COM>, size=7597654, vsize=7698247, from="Masked User" <masked.user(a)somedomain.com>, subject=testing ... So the message UID will change indefinitely forever. Is there any way to fix this with dovecot configuration? ### dovecot -n # 2.3.21.1 (d492236fa0): /etc/dovecot/dovecot.conf auth_cache_size = 1 k auth_failure_delay = 1 mins auth_mechanisms = plain login base_dir = /var/run/dovecot/ default_client_limit = 2000 default_process_limit = 500 disable_plaintext_auth = no dsync_features = no-header-hashes import_environment = TZ CORE_OUTOFMEM CORE_ERROR TZ=:/etc/localtime MALLOC_MMAP_THRESHOLD_=131072 listen = * login_greeting = login_log_format_elements = %u %r %m %c %k mail_location = maildir:~/Maildir mail_log_prefix = "%s(%u): " mail_plugins = " mail_log notify" mail_sort_max_read_count = 100 mailbox_list_index_very_dirty_syncs = yes maildir_very_dirty_syncs = yes passdb { args = dovecot driver = pam } plugin { autocreate2 = Sent Items autosubscribe2 = Sent Items mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject vsize } protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 1 } service imap { process_limit = 2048 vsz_limit = 1 G } ssl_ca = </etc/ssl/certs/mail.ca.crt ssl_cert = </etc/ssl/certs/mail.fullchain.cer ssl_cipher_list = kEECDH:+kEECDH+SHA:kEDH:+kEDH+SHA:+kEDH+CAMELLIA:kECDH:+kECDH+SHA:kRSA:+kRSA+SHA:+kRSA+CAMELLIA:!aNULL:!eNULL:!SSLv2:!RC4:!MD5:!DES:!EXP:!SEED:!IDEA:!3DES ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1 ssl_prefer_server_ciphers = yes state_dir = /var/run/dovecot userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags delay-newmail imap_idle_notify_interval = 15 mins imap_logout_format = %{rip}, bytes=%i/%o, del=%{deleted} mail_max_userip_connections = 500 } -- Mart

1 0

Message Duplication
by Doug Hardie 17 Jul '25

17 Jul '25

I have a persistent, but infrequent situation where a message from a mail list will appear in the list of messages twice. The IDs are identical between the copies. There is only one copy of the email in the mailbox. It appears that there are two entries in some index. Apple's mail gets confused by this. If I delete the first entry, the second remains but is tagged as found in mailbox NULL. It cannot easily be deleted. My first thought was that sieve was saving two copies. So I pulled a copy of the original email and ran sieve-test on it. It is only saved once to the proper mailbox. I have not been able to determine if the problem is in Dovecot or Apple's mail app. From what I see, it could be either. I would appreciate any ideas on how to diagnose this further. Thanks, -- Doug

1 0

Unknown section name: sieve_script
by Odhiambo Washington 16 Jul '25

16 Jul '25

I have manually compiled and installed Dovecot from git on Ubuntu 24.04 server. I have then brought in a config from a running server - basically I copied the /etc/dovecot to this server and customized the params necessary. Now I am getting this error and I am not sure why: root@lists:/home/wash# doveconf -n # 0.0.0-35284+9240e3a438 (9240e3a438): /usr/local/etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/dovecot.conf line 71: Unknown section name: sieve_script -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html] I have manually compiled and installed Dovecot from git on Ubuntu 24.04 server. I have then brought in a config from a running server - basically I copied the /etc/dovecot to this server and customized the params necessary. Now I am getting this error and I am not sure why: root@lists:/home/wash# doveconf -n # 0.0.0-35284+9240e3a438 (9240e3a438): /usr/local/etc/dovecot/dovecot.conf doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/dovecot.conf line 71: Unknown section name: sieve_script -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' -\_(Tu)_/- :-) [How to ask smart questions: [1]http://www.catb.org/~esr/faqs/smart-questions.html] References Visible links 1. http://www.catb.org/~esr/faqs/smart-questions.html

1 1

dovecot reload 2.4.1 => core dump
by Genes Lists 16 Jul '25

16 Jul '25

"systemctl reload docecot" crashed. systemctl start and restart work fine before and after the reload crash. Running on archlinux (using the arch dovecot 2.4.1 package). Probably about 15-20 connected clients at time of crash . Is this a known issue I wonder? thanks gene All I have at this point is systemd reported trace of the crash: Process 1381 (dovecot) of user 0 dumped core. Stack trace of thread 1381: #0 0x00007e78fad7ed1d n/a (libc.so.6 + 0x16ed1d) #1 0x00007e78fac758d8 n/a (libc.so.6 + 0x658d8) #2 0x00007e78fac99e2e n/a (libc.so.6 + 0x89e2e) #3 0x00007e78fac705d6 snprintf (libc.so.6 + 0x605d6) #4 0x00007e78fad271e1 n/a (libc.so.6 + 0x1171e1) #5 0x00007e78fad27943 __syslog_chk (libc.so.6 + 0x117943) #6 0x00007e78faf38ce5 n/a (libdovecot.so.0 + 0x138ce5) #7 0x00007e78faf36d4d n/a (libdovecot.so.0 + 0x136d4d) #8 0x00007e78faf3701e i_syslog_error_handler (libdovecot.so.0 + 0x13701e) #9 0x000058ca208bd7bf n/a (/usr/bin/dovecot + 0x87bf) #10 0x00007e78faf355e6 i_warning (libdovecot.so.0 + 0x1355e6) #11 0x000058ca208c79fa n/a (/usr/bin/dovecot + 0x129fa) #12 0x00007e78faf5b698 n/a (libdovecot.so.0 + 0x15b698) #13 0x00007e78faf536e4 io_loop_call_io (libdovecot.so.0 + 0x1536e4) #14 0x00007e78faf54c8b io_loop_handler_run_internal (libdovecot.so.0 + 0x154c8b) #15 0x00007e78faf54d47 io_loop_handler_run (libdovecot.so.0 + 0x154d47) #16 0x00007e78faf54f49 io_loop_run (libdovecot.so.0 + 0x154f49) #17 0x00007e78fae9fc00 master_service_run (libdovecot.so.0 + 0x9fc00) #18 0x000058ca208bd017 main (/usr/bin/dovecot + 0x8017) #19 0x00007e78fac376b5 n/a (libc.so.6 + 0x276b5) #20 0x00007e78fac37769 __libc_start_main (libc.so.6 + 0x27769) #21 0x000058ca208bd605 _start (/usr/bin/dovecot + 0x8605) ELF object binary architecture: AMD x86-64 -- Gene "systemctl reload docecot" crashed. systemctl start and restart work fine before and after the reload crash. Running on archlinux (using the arch dovecot 2.4.1 package). Probably about 15-20 connected clients at time of crash . Is this a known issue I wonder? thanks gene All I have at this point is systemd reported trace of the crash: Process 1381 (dovecot) of user 0 dumped core. Stack trace of thread 1381: #0 0x00007e78fad7ed1d n/a (libc.so.6 + 0x16ed1d) #1 0x00007e78fac758d8 n/a (libc.so.6 + 0x658d8) #2 0x00007e78fac99e2e n/a (libc.so.6 + 0x89e2e) #3 0x00007e78fac705d6 snprintf (libc.so.6 + 0x605d6) #4 0x00007e78fad271e1 n/a (libc.so.6 + 0x1171e1) #5 0x00007e78fad27943 __syslog_chk (libc.so.6 + 0x117943) #6 0x00007e78faf38ce5 n/a (libdovecot.so.0 + 0x138ce5) #7 0x00007e78faf36d4d n/a (libdovecot.so.0 + 0x136d4d) #8 0x00007e78faf3701e i_syslog_error_handler (libdovecot.so.0 + 0x13701e) #9 0x000058ca208bd7bf n/a (/usr/bin/dovecot + 0x87bf) #10 0x00007e78faf355e6 i_warning (libdovecot.so.0 + 0x1355e6) #11 0x000058ca208c79fa n/a (/usr/bin/dovecot + 0x129fa) #12 0x00007e78faf5b698 n/a (libdovecot.so.0 + 0x15b698) #13 0x00007e78faf536e4 io_loop_call_io (libdovecot.so.0 + 0x1536e4) #14 0x00007e78faf54c8b io_loop_handler_run_internal (libdovecot.so.0 + 0x154c8b) #15 0x00007e78faf54d47 io_loop_handler_run (libdovecot.so.0 + 0x154d47) #16 0x00007e78faf54f49 io_loop_run (libdovecot.so.0 + 0x154f49) #17 0x00007e78fae9fc00 master_service_run (libdovecot.so.0 + 0x9fc00) #18 0x000058ca208bd017 main (/usr/bin/dovecot + 0x8017) #19 0x00007e78fac376b5 n/a (libc.so.6 + 0x276b5) #20 0x00007e78fac37769 __libc_start_main (libc.so.6 + 0x27769) #21 0x000058ca208bd605 _start (/usr/bin/dovecot + 0x8605) ELF object binary architecture: AMD x86-64 -- Gene

2 3

Any planned 2.4.2 release date
by Andreas Haerter 14 Jul '25

14 Jul '25

Hi, I am currently planning the migration from Dovecot 2.3 to 2.4 and was wondering if version 2.4.2 is just around the corner (and it therefore might make sense to wait a few more days). Is there any planned schedule or does it still make sense to migrate to 2.4.1 within the next ~14 days? -- Regards, Andreas Haerter foundata GmbH Steinhäuserstr. 20 76135 Karlsruhe Sitz der Gesellschaft: Karlsruhe Registergericht: Amtsgericht Mannheim, HRB 714807 Geschäftsführung: Andreas Haerter USt-IdNr.: DE284122682

10 20

Access to deleted emails
by Kamil Jońca 14 Jul '25

14 Jul '25

Some time ago I mistakenly delete a lot of emails (mdbox storage) I was able to recover them with command like: --8<---------------cut here---------------start------------->8--- doveadm import mdbox_deleted:~/Mail/0 "" ALL --8<---------------cut here---------------end--------------->8--- But now, with I get: --8<---------------cut here---------------start------------->8--- %doveadm import -u kjonca mdbox_deleted:~/Mail/0 "" ALL doveadm(kjonca): Fatal: Import namespace initialization failed: mdbox_deleted: mdbox: mailbox_root_directory_name must not be empty --8<---------------cut here---------------end--------------->8--- How can I restore mails? KJ -- http://wolnelektury.pl/wesprzyj/teraz/ Hartley's First Law: You can lead a horse to water, but if you can get him to float on his back, you've got something.

1 0

Better 2.4.x docs?
by Steve Litt 13 Jul '25

13 Jul '25

Are you planning to improve your Dovecot 2.4.x documentation? The current 2.4.x documentation has: * Non-obvious links between 2.4.x and 2.3.x * Some 2.3.x specific grammar * Almost no examples * 2.4.x material is scattered across many pages * Contains a few inaccuracies * Contains some contradictions 2.4.x is such a huge change that it should have its own, standalone documentation tree exclusively for 2.4.x. This tree should have a different color scheme than your other docs so people know at a glance exactly what they're looking at. You could have a page devoted to often used dovecot.conf content, with numerous examples, documented as if there had never been an earlier version. You could have a page devoted to conversion of 2.3.x dovecot.conf to 2.4.x, once again, with numerous examples. Another page with more exotic dovecot.conf content, with numerous examples. Another page discussing the 2.3.x features that don't appear in 2.4.x, what capabilities that takes away, and how best to cobble together those capabilities for those who don't want Dovecot Professional. Another page for brand new capabilities of 2.4.x. Thanks, SteveT Steve Litt http://444domains.com

4 5

Dovecot 2.4 migration / passwd authentication
by John 12 Jul '25

12 Jul '25

Hello, I have problem getting passwd/userdb to work on 2.4. Debian 13 Trixie, Exim4, Dovecot 2.4.0. pop3, lmtp On a 2.3 system I could use: passdb { driver=passwd-file args = /etc/dovecot/passwd } userdb { driver=static args = uid=vmail gid=vmail home=/home/vmail/%u } service lmtp { unix_listener lmtp { } } passwd looks like this: test@onedomain.tlda:{BLF-CRYPT}$2y$05$[encoded] test@domain.tld:{ARGON2ID}$argon2id$v=19$m=65536,t=3,p=1$[encoded] test@two-domain.tldb:{ARGON2ID}$argon2id$v=19$m=65536,t=3,p=1$[encoded] I want to keep the passwd file as is, no extra fields. mail_uid = vmail mail_gid = vmail mail_home = /var/vmail/%{user} mail_driver = maildir mail_path = /home/vmail/%{user}/Maildir pop3_uidl_format = %{guid} passdb passwd-file { driver=passwd-file } userdb static { driver=static } Directory /var/vmail/test(a)domain.tld exists (empty). This doesn't work. Error messages: Exim log - attempt to deliver message: ** test(a)domain.tld R=dovecot_myrouter_lmtp T=dovecot_transport_lmtp: LMTP error after RCPT TO:<test(a)domain.tld>: 550 5.1.1 <test(a)domain.tld> User doesn't exist: test(a)domain.tld Dovecot debug log: master: Info: Dovecot v2.4.1-4 (7d8c0e5759) starting up for pop3, lmtp (core dumps disabled) auth(info): Info: passwd-file: unknown user - trying the next passdb lmtp(16933): Debug: Effective uid=0, gid=0, home=/run/dovecot/empty lmtp(16933): Debug: none: root=/home/vmail/raw-mail-user/Maildir, index=, indexpvt=, control=, inbox=, alt= lmtp(test(a)domain.tld)<16933><[some_string]>: Debug: auth-master: userdb lookup(test(a)domain.tld): Started userdb lookup lmtp(test(a)domain.tld)<16933><[some_string]>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting lmtp(test(a)domain.tld)<16933><[some_string]>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=16922,uid=0): Client connected (fd=16) lmtp(test(a)domain.tld)<16933><[some_string]>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=16922,uid=0): auth input: lmtp(test(a)domain.tld)<16933><[some_string]>: Debug: auth-master: userdb lookup(test(a)domain.tld): auth USER input: lmtp(test(a)domain.tld)<16933><[some_string]>: Debug: auth-master: userdb lookup(test(a)domain.tld): Userdb lookup failed lmtp(16933): Debug: User session is finished # doveadm user test(a)domain.tld field value uid vmail gid vmail home /home/vmail/test(a)domain.tld mail_path /home/vmail/test(a)domain.tld/Maildir How can this be fixed? Thank you for any help! John Sent with Proton Mail secure email.

2 3

Doveadm HTTP API authCacheFlush error
by Ricardo Machini 08 Jul '25

08 Jul '25

Hello, I'm getting a fatal error when I try to run the authCacheFlush command via the doveadm HTTP API. Example of the call: curl -u user:password -X POST http://localhost:9010/doveadm/v1 -H "Content-Type: application/json" -d '[["authCacheFlush",{"user":"username"},"tag1"]]' Fatal error: doveadm(::1): Panic: file doveadm-cmd-parse.c: line 120 (doveadm_cmd_param_str): assertion failed: (param->type == CMD_PARAM_STR) doveadm(::1): Error: Raw backtrace: #0 test_subprocess_fork[0x7fc5fd934a70] -> #1 backtrace_append[0x7fc5fd934d10] -> #2 backtrace_get[0x7fc5fd934eb0] -> #3 event_filter_register_cmp[0x7fc5fd93ea50] -> #4 i_syslog_fatal_handler[0x7fc5fd93eb80] -> #5 i_panic[0x7fc5fd86eca3] -> #6 [unw_get_proc_name() failed: -10] -> #7 http_server_connection_shut_down[0x7fc5fd8dd1b0] -> #8 io_loop_call_io[0x7fc5fd959a40] -> #9 io_loop_handler_run_internal[0x7fc5fd95ad80] -> #10 io_loop_handler_run[0x7fc5fd95af20] -> #11 io_loop_run[0x7fc5fd95b110] -> #12 master_service_run[0x7fc5fd8af640] -> #13 main[0x5593ce2ab3d0] -> #14 __libc_start_call_main[0x7fc5fd429550] -> #15 __libc_start_main[0x7fc5fd429600] -> #16 _start[0x5593ce2ab5c0] doveadm(::1): Fatal: master: service(doveadm): child 168532 killed with signal 6 (core dumped) Regards, Ricardo Hello, I'm getting a fatal error when I try to run the authCacheFlush command via the doveadm HTTP API. Example of the call: curl -u user:password -X POST [1]http://localhost:9010/doveadm/v1 -H "Content-Type: application/json" -d '[["authCacheFlush",{"user":"username"},"tag1"]]' Fatal error: doveadm(::1): Panic: file doveadm-cmd-parse.c: line 120 (doveadm_cmd_param_str): assertion failed: (param->type == CMD_PARAM_STR) doveadm(::1): Error: Raw backtrace: #0 test_subprocess_fork[0x7fc5fd934a70] -> #1 backtrace_append[0x7fc5fd934d10] -> #2 backtrace_get[0x7fc5fd934eb0] -> #3 event_filter_register_cmp[0x7fc5fd93ea50] -> #4 i_syslog_fatal_handler[0x7fc5fd93eb80] -> #5 i_panic[0x7fc5fd86eca3] -> #6 [unw_get_proc_name() failed: -10] -> #7 http_server_connection_shut_down[0x7fc5fd8dd1b0] -> #8 io_loop_call_io[0x7fc5fd959a40] -> #9 io_loop_handler_run_internal[0x7fc5fd95ad80] -> #10 io_loop_handler_run[0x7fc5fd95af20] -> #11 io_loop_run[0x7fc5fd95b110] -> #12 master_service_run[0x7fc5fd8af640] -> #13 main[0x5593ce2ab3d0] -> #14 __libc_start_call_main[0x7fc5fd429550] -> #15 __libc_start_main[0x7fc5fd429600] -> #16 _start[0x5593ce2ab5c0] doveadm(::1): Fatal: master: service(doveadm): child 168532 killed with signal 6 (core dumped) Regards, Ricardo References Visible links 1. http://localhost:9010/doveadm/v1

1 0

Re: How to require client SSL certificate, except for local connections
by Nikolaos Chatzikonstantinou 08 Jul '25

08 Jul '25

Hello all, Is there a solution to this message: <https://dovecot.org/list/dovecot/2017-October/109576.html>? Regards, Nikolaos Chatzikonstantinou

1 0

Access issue with public/shared mailboxes after migrating to v2.4.x
by Juergen Edner 08 Jul '25

08 Jul '25

Hi all, I'm currently trying to get my public/shared mailbox access working again after migration to 2.4.1. I thought I would have done all required changes, but Dovecot 2.4.1 seems to act slightly different than 2.3.x. I've tried to understand what is wrong, read the documentation multiple times and searched the internet for a solution, but unfortunately without final success. I hope you can shed some light on how to get the original behavior back. Let me explain my original setup, which worked for years without any issues. I've setup the following shared folders as an adminstrator and set the access right on a directly level, e.g. /home/imapshared imapshared:users 0770 /home/imapshared/.Parents imapshared:parents 0770 /home/imapshared/.Kids imapshared:kids 0770 This was my working Dovecot 2.3 configuration: namespace { type = shared separator = / prefix = '#Shared/' location = maildir:/home/imapshared:INDEXPVT=~/.imapmail/shared subscriptions = no } User, who were allowed to access the folder, got e.g. the 'parents' or 'kids' group assigned as secondary group, the primary one is 'users'. Based on the documentation I've modified the Dovecot 2.4 configuration as follows: namespace shared { type = shared mail_driver = maildir separator = / prefix = '#Shared/' mail_path = /home/imapshared mail_index_private_path = ~/.imapmail/shared subscriptions = no } This is what I already found out or tried to adjust: - I found out that the shared folder can be accessed if the shared folder system group is set to 'users' (primary group), but by default not if a system group is used which is the secondary group of a user (e.g. parents or kids) - In the documentation I found a hint, that Dovecot by default would now only accept the primary group. By setting the following parameter additional groups should also be accepted: mail_access_groups = yes Unfortunately, that doesn't restore the orinal functionality. - In the documentation I found a hint, that all folders which have been created by an administrator, should now be of type 'public' but changing that setting doesn't work either. "It's important that the namespace type is "public" regardless of whether you set the namespace prefix to "shared." or something else." This is the error which is logged, which is not true: Error: maildir: stat(/home/imapshared/.Parents/tmp) failed: Permission denied (euid=2000(father) egid=100(users) missing +x perm: /home/imapshared/.Parents, we're not in group 203(parents), dir owned by 2226:203 mode=0770) This is the user used to access the folder: uid=2000(father) gid=100(users) groups=100(users), ..., 203(parents), ... Do you have any idea or hint how to solve this issue and provide an example what needs to be modified in my configuration to get the original functionality back? Thanks Juergen -- Mail: juergen.edner(a)telejeck.de GPG Key available -- Mail: juergen(a)eisfair.org

1 0

Pigeonhole releases
by Aleksandr Mezin 07 Jul '25

07 Jul '25

Hi. I've been using https://pigeonhole.dovecot.org/releases/2.4/ to monitor when new releases are published. Now that URL suddenly returns 403. Was it an intentional change? Why? Also, https://pigeonhole.dovecot.org/download.html still points to v2.4.0 https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.0.tar.gz as the latest release. Even though a newer v2.4.1-4 https://pigeonhole.dovecot.org/releases/2.4/dovecot-pigeonhole-2.4.1-4.tar.… was published more than 2 months ago. Also, is it v2.4.1-4 or v2.4.1? The Git tag is `2.4.1` https://github.com/dovecot/pigeonhole/releases/tag/2.4.1 but the attached tarball name ends with `-2.4.1-4` (as well as the name of the tarball on https://pigeonhole.dovecot.org/releases/) What does the `-4` suffix mean? Will it be present in future versions?

2 1

Re: USERDB/LDAP fails if attribute doesn't exist
by ricardomachini＠gmail.com 06 Jul '25

06 Jul '25

Same problem here. I would like to set some default value when attribute is not found on LDAP. Luis, did you find out how to solve it? Regards, Ricardo Same problem = here. I would like = to set some default value when attribute is not found on = LDAP. Luis, did you find out how to solve = it? Regards, Ricardo

1 0

pigeonhole permission errors regarding bin_path
by jasper＠jappie.dev 06 Jul '25

06 Jul '25

Hi, While trying to use the `sieve_script_bin_path` option to have Pigeonhole auto-create directories for compiled sieve scripts, I ran into some permission issues: "Error: sieve: binary /run/dovecot2/sieve/jasper/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin: save: failed to create temporary file: open(/run/dovecot2/sieve/jasper/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin.) failed: Permission denied (euid=986(dovemail) egid=985(dovemail) missing +w perm: /run/dovecot2/sieve/jasper, dir owner missing perms)" I'm using `bin_path` like this: `sieve_script_bin_path = "/run/dovecot2/sieve/%{user|username|lower}";` and the permissions of the `sieve` directory are as follows: ``` $ ls -lah sieve total 0 drwxr-xrwx 3 root root 60 Jul 5 13:01 . drwxr-xr-x 10 root root 780 Jul 5 13:00 .. dr-xr-xr-x 2 dovemail dovemail 40 Jul 5 13:01 jasper ``` `strace`ing Dovecot shows that it uses `0555` when creating this directory (but not before setting `umask` to `000`?): ``` 260940 newfstatat(AT_FDCWD</var/vmail/jappie.dev/jasper>, "/run/dovecot2/sieve/jasper", 0x7fff4306af00, 0) = -1 ENOENT (No such file or directory) 260940 umask(000) = 077 260940 mkdir("/run/dovecot2/sieve/jasper", 0555) = 0 260940 umask(077) = 000 ``` I also tried patching Pigeonhole's source to log the value of `mode`: ``` diff --git a/src/lib-sieve/sieve-storage.c b/src/lib-sieve/sieve-storage.c index e68fe39f..4c7a081f 100644 --- a/src/lib-sieve/sieve-storage.c +++ b/src/lib-sieve/sieve-storage.c @@ -887,6 +887,6 @@ int sieve_storage_setup_bin_path(struct sieve_storage *storage, mode_t mode) if (mkdir_parents(bin_path, mode) == 0) { e_debug(storage->event, - "Created directory for binaries: %s", bin_path); + "Created directory for binaries: %s %u", bin_path, mode); return 1; } ``` and this logged `365`, which - if I understand `mode_t` correctly - corresponds to `-wxrw-r-x`: ``` Debug: sieve: storage after: file: Created directory for binaries: /run/dovecot2/sieve/jasper 365 ``` Needless to say, I'm a little confused as to what's going on here - am I missing something or does this look like a Pigeonhole / Dovecot bug? Kind regards, - Jasper Full log: ``` dovecot[260506]: lmtp(260940): Connect from local dovecot[260506]: lmtp(260940): Debug: auth-master: passdb lookup(jasper(a)jappie.dev): Started passdb lookup dovecot[260506]: lmtp(260940): Debug: auth-master: conn unix:/run/dovecot2/auth-userdb: Connecting dovecot[260506]: lmtp(260940): Debug: auth-master: conn unix:/run/dovecot2/auth-userdb (pid=260501,uid=0): Client connected (fd=14) dovecot[260506]: lmtp(260940): Debug: auth-master: conn unix:/run/dovecot2/auth-userdb (pid=260501,uid=0): auth input: user=jasper(a)jappie.dev dovecot[260506]: lmtp(260940): Debug: auth-master: passdb lookup(jasper(a)jappie.dev): auth PASS input: user=jasper(a)jappie.dev dovecot[260506]: lmtp(260940): Debug: auth-master: passdb lookup(jasper(a)jappie.dev): Finished passdb lookup (user=jasper(a)jappie.dev) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: userdb lookup(jasper(a)jappie.dev): Started userdb lookup dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: conn unix:/run/dovecot2/auth-userdb (pid=260501,uid=0): auth input: jasper(a)jappie.dev dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: userdb lookup(jasper(a)jappie.dev): auth USER input: jasper(a)jappie.dev dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: userdb lookup(jasper(a)jappie.dev): Finished userdb lookup (username=jasper(a)jappie.dev ) dovecot[260506]: lmtp(260940): Debug: Mailbox <lmtp DATA local>: Mailbox opened dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Effective uid=986, gid=985, home=/var/vmail/jappie.dev/jasper dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: open(/proc/self/io) failed: Permission denied (euid=986(dovemail) egid=985(dovemail) missing +r perm: /proc/self/io) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: maildir++: root=/var/vmail/jappie.dev/jasper/mail, index=, indexpvt=, control=, inbox=/var/vmail/jappie.dev/jasper/mail, alt= dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.From to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.Message-ID to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.Return-Path to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.Subject to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.To to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Local delivery started dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: duplicate db: Initialize dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Pigeonhole version 2.4.0 (1b2d5bb9) initializing dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: Directory for binaries: /run/dovecot2/sieve/jasper dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: Using Sieve script path: /nix/store/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.sieve dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after': Opened from 'after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Using the following personal Sieve script: after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Start execute sequence dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Opening script 1 of 1 from 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Loading script after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after': Opened script for reading dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' successfully compiled dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: Created directory for binaries: /run/dovecot2/sieve/jasper 365 dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after': Saving binary to '/run/dovecot2/sieve/jasper/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Error: sieve: binary /run/dovecot2/sieve/jasper/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin: save: failed to create temporary file: open(/run/dovecot2/sieve/jasper/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin.) failed: Permission denied (euid=986(dovemail) egid=985(dovemail) missing +w perm: /run/dovecot2/sieve/jasper, dir owner missing perms) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Executing script from 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Run script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Started running script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Finished running script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' (status=ok, resource usage: no usage recorded) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Execute result dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing result (status=ok, commit=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Starting execution of actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executed explicit keep dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing actions (status=ok, keep=explicit, executed=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing result (no commit, status=ok, keep=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Sequence active dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Finishing sequence (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing result (status=ok, commit=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Starting execution of actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing actions (status=ok, keep=implicit, executed=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Found deferred keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Execute implicit keep (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Start storing into mailbox INBOX dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing implicit keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Execute storing into mailbox 'INBOX' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox INBOX: Mailbox opened dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Saving to mailbox 'INBOX' successful so far dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing implicit keep action (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finalizing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished finalizing actions (status=ok, keep=implicit, committed=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finalize implicit keep (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finalize implicit keep action(status=ok, action_status=ok, commit_status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Commit implicit keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Commit storing into mailbox 'INBOX' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: stored mail into mailbox 'INBOX' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finish implicit keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finishing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing result (final, status=ok, keep=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Sequence finished (status=ok, keep=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Destroy dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after': Closed script dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: duplicate db: Cleanup dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Local delivery finished successfully dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: User session is finished dovecot[260506]: lmtp(260940): Disconnect from local: Logged out (state=READY) dovecot[260506]: lmtp(260940): Debug: User session is finished ``` Hi, While trying to use the `sieve_script_bin_path` option to have Pigeonhole auto- create directories for compiled sieve scripts, I ran into some permission issues: "Error: sieve: binary /run/dovecot2/sieve/jasper/ 84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin: save: failed to create temporary file: open(/run/dovecot2/sieve/jasper/84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after.svbin.) failed: Permission denied (euid=986(dovemail) egid=985(dovemail) missing +w perm: /run/dovecot2/sieve/jasper, dir owner missing perms)" I'm using `bin_path` like this: `sieve_script_bin_path = "/run/dovecot2/sieve/% {user|username|lower}";` and the permissions of the `sieve` directory are as follows: ``` $ ls -lah sieve total 0 drwxr-xrwx 3 root root 60 Jul 5 13:01 . drwxr-xr-x 10 root root 780 Jul 5 13:00 .. dr-xr-xr-x 2 dovemail dovemail 40 Jul 5 13:01 jasper ``` `strace`ing Dovecot shows that it uses `0555` when creating this directory (but not before setting `umask` to `000`?): ``` 260940 newfstatat(AT_FDCWD</var/vmail/jappie.dev/jasper>, "/run/dovecot2/sieve/ jasper", 0x7fff4306af00, 0) = -1 ENOENT (No such file or directory) 260940 umask(000) = 077 260940 mkdir("/run/dovecot2/sieve/jasper", 0555) = 0 260940 umask(077) = 000 ``` I also tried patching Pigeonhole's source to log the value of `mode`: ``` diff --git a/src/lib-sieve/sieve-storage.c b/src/lib-sieve/sieve-storage.c index e68fe39f..4c7a081f 100644 --- a/src/lib-sieve/sieve-storage.c +++ b/src/lib-sieve/sieve-storage.c @@ -887,6 +887,6 @@ int sieve_storage_setup_bin_path(struct sieve_storage *storage, mode_t mode) if (mkdir_parents(bin_path, mode) == 0) { e_debug(storage->event, - "Created directory for binaries: %s", bin_path); + "Created directory for binaries: %s %u", bin_path, mode); return 1; } ``` and this logged `365`, which - if I understand `mode_t` correctly - corresponds to `-wxrw-r-x`: ``` Debug: sieve: storage after: file: Created directory for binaries: /run/ dovecot2/sieve/jasper 365 ``` Needless to say, I'm a little confused as to what's going on here - am I missing something or does this look like a Pigeonhole / Dovecot bug? Kind regards, - Jasper Full log: ``` dovecot[260506]: lmtp(260940): Connect from local dovecot[260506]: lmtp(260940): Debug: auth-master: passdb lookup (jasper(a)jappie.dev) Started passdb lookup dovecot[260506]: lmtp(260940): Debug: auth-master: conn unix:/run/dovecot2/ auth-userdb: Connecting dovecot[260506]: lmtp(260940): Debug: auth-master: conn unix:/run/dovecot2/ auth-userdb (pid=260501,uid=0): Client connected (fd=14) dovecot[260506]: lmtp(260940): Debug: auth-master: conn unix:/run/dovecot2/ auth-userdb (pid=260501,uid=0): auth input: user=jasper(a)jappie.dev dovecot[260506]: lmtp(260940): Debug: auth-master: passdb lookup (jasper(a)jappie.dev) auth PASS input: user=jasper(a)jappie.dev dovecot[260506]: lmtp(260940): Debug: auth-master: passdb lookup (jasper(a)jappie.dev) Finished passdb lookup (user=jasper(a)jappie.dev) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: userdb lookup(jasper(a)jappie.dev): Started userdb lookup dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: conn unix:/run/dovecot2/auth-userdb (pid=260501,uid=0): auth input: jasper(a)jappie.dev dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: userdb lookup(jasper(a)jappie.dev): auth USER input: jasper(a)jappie.dev dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: auth-master: userdb lookup(jasper(a)jappie.dev): Finished userdb lookup (username=jasper(a)jappie.dev ) dovecot[260506]: lmtp(260940): Debug: Mailbox <lmtp DATA local>: Mailbox opened dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Effective uid=986, gid=985, home=/var/vmail/jappie.dev/jasper dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: open(/proc/self/io) failed: Permission denied (euid=986(dovemail) egid=985(dovemail) missing +r perm: /proc/self/io) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: maildir++: root=/var/vmail/jappie.dev/jasper/mail, index=, indexpvt=, control=, inbox=/var/vmail/jappie.dev/jasper/mail, alt= dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.From to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.Message-ID to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.Return-Path to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.Subject to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox <lmtp DATA local>: Adding field hdr.To to cache for the first time (uid=1) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Local delivery started dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: duplicate db: Initialize dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Pigeonhole version 2.4.0 (1b2d5bb9) initializing dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: Directory for binaries: /run/dovecot2/sieve/ jasper dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: Using Sieve script path: /nix/store/ 84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.sieve dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after': Opened from 'after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Using the following personal Sieve script: after/ 84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Start execute sequence dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Opening script 1 of 1 from 'after/ 84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Loading script after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after': Opened script for reading dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after' successfully compiled dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: Created directory for binaries: /run/ dovecot2/sieve/jasper 365 dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after': Saving binary to '/run/dovecot2/sieve/jasper/ 84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Error: sieve: binary /run/dovecot2/sieve/jasper/ 84lkfddk8d88ib7zh3zh6hmy5lrvn54x-after.svbin: save: failed to create temporary file: open(/run/dovecot2/sieve/jasper/84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after.svbin.) failed: Permission denied (euid=986(dovemail) egid=985(dovemail) missing +w perm: /run/dovecot2/sieve/jasper, dir owner missing perms) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Executing script from 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Run script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Started running script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: Finished running script 'after/84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after' (status=ok, resource usage: no usage recorded) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Execute result dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing result (status=ok, commit=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Starting execution of actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executed explicit keep dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing actions (status=ok, keep=explicit, executed=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing result (no commit, status=ok, keep=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Sequence active dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Finishing sequence (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing result (status=ok, commit=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Starting execution of actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing actions (status=ok, keep=implicit, executed=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Found deferred keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Execute implicit keep (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Start storing into mailbox INBOX dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Executing implicit keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Execute storing into mailbox 'INBOX' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Mailbox INBOX: Mailbox opened dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Saving to mailbox 'INBOX' successful so far dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing implicit keep action (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finalizing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished finalizing actions (status=ok, keep=implicit, committed=no) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finalize implicit keep (status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finalize implicit keep action(status=ok, action_status=ok, commit_status=ok) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Commit implicit keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Commit storing into mailbox 'INBOX' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: stored mail into mailbox 'INBOX' dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finish implicit keep action dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finishing actions dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: msgid=<E62D66EA-D095-4EBC-AFFE-640FB6824F45(a)jappie.dev>: Finished executing result (final, status=ok, keep=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Sequence finished (status=ok, keep=yes) dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: multi-script: Destroy dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: sieve: storage after: file: script '84lkfddk8d88ib7zh3zh6hmy5lrvn54x- after': Closed script dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: duplicate db: Cleanup dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: Local delivery finished successfully dovecot[260506]: lmtp(jasper(a)jappie.dev)<260940><3P0ZDyQGaWhM+wMAbxW+ag>: Debug: User session is finished dovecot[260506]: lmtp(260940): Disconnect from local: Logged out (state=READY) dovecot[260506]: lmtp(260940): Debug: User session is finished ```

2 1

how to disable services on the docker image?
by Felix Rubio 06 Jul '25

06 Jul '25

Hi everybody! I am trying to find the cleanest way to disable services (like pop3-login, pop3, etc.) in the docker image, if possible extending the existing configuration with conf.d files. Is this possible? I have tried using the protocol keyword on those services, after setting the protocols to that ones I want, and the services still get instantiated (thus consuming resources as well). Thank you! Felix

2 4

null pointer crash in lib11_trash_plugin.so
by Nik Soggia 02 Jul '25

02 Jul '25

dovecot crashes if you don't explicitly set "trash_priority" on all namespace mailboxes. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f6af06b4563 in trash_try_mailbox (error_r=0x7ffcf37077b8, box_name=0x56384813f980 "Drafts", ns=0x5638481423b0) at trash-plugin.c:582 (gdb) print trash_set $1 = (const struct trash_settings *) 0x0 unsigned int trash_priority = trash_set->trash_priority; // ^^^^^^^^^ SIGSEGV if NULL here is my configuration, to stop it from crashing uncomment the two "trash_priority = 0". cheers # 2.4.1-4 (7d8c0e5759): /etc/dovecot/dovecot.conf # Pigeonhole version 2.4.0 (1b2d5bb9) # OS: Linux 6.12.32 x86_64 Slackware 15.0 ext4 # Hostname: niksoggia.it # 4 default setting changes since version 2.4.0 dovecot_config_version = 2.4.0 auth_master_user_separator = * dovecot_storage_version = 2.4.0 mail_driver = maildir mail_home = /var/spool/mail/%{user} mail_path = /var/spool/mail/%{user}/dovecot protocols { imap = yes lmtp = yes pop3 = yes } protocol imap { mail_plugins { quota = yes trash = yes imap_quota = yes } } protocol lda { mail_plugins { quota = yes sieve = yes } } protocol lmtp { mail_plugins { quota = yes sieve = yes } } protocol pop3 { mail_plugins { quota = yes } } service imap-login { inet_listener imap { port = 143 listen = 127.0.0.1 } inet_listener imaps { port = 993 listen = 127.0.0.1 } } service managesieve-login { inet_listener sieve { listen = 127.0.0.1 } } service pop3-login { inet_listener pop3 { port = 110 listen = 127.0.0.1 } inet_listener pop3s { port = 995 listen = 127.0.0.1 } } sieve_script personal { path = /var/spool/mail/%{user}/sieve/dovecot.sieve } namespace inbox { inbox = yes prefix = separator = / trash_priority = 0 mailbox Drafts { auto = subscribe special_use = "\\Drafts" # trash_priority = 0 } mailbox Junk { auto = subscribe special_use = "\\Junk" trash_priority = 1 } mailbox Sent { auto = subscribe special_use = "\\Sent" # trash_priority = 0 } mailbox Trash { auto = subscribe special_use = "\\Trash" trash_priority = 2 } } ssl_server { cert_file = /etc/dovecot/fullchain.pem key_file = /etc/dovecot/privkey.pem } passdb pam { driver = pam } userdb passwd { driver = passwd } userdb prefetch { driver = prefetch }

1 0

how to fix this
by Marc 01 Jul '25

01 Jul '25

doveadm force-resync -u $account INBOX doveadm(): Warning: fscking index file /.../index/storage/dovecot.map.index doveadm(): Warning: mdbox /.../mdbox/storage: rebuilding indexes doveadm(): Error: Couldn't open mailbox 'foldertest1751045732429': Mailbox doesn't exist: foldertest1751045732429 doveadm(): Error: Couldn't open mailbox 'foldertest1751045732429/foldertest': Mailbox doesn't exist: foldertest1751045732429/foldertest doveadm(): Error: Couldn't open mailbox 'foldertest17485243507278': Mailbox doesn't exist: foldertest17485243507278 doveadm(): Error: Couldn't open mailbox 'foldertest17485243507278/foldertest': Mailbox doesn't exist: foldertest17485243507278/foldertest doveadm(): Error: Couldn't open mailbox 'Trash/test': Mailbox doesn't exist: Trash/test doveadm(): Error: Couldn't open mailbox 'INBOX/test-files': Mailbox doesn't exist: INBOX/test-files doveadm(): Warning: fscking index file /.../index/storage/dovecot.map.index

2 5

sievec fails when run as non-root - bug?
by Genes Lists 30 Jun '25

30 Jun '25

1) With 2.4.1, when a non-root user runs sievec on their own sieve scripts it fails to run due to permission denied on the dovecot certificate key (which is only readable by root). Specifically: sievec active.sieve doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10- ssl.conf line 10: cert_file: open(/etc/.../fullchain.pem) failed: Permission denied What is recommended way to deal with this? 2) Separate question: Might this explain why users sieve scripts are not running? I assume not as there are no 'sieve' items reported by lmtp in the logs. Config has: protocol lmtp { postmaster_address = postmaster@<domain>.com mail_plugins { sieve = yes } hostname = imap.<domain>.com } sieve_script before { driver = file path = /etc/dovecot/sieve/global active_path = remove_dup.sieve } sieve_script personal { driver = file path = ~/sieve active_path = ~/.dovecot.sieve } sieve_script after { driver = file path = /etc/dovecot/sieve active_path = default.sieve } thanks. -- Gene

2 5