- dovecot - dovecot.org

Crash in dovecot snippet when using imapc
by John van der Kamp 20 Mar '24

20 Mar '24

Hello, I've found a crash in a very specific setup. A dovecot server with imapc connection needs to receive an email with no body contents for the intent of generating a preview/snippet. It crashes somewhere deep in the jungle of istream and snapshots. I've included a script which sets up the systems to reproduce the crash. I've tested this with several versions. 2.3.16 doesn't seem to be affected, but 2.3.20 and 2.3.21 are affect. For me it produces a traceback like this, using the ubuntu version from here: https://packages.ubuntu.com/noble/dovecot-core (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140530132887360) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140530132887360) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140530132887360, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x00007fcfb8842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x00007fcfb88287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x00007fcfb8b37fe5 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at ../lib/failures.c:465 #6 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:477 #7 0x00007fcfb8be50d7 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:879 #8 0x00007fcfb8b37eea in i_panic (format=0x7fcfb8c29020 "file %s: line %d (%s): assertion failed: (%s)") at ../lib/failures.c:530 #9 0x00007fcfb8b3387b in i_stream_header_filter_snapshot_free (_snapshot=<optimized out>) at ../lib-mail/istream-header-filter.c:663 #10 i_stream_header_filter_snapshot_free (_snapshot=0x55dabe297a60) at ../lib-mail/istream-header-filter.c:655 #11 0x00007fcfb8bf25ac in i_stream_snapshot_free (_snapshot=_snapshot@entry=0x55dabe29b0d0) at ../lib/istream.c:253 #12 0x00007fcfb8bf2654 in i_stream_unref (stream=0x7ffc16cc7fa0) at ../lib/istream.c:66 #13 0x00007fcfb8d96baa in index_mail_write_body_snippet (mail=0x55dabe292058) at index/index-mail.c:1151 #14 0x00007fcfb8d97e48 in index_mail_parse_bodystructure (mail=0x55dabe292058, field=MAIL_CACHE_BODY_SNIPPET) at index/index-mail.c:1551 #15 0x00007fcfb8d97fe2 in index_mail_fetch_body_snippet (value_r=0x7ffc16cc8050, mail=0x55dabe292058) at index/index-mail.c:1602 #16 index_mail_get_special (_mail=0x55dabe292058, field=<optimized out>, value_r=0x7ffc16cc8050) at index/index-mail.c:1730 #17 0x00007fcfb8d16ffe in mail_get_special (mail=mail@entry=0x55dabe292058, field=field@entry=MAIL_FETCH_BODY_SNIPPET, value_r=value_r@entry=0x7ffc16cc8050) at /home/ubuntu/dovecot/new/dovecot-2.3.21+dfsg1/src/lib-storage/mail.c:418 #18 0x000055dabc52645c in fetch_snippet (ctx=0x55dabe26e050, mail=0x55dabe292058, preview=0x55dabe28f1f8) at ./src/imap/imap-fetch-body.c:615 #19 0x000055dabc52b5cc in imap_fetch_more_int (ctx=0x55dabe26e050, cancel=false) at ./src/imap/imap-fetch.c:562 #20 0x000055dabc52b8ad in imap_fetch_more (ctx=0x55dabe26e050, cmd=0x55dabe26de98) at ./src/imap/imap-fetch.c:617 #21 0x000055dabc51fd07 in cmd_fetch (cmd=0x55dabe26de98) at ./src/imap/cmd-fetch.c:382 #22 0x000055dabc528af4 in command_exec (cmd=0x55dabe26de98) at ./src/imap/imap-commands.c:201 #23 0x000055dabc52e9e2 in client_command_input (cmd=<optimized out>) at ./src/imap/imap-client.c:1237 #24 0x000055dabc52ea96 in client_command_input (cmd=<optimized out>) at ./src/imap/imap-client.c:1307 #25 0x000055dabc52eeed in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x55dabe26d2c8) at ./src/imap/imap-client.c:1349 #26 client_handle_input (client=0x55dabe26d2c8) at ./src/imap/imap-client.c:1363 #27 0x000055dabc52f2c4 in client_input (client=0x55dabe26d2c8) at ./src/imap/imap-client.c:1407 #28 0x00007fcfb8bfe27d in io_loop_call_io (io=0x55dabe26e660) at ../lib/ioloop.c:737 #29 0x00007fcfb8bff81a in io_loop_handler_run_internal (ioloop=0x55dabe243fd0) at ../lib/ioloop-epoll.c:222 #30 0x00007fcfb8bff8d4 in io_loop_handler_run (ioloop=0x55dabe243fd0) at ../lib/ioloop.c:789 #31 0x00007fcfb8bffa90 in io_loop_run (ioloop=0x55dabe243fd0) at ../lib/ioloop.c:762 #32 0x00007fcfb8b6ce57 in master_service_run (service=0x55dabe243e20, callback=callback@entry=0x55dabc533210 <client_connected>) at ../lib-master/master-service.c:878 #33 0x000055dabc51ad37 in main (argc=<optimized out>, argv=<optimized out>) at ./src/imap/main.c:575 John Hello, I've found a crash in a very specific setup. A dovecot server with imapc connection needs to receive an email with no body contents for the intent of generating a preview/snippet. It crashes somewhere deep in the jungle of istream and snapshots. I've included a script which sets up the systems to reproduce the crash. I've tested this with several versions. 2.3.16 doesn't seem to be affected, but 2.3.20 and 2.3.21 are affect. For me it produces a traceback like this, using the ubuntu version from here: https://packages.ubuntu.com/noble/dovecot-core (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140530132887360) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140530132887360) at ./nptl/ pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140530132887360, signo=signo@entry=6) at ./ nptl/pthread_kill.c:89 #3 0x00007fcfb8842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/ raise.c:26 #4 0x00007fcfb88287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x00007fcfb8b37fe5 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at ../lib/failures.c:465 #6 fatal_handler_real (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:477 #7 0x00007fcfb8be50d7 in i_internal_fatal_handler (ctx=<optimized out>, format=<optimized out>, args=<optimized out>) at ../lib/failures.c:879 #8 0x00007fcfb8b37eea in i_panic (format=0x7fcfb8c29020 "file %s: line %d (%s): assertion failed: (%s)") at ../lib/failures.c:530 #9 0x00007fcfb8b3387b in i_stream_header_filter_snapshot_free (_snapshot=<optimized out>) at ../lib-mail/istream-header-filter.c:663 #10 i_stream_header_filter_snapshot_free (_snapshot=0x55dabe297a60) at ../lib- mail/istream-header-filter.c:655 #11 0x00007fcfb8bf25ac in i_stream_snapshot_free (_snapshot=_snapshot@entry=0x55dabe29b0d0) at ../lib/istream.c:253 #12 0x00007fcfb8bf2654 in i_stream_unref (stream=0x7ffc16cc7fa0) at ../lib/ istream.c:66 #13 0x00007fcfb8d96baa in index_mail_write_body_snippet (mail=0x55dabe292058) at index/index-mail.c:1151 #14 0x00007fcfb8d97e48 in index_mail_parse_bodystructure (mail=0x55dabe292058, field=MAIL_CACHE_BODY_SNIPPET) at index/index-mail.c:1551 #15 0x00007fcfb8d97fe2 in index_mail_fetch_body_snippet (value_r=0x7ffc16cc8050, mail=0x55dabe292058) at index/index-mail.c:1602 #16 index_mail_get_special (_mail=0x55dabe292058, field=<optimized out>, value_r=0x7ffc16cc8050) at index/index-mail.c:1730 #17 0x00007fcfb8d16ffe in mail_get_special (mail=mail@entry=0x55dabe292058, field=field@entry=MAIL_FETCH_BODY_SNIPPET, value_r=value_r@entry=0x7ffc16cc8050) at /home/ubuntu/dovecot/new/dovecot-2.3.21+dfsg1/src/lib-storage/mail.c:418 #18 0x000055dabc52645c in fetch_snippet (ctx=0x55dabe26e050, mail=0x55dabe292058, preview=0x55dabe28f1f8) at ./src/imap/imap-fetch-body.c: 615 #19 0x000055dabc52b5cc in imap_fetch_more_int (ctx=0x55dabe26e050, cancel=false) at ./src/imap/imap-fetch.c:562 #20 0x000055dabc52b8ad in imap_fetch_more (ctx=0x55dabe26e050, cmd=0x55dabe26de98) at ./src/imap/imap-fetch.c:617 #21 0x000055dabc51fd07 in cmd_fetch (cmd=0x55dabe26de98) at ./src/imap/cmd- fetch.c:382 #22 0x000055dabc528af4 in command_exec (cmd=0x55dabe26de98) at ./src/imap/imap- commands.c:201 #23 0x000055dabc52e9e2 in client_command_input (cmd=<optimized out>) at ./src/ imap/imap-client.c:1237 #24 0x000055dabc52ea96 in client_command_input (cmd=<optimized out>) at ./src/ imap/imap-client.c:1307 #25 0x000055dabc52eeed in client_handle_next_command (remove_io_r=<synthetic pointer>, client=0x55dabe26d2c8) at ./src/imap/imap-client.c:1349 #26 client_handle_input (client=0x55dabe26d2c8) at ./src/imap/imap-client.c: 1363 #27 0x000055dabc52f2c4 in client_input (client=0x55dabe26d2c8) at ./src/imap/ imap-client.c:1407 #28 0x00007fcfb8bfe27d in io_loop_call_io (io=0x55dabe26e660) at ../lib/ ioloop.c:737 #29 0x00007fcfb8bff81a in io_loop_handler_run_internal (ioloop=0x55dabe243fd0) at ../lib/ioloop-epoll.c:222 #30 0x00007fcfb8bff8d4 in io_loop_handler_run (ioloop=0x55dabe243fd0) at ../ lib/ioloop.c:789 #31 0x00007fcfb8bffa90 in io_loop_run (ioloop=0x55dabe243fd0) at ../lib/ ioloop.c:762 #32 0x00007fcfb8b6ce57 in master_service_run (service=0x55dabe243e20, callback=callback@entry=0x55dabc533210 <client_connected>) at ../lib-master/ master-service.c:878 #33 0x000055dabc51ad37 in main (argc=<optimized out>, argv=<optimized out>) at ./src/imap/main.c:575 John

2 6

Notifications to over-quota accounts
by N V 15 Mar '24

15 Mar '24

Hello! I'm trying to allow a system email address to send notifications to over-quota accounts. Is there a way to do it? Thanks in advance! Hello! I'm trying to allow a system email address to send notifications to over-quota accounts. Is there a way to do it? Thanks in advance!

3 2

Question about sieve language
by Lev Serebryakov 15 Mar '24

15 Mar '24

Hello! I need to match all messages sent from some specific domain and all its sub-domains. I can achieve this with: if address :match :domain "From" [ "domain.com", "*.domain.com" ] { ... } But it looks ugly, especially if repeated for 5-6 domains. Is here way better? `:match ["*domain.com"]` will match "notdomain.com" and `:is [ "domain.com" ] doesn't match sub-domains. I understand, that it is (slightly?) off-topic, but I can not find any sieve-specific resources (all google find ins questions about PronotMail and FastMail filters, and these questions are very basic). Thank you. -- // Black Lion AKA Lev Serebryakov

3 4

antispoofing with dovecot submission
by Adrian M 15 Mar '24

15 Mar '24

Hi, it is possible to do antispoofing, like reject_authenticated_sender_login_mismatch from postfix ? Hi, it is possible to do antispoofing, like reject_authenticated_sender_login_mismatch from postfix ?

4 3

How to get a memory pointer in the core process
by Joan Moreau 15 Mar '24

15 Mar '24

Hi Is it possible, from a plugin perspective, to create and recover a pointer in the core process (i.e. memory not lost between 2 calls to the plugin, even after the "deinit" of the plugin" ) ? Thanks Hi Is it possible, from a plugin perspective, to create and recover a pointer in the core process (i.e. memory not lost between 2 calls to the plugin, even after the "deinit" of the plugin" ) ? Thanks

4 11

dovecot panic
by Michael Grant 15 Mar '24

15 Mar '24

I'm running dovecot 2.3.19.1 on debian stable. I just started seeing a slew of these in my log: Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: imap(mgrant)<1939553><DcMIWJ8T6s7ZIx04>: Panic: file istream-header-filter.c: line 663 (i_stream_header_filter_snapshot_free): assertion failed: (snapshot->mstream->snapshot_pending) Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: imap(mgrant)<1939553><DcMIWJ8T6s7ZIx04>: Error: Raw backtrace: #0 test_subprocess_fork[0x7f1a33d7ca20] -> #1 backtrace_append[0x7f1a33d7cc90] -> #2 backtrace_get[0x7f1a33d7ce20] -> #3 execvp_const[0x7f1a33d89f90] -> #4 i_syslog_fatal_handler[0x7f1a33d8a900] -> #5 i_panic[0x7f1a33ce00a4] -> #6 fs_wrapper_unlock[0x7f1a33cdb71d] -> #7 i_stream_snapshot_free[0x7f1a33d96110] -> #8 i_stream_unref[0x7f1a33d96180] -> #9 index_mail_get_virtual_size[0x7f1a33f2d190] -> #10 index_mail_save_finish[0x7f1a33f2d470] -> #11 index_mail_get_special[0x7f1a33f2d690] -> #12 mail_get_special[0x7f1a33eaf950] -> #13 cmd_select[0x560714f983e0] -> #14 imap_fetch_begin[0x560714f9d170] -> #15 imap_fetch_more[0x560714f9d550] -> #16 cmd_fetch[0x560714f91c00] -> #17 command_exec[0x560714f9a880] -> #18 cmd_x_cancel[0x560714fa0510] -> #19 cmd_x_cancel[0x560714fa0510] -> #20 cmd_x_cancel[0x560714fa0510] -> #21 client_handle_input[0x560714fa0880] -> #22 client_input[0x560714fa0d80] -> #23 io_loop_call_io[0x7f1a33da1c70] -> #24 io_loop_handler_run_internal[0x7f1a33da3970] -> #25 io_loop_handler_run[0x7f1a33da3b00] -> #26 io_loop_run[0x7f1a33da3cd0] -> #27 master_service_run[0x7f1a33d14180] -> #28 main[0x560714f8ca00] -> #29 __libc_init_first[0x7f1a33ac51d0] -> #30 __libc_start_main[0x7f1a33ac5280] -> #31 _start[0x560714f8d000] I realize this is a slightly old version of dovecot but this is what's in debian's stable package repository. I see 2.3.21+dfsg1-2 in testing and 2.3.21+dfsg1-3 in unstable. I really try to avoid installing this on production. I didn't recently change anything in my configs on the server. I did start recently using 'eM Client' on Windows a couple days ago, could that have caused this? Mail seems to continue to come in to my imap clients, but these errors in the log are worrying! Michael Grant I'm running dovecot 2.3.19.1 on debian stable. I just started seeing a slew of these in my log: Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: imap (mgrant)<1939553><DcMIWJ8T6s7ZIx04>: Panic: file istream-header-filter.c: line 663 (i_stream_header_filter_snapshot_free): assertion failed: (snapshot- >mstream->snapshot_pending) Mar 14 10:02:38 strange.networkguild.org dovecot[865654]: imap (mgrant)<1939553><DcMIWJ8T6s7ZIx04>: Error: Raw backtrace: #0 test_subprocess_fork[0x7f1a33d7ca20] -> #1 backtrace_append[0x7f1a33d7cc90] - > #2 backtrace_get[0x7f1a33d7ce20] -> #3 execvp_const[0x7f1a33d89f90] -> #4 i_syslog_fatal_handler[0x7f1a33d8a900] -> #5 i_panic[0x7f1a33ce00a4] -> #6 fs_wrapper_unlock[0x7f1a33cdb71d] -> #7 i_stream_snapshot_free[0x7f1a33d96110] -> #8 i_stream_unref[0x7f1a33d96180] -> #9 index_mail_get_virtual_size [0x7f1a33f2d190] -> #10 index_mail_save_finish[0x7f1a33f2d470] -> #11 index_mail_get_special[0x7f1a33f2d690] -> #12 mail_get_special[0x7f1a33eaf950] -> #13 cmd_select[0x560714f983e0] -> #14 imap_fetch_begin[0x560714f9d170] - > #15 imap_fetch_more[0x560714f9d550] -> #16 cmd_fetch[0x560714f91c00] -> #17 command_exec[0x560714f9a880] -> #18 cmd_x_cancel[0x560714fa0510] -> #19 cmd_x_cancel[0x560714fa0510] -> #20 cmd_x_cancel[0x560714fa0510] -> #21 client_handle_input[0x560714fa0880] -> #22 client_input[0x560714fa0d80] -> #23 io_loop_call_io[0x7f1a33da1c70] -> #24 io_loop_handler_run_internal [0x7f1a33da3970] -> #25 io_loop_handler_run[0x7f1a33da3b00] -> #26 io_loop_run [0x7f1a33da3cd0] -> #27 master_service_run[0x7f1a33d14180] -> #28 main [0x560714f8ca00] -> #29 __libc_init_first[0x7f1a33ac51d0] -> #30 __libc_start_main[0x7f1a33ac5280] -> #31 _start[0x560714f8d000] I realize this is a slightly old version of dovecot but this is what's in debian's stable package repository. I see 2.3.21+dfsg1-2 in testing and 2.3.21+dfsg1-3 in unstable. I really try to avoid installing this on production. I didn't recently change anything in my configs on the server. I did start recently using 'eM Client' on Windows a couple days ago, could that have caused this? Mail seems to continue to come in to my imap clients, but these errors in the log are worrying! Michael Grant

2 1

Re: [EXT] Re: How to get a memory pointer in the core process
by Joseph Tam 15 Mar '24

15 Mar '24

From: Joan Moreau > I am trying to avoid closing/ reopening a file pointer to the exact same file > between each call to the plugin Can't you do an end-run around all this by having a persistent standalone process that holds all your persistent data, and the plugin collects session data and passes it to the persistent process via sockets? You'll have to have some initial handshake protocol to establish session context, but this seems the easiest way to accomplish what you want. Joseph Tam <jtam.home(a)gmail.com>

1 0

dovecot and solr clustering
by Maciej Milaszewski 13 Mar '24

13 Mar '24

Hi I have 1 director and ~8 dovecot nodes. I thinking about Solr cluster beacuse one server solr probably is not enough. I thinking about SolrCloud Mode but I don't know if it will work with Dovecot And if not SolrCloud Mode, then what? I don't have much experience in Solr clustering and I want to choose the most optimal solution with scalable aand redundancy (bare metal servers is not problem) Hi I have 1 director and ~8 dovecot nodes. I thinking about Solr cluster beacuse one server solr probably is not enough. I thinking about SolrCloud Mode but I don't know if it will work with Dovecot And if not SolrCloud Mode, then what? I don't have much experience in Solr clustering and I want to choose the most optimal solution with scalable aand redundancy (bare metal servers is not problem)

1 0

Dovecot and SNI
by steffan＠hldns.com 13 Mar '24

13 Mar '24

I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips that’s been fine for quite some time. Recently I started getting complaints related to SNI. I test with this: openssl s_client -connect mail.domain.com:993 -crlf -quiet On macOS using OpenSSL LibreSSL 3.3.6 I test and get the default dovecot domain “SomeWrongDomain.com” which causes issues. On Oracle Linux 9 using OpenSSL 3.0.7 I get the correct response for the domain “mail.domain.com” What could cause this? Thank you, Steffan Cline steffan(a)hldns.com<mailto:steffan@hldns.com> 602-793-0014 I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips that’s been fine for quite some time. Recently I started getting complaints related to SNI. I test with this: openssl s_client -connect mail.domain.com:993 -crlf -quiet On macOS using OpenSSL LibreSSL 3.3.6 I test and get the default dovecot domain “SomeWrongDomain.com” which causes issues. On Oracle Linux 9 using OpenSSL 3.0.7 I get the correct response for the domain “mail.domain.com” What could cause this? Thank you, Steffan Cline steffan(a)hldns.com 602-793-0014

4 3

quota plugin with virtual user
by noemi 13 Mar '24

13 Mar '24

Hi, I'm having some problems after activating the quota plugin: I followed the guide from the doc[0] but I'm having problems with some virtual user. I understand that,with my conf,the quota plugin check the limit of a user and then tell postfix to accept/discard the mail. i have some users under my main domain [conf in /etc/passwd] and some virtual user/domains [conf in virtusertable/virtdomains as files in postfix]. the virtual users use their local user for the login, so dovecot doesn't know they are virtual. I think the problem is here, because it is clear that the quota-status check is made by dovecot using the virtual user and not the local user[1]. understanding the problem doesn't help me in the resolution [other than burn everything and rebuild with a single management for local/virtual users using a db] but i will prefer a more soft approach. any help? my complete conf below[2] thanks, noemi [0] https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html [1] where the virtual user is mail(a)virtdomain.com and the local user is mail_virtdomain the check is done to user 'mail', thus returning a error: Nov 16 06:36:09 quota-status(other-user)<129776><OOwwMv+3VWXw+gEAKobZ8Q>: Error: Failed to lookup user mail(a)virtdomain.com: Mail access for users with UID 8 not permitted (see first_valid_uid in config file, uid from userdb lookup). [2] # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 6.1.0-10-amd64 x86_64 Debian 11.7 zfs # Hostname: mail-ng.pangea.org auth_mechanisms = plain login auth_username_format = %Ln default_client_limit = 3000 disable_plaintext_auth = no first_valid_uid = 8 log_path = /var/log/mail.log mail_location = maildir:/home/%n/Maildir mail_plugins = " quota" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext 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 { driver = pam } plugin { quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to https://laweb.pangea.org/contacte/ for instructions on how to fix this. quota_grace = 10%% quota_max_mail_size = 100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full and cannot receive any more emails quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve/;active=~/.dovecot.sieve sieve_user_log = /var/log/sieve.log sieve_vacation_send_from_recipient = yes } protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service imap-login { process_limit = 1024 service_count = 100 } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { process_limit = 1024 service_count = 0 } service pop3 { process_limit = 1024 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 7777 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { mode = 0666 user = vmail } user = dovecot } ssl_cert = </etc/letsencrypt/live/mail-ng.pangea.org/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { mail_max_userip_connections = 40 mail_plugins = " quota imap_quota" } protocol lmtp { mail_plugins = " quota sieve" }

1 0

Possible bug in dovecot doc
by Petr Šorm 13 Mar '24

13 Mar '24

Dear maintainer, there is potentially conflicting information in dovecot doc about the count quota backend. According to https://doc.dovecot.org/configuration_manual/quota/quota_count/ the count quota backend is the recommended way of calculating quota on recent Dovecot installations. But according to https://github.com/dovecot/core/blob/main/doc/example-config/conf.d/90-quot… it is extremely SLOW with Maildir. It'll eat your CPU and disk I/O. I don't think the information on github is true, but I could be wrong. Could you fix/clarify this? Thank you in advance. Best regards Petr Sorm

1 0

Configure: "Can't build with MySQL support: libmysqlclient not found"
by James L. Brown 12 Mar '24

12 Mar '24

Hi all. I’m getting errors when trying to configure make for version 2.3.21 on macOS 14.3.1 Sonoma. It ends with: checking for mysql_config... mysql_config checking for mysql_init in -lmysqlclient... no configure: error: Can't build with MySQL support: libmysqlclient not found I’m using: env PKG_CONFIG_PATH=/opt/homebrew/lib/pkgconfig pkg-config --libs libsodium CPPFLAGS=-I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include LDFLAGS=-L/opt/homebrew/opt/openssl@3/lib ./configure --with-ssl=openssl --with-mysql --with-sodium Looking at config.log I see: configure:28222: checking for mysql_config configure:28238: found /opt/homebrew/bin/mysql_config configure:28250: result: mysql_config configure:28285: checking for mysql_init in -lmysqlclient configure:28310: gcc -o conftest -std=gnu99 -g -O2 -fstack-protector-strong -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include -I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include -L/opt/homebrew/opt/openssl@3/lib conftest.c -lmysqlclient -L/opt/homebrew/Cellar/mysql/8.3.0_1/lib -lmysqlclient -lz -lzstd -lssl -lcrypto -lresolv -lz -lm >&5 ld: warning: ignoring duplicate libraries: '-lmysqlclient', '-lz' ld: library 'zstd' not found clang: error: linker command failed with exit code 1 (use -v to see invocation) configure:28310: $? = 1 Odd that it is using the old version mysql. Would someone be able to help me get it to find libmysqlclient? In /opt/homebrew/Cellar/mysql/8.0.32/lib/ I have: libmysqlclient.21.dylib libmysqlclient.a libmysqlclient.dylib Thanks, James. Hi all. I’m getting errors when trying to configure make for version 2.3.21 on macOS 14.3.1 Sonoma. It ends with: checking for mysql_config... mysql_config checking for mysql_init in -lmysqlclient... no configure: error: Can't build with MySQL support: libmysqlclient not found I’m using: env PKG_CONFIG_PATH=/opt/homebrew/lib/pkgconfig pkg-config --libs libsodium CPPFLAGS=-I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include LDFLAGS=-L/opt/ homebrew/opt/openssl@3/lib ./configure --with-ssl=openssl --with-mysql --with- sodium Looking at config.log I see: configure:28222: checking for mysql_config configure:28238: found /opt/homebrew/bin/mysql_config configure:28250: result: mysql_config configure:28285: checking for mysql_init in -lmysqlclient configure:28310: gcc -o conftest -std=gnu99 -g -O2 -fstack-protector-strong - U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -Wall -W -Wmissing-prototypes -Wmissing- declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast - Wno-duplicate-decl-specifier -Wstrict-aliasing=2 -I/opt/homebrew/Cellar/ openssl(a)3/3.2.1/include -I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include -L/opt/ homebrew/opt/openssl@3/lib conftest.c -lmysqlclient -L/opt/homebrew/Cellar/ mysql/8.3.0_1/lib -lmysqlclient -lz -lzstd -lssl -lcrypto -lresolv -lz -lm >&5 ld: warning: ignoring duplicate libraries: '-lmysqlclient', '-lz' ld: library 'zstd' not found clang: error: linker command failed with exit code 1 (use -v to see invocation) configure:28310: $? =1 Odd that it is using the old version mysql. Would someone be able to help me get it to find libmysqlclient? In /opt/homebrew/Cellar/mysql/8.0.32/lib/ I have: libmysqlclient.21.dylib libmysqlclient.a libmysqlclient.dylib Thanks, James.

3 4

Re: Dovecot installation and ssl certificates
by Joseph Tam 12 Mar '24

12 Mar '24

Jerry Stuckle writes: > I'm starting with POP3 (because it's easy to handle from the CLI). I > have it working from localhost - I can telnet to port localhost 110 and > access emails (of course I can't do this from a remote system because it > requires SSL). Sure you can: (STARTTLS style) openssl s_client -starttls pop3 -connect your.pop.server:110 (SSL style) openssl s_client -connect your.pop.server:995 You can also use ncat (exercise left to the reader). "localhost", I believe, is a specific exclusion where SSL in *not* enforced during the session. > Trying to access this from a remote system with Thunderbird is not > working. /var/log/mail.log shows the following: > > 2024-03-03T22:18:54.887061-05:00 debian-server dovecot: pop3-login: > Disconnected: Connection closed: SSL_accept() failed: error:0A000412:SSL > routines::sslv3 alert bad certificate: SSL alert number 42 (no auth > attempts in 0 secs): user=<>, rip=206.223.85.12, lip=206.223.85.137, TLS > handshaking: SSL_accept() failed: error:0A000412:SSL routines::sslv3 > alert bad certificate: SSL alert number 42, session=<l6qBL80SOePO31UM> This looks like an error message stating STARTTLS was expected but the client used a plaintext session. Try enabling STARTTLS on your Thunderbird. If that is not the cause ... Ref: https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/ The most important dovecot configurations are ssl_cert = </path/to/your/server.crt ssl_key = </path/to/your/server.key You can have protocol specific certificates e.g. protocol pop3 { ssl_cert = ... ssl_key = ... } but you'll typically put this outside the protocol section so that there is one default certificate. > I need help. First of all, an explanation as to how to configure the > dovecot-openssl.cnf file (an example with actual values - real or fake - > would be a real help). > > Second, where does this go? Maybe running doveconf will tell you where your installation expects the main configuration file to be. This file may include other config files. > Note that for right now I'm trying to just get one domain working but > eventually this will serve at least 4 domains. Once I get the first > domain working, thoughts about how to get multiple domains working would > also be appreciated. This depends on how you set up your filesystem and authentication and your security constraints. You'll have to be more specific on your setup. Confining my reply to just SSL setup, you can obtain a SSL certificate with multiple domains named listed, which makes multi-domain SSL support easier. Joseph Tam <jtam.home(a)gmail.com>

1 0

Remote IP address in dovecot
by Andre Rodier 12 Mar '24

12 Mar '24

Hello, I am using a webmail, SOGo, to access Dovecot mail server in IMAP. SOGo correctly logs the remote IP address, using the standard nginx headers, especially X-Forwarded-For. However, when I check the IMAP logs, I see my server's IP address for the "remote_ip" value. I think there is a way to override this value from the environment, but I could not find it. Thanks for your help, -- André Rodier

2 1

Dovecot installation and ssl certificates
by Jerry Stuckle 12 Mar '24

12 Mar '24

Hi, all, First of all, I will admit I am totally a noob with Dovecot. I am trying to install it on Debian and am somewhat lost. Right now this is a test system on our LAN. I'm starting with POP3 (because it's easy to handle from the CLI). I have it working from localhost - I can telnet to port localhost 110 and access emails (of course I can't do this from a remote system because it requires SSL). Trying to access this from a remote system with Thunderbird is not working. /var/log/mail.log shows the following: 2024-03-03T22:18:54.887061-05:00 debian-server dovecot: pop3-login: Disconnected: Connection closed: SSL_accept() failed: error:0A000412:SSL routines::sslv3 alert bad certificate: SSL alert number 42 (no auth attempts in 0 secs): user=<>, rip=206.223.85.12, lip=206.223.85.137, TLS handshaking: SSL_accept() failed: error:0A000412:SSL routines::sslv3 alert bad certificate: SSL alert number 42, session=<l6qBL80SOePO31UM> I tried to create a certificate with mkconf.sh but obviously don't have the right information in the configuration file and/or didn't get the files in the right place (I've seen different places they should be). I need help. First of all, an explanation as to how to configure the dovecot-openssl.cnf file (an example with actual values - real or fake - would be a real help). Second, where does this go? Note that for right now I'm trying to just get one domain working but eventually this will serve at least 4 domains. Once I get the first domain working, thoughts about how to get multiple domains working would also be appreciated. I know we noobs are a PITA but I really appreciate the help. Jerry

2 1

[dovecot 2.3.4.1] Pigeonhole sieve: Howto use vacation extension with virtual users and subject/message stored in database?
by phren＠ist-einmalig.de 11 Mar '24

11 Mar '24

Hi, we're about to replace our current auto-responder with pigeonhole sieve vacation extension. Currently the (virtual) users are able to enable and disable the auto-responder, besides subject and message, in the webinterface and the setting is stored in a database. Now we're looking for a way for the vacation extension to use the database as source for enabled/disabled/subject/message. The goal is *not* to use the virtual home directory as storage. On the first sight the extdata plugin seems to have an interface to the database, but I'm unable to find a way for conditional SQL statements. Our last resort could be the extprograms plugin, but we try to avoid shell scripts. Virtual users are common usage and so we're pretty sure that there is a way to use pigeonhole sieve vacation extension with database storage. But we're unable to find it. Can please someone point to us to the right direction? Every hint is appreciated. -- Phren

1 0

Remote IP address in dovecot
by André Rodier 11 Mar '24

11 Mar '24

Hello, I am using a webmail, SOGo, to access Dovecot mail server in IMAP. SOGo correctly logs the remote IP address, using the standard nginx headers, especially X-Forwarded-For. However, when I check the IMAP logs, I see my server's IP address for the "remote_ip" value. I think there is a way to override this value from the environment, but I could not find it. Thanks for your help, -- André Rodier

1 0

Documentation error for sieve_redirect_envelope_from
by Thomas Mechtersheimer 11 Mar '24

11 Mar '24

Hi, the documentation at https://doc.dovecot.org/settings/pigeonhole/ says regarding sieve_redirect_envelope_from setting option user_email: | The user’s primary address is used. This is configured with the | sieve_user_email setting. If that setting is not configured, user_email | is equal to sender. But checking dovecot-2.3-pigeonhole-0.5.21/src/lib-sieve/sieve-address-source.c ~line 79: | if ( type == SIEVE_ADDRESS_SOURCE_USER_EMAIL && | svinst->user_email == NULL ) | type = SIEVE_ADDRESS_SOURCE_RECIPIENT; So if sieve_user_email is not configured, "user_email" is equal to "recipient" (which is the observed behaviour). Either the documentation is incorrect and should be updated, or the source has a bug . btw: I was looking at this cause I search for a way to change the envelope sender on redirect only for a specific user. But it looks like this is impossible: sieve_redirect_envelope_from is a server wide setting; and the sieve script doesn't allow changing the envelope... -- Thomas Mechtersheimer - Necklenbroicher Str. 45a - D-40667 Meerbusch - Germany EMail: thomasm(a)wupper.com IRC-Nick: Mechti Of course I'm crazy, but that doesn't mean I'm wrong. I'm mad but not ill.

1 0

deliverability test
by Aki Tuomi 11 Mar '24

11 Mar '24

Test Aki

2 1

Abort IMAP COPY command from imapsieve?
by Tom Hendrikx 10 Mar '24

10 Mar '24

Hi, I'm finding myself regularly moving messages to the wrong folder in my MUA. Most of the time this is easily corrected, but sometimes this is a bit harder. Imagine selecting all messages in the 'Trash' or 'Junk' folder, and moving them in the 'Archive' folder (by clicking on the MUA's 'Archive' button in stead of the 'Delete' button). I'm looking into blocking this server-side using an IMAPSieve script. So far I've been able to log relevant details of such a message move, but I don't how I can abort the message move altogether. I'm now using the following config, which result in log messages like: dovecot: imap(tom(a)example.org)<540588><TmDbwVATNOoqEDeBFZcAASOvWpPsXcmR>: sieve: DEBUG: move-to-archive: Message archived: mailbox-from=INBOX mailbox-to=Archives.2023 message-id=<648ab0b4-8439-4b2d-8e53-b97e700ff9d0(a)mail.example.org> subject='Testing IMAPSieve' File: dovecot.conf ----- protocol imap { mail_plugins = $mail_plugins imap_sieve } plugin { sieve_plugins = sieve_imapsieve sieve_implicit_extensions = +vnd.dovecot.debug # Find out how to block messages from being from 'Trash' to 'Archive' folder imapsieve_mailbox1_name = Archives.* #imapsieve_mailbox1_from = INBOX imapsieve_mailbox1_before = file:/etc/dovecot/sieve-scripts/move-to-archive.sieve } ----- File: move-to-archive.sieve ----- require "environment"; require "variables"; require "vnd.dovecot.debug"; require "vnd.dovecot.imapsieve"; if header :matches "Message-ID" "*" { set "message_id" "${1}"; } else { set "message_id" "UNKNOWN"; } if header :matches "Subject" "*" { set "subject" "${1}"; } else { set "subject" "UNKNOWN"; } if environment :matches "vnd.dovecot.mailbox-from" "*" { set "mailbox_from" "${1}"; } else { set "mailbox_from" "UNKNOWN"; } if environment :matches "vnd.dovecot.mailbox-to" "*" { set "mailbox_to" "${1}"; } else { set "mailbox_to" "UNKNOWN"; } debug_log "move-to-archive: Message archived: mailbox-from=${mailbox_from} mailbox-to=${mailbox_to} message-id=${message_id} subject='${subject}'"; ----- I tried the "reject" sieve command but that only works in the context of delivery. Is there a way to abort the actual move, and return an error to the MUA? Or am I on the wrong track altogether, and is there a better approach? NB: While doing research I found that not all environment variables in RFC 6785 (https://www.rfc-editor.org/rfc/rfc6785.html#section-4) are implemented in Pigeonhole? I tried to access the 'imap.cause' and 'imap.mailbox' variables but they were empty, only the variables from RFC 5183 seem to be available. This is inline with the docs at https://github.com/dovecot/pigeonhole/blob/main/README, but not with https://github.com/dovecot/pigeonhole/blob/main/doc/plugins/imapsieve.txt and https://doc.dovecot.org/configuration_manual/sieve/plugins/imapsieve/, which both seems to imply that RFC 6785 is implemented? Kind regards, Tom

1 0

Fw: User-configurable time-based mail deletion in specific folders
by Rupert Gallagher 10 Mar '24

10 Mar '24

> Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven -- https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list -- dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org > Things like this should be done locally on the Mailclient (MUA), IMHO. If you are a company, then you must delete old e-mails automatically, by GDPR law. -------- Original Message -------- On Feb 21, 2024, 23:25, Steven Varco < dovecot.org(a)bbs.varco.ch> wrote: > Am 21.02.2024 um 21:25 schrieb Peter Reinhold : > > Hi > I have been wondering about if Dovecot has a feature that would allow users to > setup a rule for a given folder, that mails older than X days should be > deleted? > Or is > this something that would need to be done by an external script? Yes. It goes beyond of what I expect from an IMAP server. > I have looked a bit at autoexpunge, and while the basic feature looks to be > what I need, it doesn't seem to be configurable down to a specific folder on a > single user. Things like this should be done locally on the Mailclient (MUA), IMHO. Steven - - https://steven.varco.ch/ https://www.tech-island.com/ _______________________________________________ dovecot mailing list - - dovecot(a)dovecot.org To unsubscribe send an email to dovecot-leave(a)dovecot.org

6 8

JMAP status?
by Brad Koehn 08 Mar '24

08 Mar '24

Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world. Just wondering how/if JMAP support is coming along. It seems to offer major protocol advantages to a connection-oriented protocol like IMAP; I’m curious to see how it performs in the real world.

3 2

High number of folders, Low sink speed
by aria mazloom 07 Mar '24

07 Mar '24

I just moved my server. Dovecot version 2.3.19.1 (9b53102964) After the transfer, I deleted the indexes and caches and rebuilt them. One of my users is experiencing slowness when send/recevie all his folders. The user has about 250 folders with a maximum depth of 3. The volume of emails is about 13 GB. Outlook wants to receive all email folders in every send/recevie all folders. Outlook 2019 and Windows 10. We connected to other users with his Outlook and we don't have this problem. We also tested with another device and same user and we have this problem. Another user with 100 folders also reported slower sync speeds after transfer server. Outlook 2019 and Windows 10. I just moved my server. Dovecot version 2.3.19.1 (9b53102964) After the transfer, I deleted the indexes and caches and rebuilt them. One of my users is experiencing slowness when send/recevie all his folders. The user has about 250 folders with a maximum depth of 3. The volume of emails is about 13 GB. Outlook wants to receive all email folders in every send/recevie all folders. Outlook 2019 and Windows 10. We connected to other users with his Outlook and we don't have this problem. We also tested with another device and same user and we have this problem. Another user with 100 folders also reported slower sync speeds after transfer server. Outlook 2019 and Windows 10.

1 0

Bug/Warning not sure which
by Richard Shetron 04 Mar '24

04 Mar '24

Hello, My sysadmin and I spent a couple hours trying to figure out a POP3 problem that has worked for about 20 or so years. We run our own dns for sgeinc.com. I've always used mail.sgeinc.com as my incoming and outgoing server. At various times mail has been an alias for another machine. It's currently on the same address as sge.sgeinc.com. On the update forced on us on 2/22/24 or 2/23/24 it stopped working. It still works as an outgoing server but incoming POP3 it stopped working. It started working when I changed my incoming server to sge.sgeinc.com. You might want to look into it or not. We chased the initial problem to, we think, ssh-keygen in /usr/local/bin/ which was Not found but is there. Thanks root@sge:/usr/local/bin# dovecot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0-172-generic x86_64 Ubuntu 20.04.6 LTS # Hostname: sge.sgeinc.com auth_mechanisms = plain login mail_location = maildir:~/Maildir 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 { driver = pam } protocols = " imap lmtp pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0660 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } } ssl = required ssl_cert = </etc/letsencrypt/live/sgeinc.com/fullchain.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd }

5 6

Re: Bug/Warning not sure which
by Joseph Tam 03 Mar '24

03 Mar '24

> From: Richard Shetron <guest2(a)sgeinc.com> > We run our own dns for sgeinc.com. > I've always used mail.sgeinc.com as my incoming and outgoing server. At > various times mail has been an alias for another machine. It's > currently on the same address as sge.sgeinc.com. On the update forced > on us on 2/22/24 or 2/23/24 it stopped working. It still works as an > outgoing server but incoming POP3 it stopped working. It started > working when I changed my incoming server to sge.sgeinc.com. Maybe your SSL cert? $ openssl s_client -connect mail.sgeinc.com:995 < /dev/null |& openssl x509 -noout -text | grep DNS: DNS:sge.sgeinc.com, DNS:sgeinc.com, DNS:www.sgeinc.com "mail.sgeinc.com" is not in your list of alternate names, hence your mail clients started rejecting the SSL certificate as invalid. Joseph Tam <jtam.home(a)gmail.com>

1 0

LMTP: user does not exist
by dienes_devout_0d＠icloud.com 03 Mar '24

03 Mar '24

Hello all, I have been using Postfix/Dovecot for some time, but now need to setup Sieve. As I understand this requires Dovecot to do the local mailbox delivery. In my case LMTP would be the best. Here is the current setup. The users on the system all have local accounts and authenticate with Kerberos via pam_krb5 against kerberos realm domain.tld. They authenticate to the mail server as user(a)domain.tld. The server name is mail.domain.tld and mailbox names on the mail server are user(a)mail.domain.tld. User mailboxes are located in /home/user/Maildir. I went through the configuration described in the documentation (https://doc.dovecot.org/configuration_manual/howto/postfix_dovecot_lmtp/#ho…) but hit a weird problem. When LMTP is enabled in Postfix, the delivery fails with an error: 550 5.1.1 <user(a)mail.domain.tld> User doesn't exist: user(a)mail.domain.tld (in reply to RCPT TO command)) If LMTP is not enabled in Postfix, it successfully delivers the messages to ~/Maildir as expected. Can anyone advise me why is this failure with LMTP occurring and how do I fix it? Thank you, Alex

1 0

better delivery mechanism to maildir?
by dovecot.org＠schildbach.de 03 Mar '24

03 Mar '24

As many of you probably are, I'm using Postfix together with Dovecot. Postfix delivers mail for my users by writing them directly to the filesystem (maildir). I wonder is there a better alternative? I'd like to separate the two services on different physical machines, so a shared filesystem isn't trivial any more. (I'd also like to stay with maildir storage and rather not do SQL or similar.) Can mail be delivered via IMAP for example? Or is there some other delivery protocol I don't know about that both Dovecot and Postfix support? Thanks!

4 7

Dbox-storage error when compiling: no member named 'st_atim' in 'struct stat'
by James L. Brown 03 Mar '24

03 Mar '24

Hi all. I’m getting errors when trying to compile 2.3.21 on macOS 14.3.1 Sonoma. It ends with: 3.2.1/include -MT dbox-storage.lo -MD -MP -MF .deps/dbox-storage.Tpo -c dbox-storage.c -fno-common -DPIC -o .libs/dbox-storage.o dbox-storage.c:296:32: error: no member named 'st_atim' in 'struct stat' last_temp_file_scan = stats.st_atim.tv_sec; ~~~~~ ^ dbox-storage.c:297:24: error: no member named 'st_ctim' in 'struct stat' change_time = stats.st_ctim.tv_sec; ~~~~~ ^ 2 errors generated. make[5]: *** [dbox-storage.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 Before ‘make’ I ran: sudo CPPFLAGS=-I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include LDFLAGS=-L/opt/homebrew/opt/openssl@3/lib LDFLAGS=-L/opt/homebrew/lib ./configure --with-ssl=openssl --with-mysql --with-sodium I had to run ’sudo’ before ‘make’ as I was getting this error: error: error opening '.deps/fuzzer.Tpo': /Users/jlbrown/Downloads/dovecot-2.3.21/src/lib-test/.deps/fuzzer.Tpo: Permission denied Would someone be able to help we with the dbox-storage error? Thanks, James. Hi all. I’m getting errors when trying to compile 2.3.21 on macOS 14.3.1 Sonoma. It ends with: 3.2.1/include -MT dbox-storage.lo -MD -MP -MF .deps/dbox-storage.Tpo -c dbox- storage.c -fno-common -DPIC -o .libs/dbox-storage.o dbox-storage.c:296:32:error:no member named 'st_atim' in 'struct stat' last_temp_file_scan = stats.st_atim.tv_sec; ~~~~~ ^ dbox-storage.c:297:24:error:no member named 'st_ctim' in 'struct stat' change_time = stats.st_ctim.tv_sec; ~~~~~ ^ 2 errors generated. make[5]: *** [dbox-storage.lo] Error 1 make[4]: *** [all-recursive] Error 1 make[3]: *** [all-recursive] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 Before ‘make’ I ran: sudo CPPFLAGS=-I/opt/homebrew/Cellar/openssl(a)3/3.2.1/include LDFLAGS=-L/opt/ homebrew/opt/openssl@3/lib LDFLAGS=-L/opt/homebrew/lib ./configure --with- ssl=openssl --with-mysql --with-sodium I had to run ’sudo’ before ‘make’ as I was getting this error: error:error opening '.deps/fuzzer.Tpo': /Users/jlbrown/Downloads/dovecot- 2.3.21/src/lib-test/.deps/fuzzer.Tpo: Permission denied Would someone be able to help we with the dbox-storage error? Thanks, James.

1 0

IMAPSieve plugin and special-use attribute
by Kirill Kirilenko 02 Mar '24

02 Mar '24

Hello. Since version 0.5.9 Pigeonhole has RFC 8579 support, so Dovecot admins can easily setup redirection of spam messages into a personal mailbox identified by a particular special-use attribute rather than the mailbox's name. That's great! But, if we need to setup, for example, spam/not-spam reporting using IMAPSieve plugin, we still forced to specify mailbox's name in rules: # From elsewhere to Spam folder imapsieve_mailbox1_name = Spam imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/etc/dovecot/report-spam.sieve # From Spam folder to elsewhere imapsieve_mailbox2_name = * imapsieve_mailbox2_from = Spam imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_before = file:/etc/dovecot/report-ham.sieve I think, it would be great to allow one to specify a special-use attribute in imapsieve_mailboxXXX_name and imapsieve_mailboxXXX_from settings. Best regards, Kirill Kirilenko.

1 0

seeking advice Error: Failed to lookup user
by noemi 28 Feb '24

28 Feb '24

Hi, I'm having some problems after activating the quota plugin: I followed the guide from the doc[0] but I'm having problems with some virtual user. I understand that,with my conf,the quota plugin check the limit of a user and then tell postfix to accept/discard the mail. i have some users under my main domain [conf in /etc/passwd] and some virtual user/domains [conf in virtusertable/virtdomains as files in postfix]. the virtual users use their local user for the login, so dovecot doesn't know they are virtual. I think the problem is here, because it is clear that the quota-status check is made by dovecot using the virtual user and not the local user[1]. understanding the problem doesn't help me in the resolution [other than burn everything and rebuild with a single management for local/virtual users using a db] but i will prefer a more soft approach. any help? my complete conf below[2] thanks, noemi [0] https://blog.sys4.de/postfix-dovecot-mailbox-quota-en.html [1] where the virtual user is mail(a)virtdomain.com and the local user is mail_virtdomain the check is done to user 'mail', thus returning a error: Nov 16 06:36:09 quota-status(other-user)<129776><OOwwMv+3VWXw+gEAKobZ8Q>: Error: Failed to lookup user mail(a)virtdomain.com: Mail access for users with UID 8 not permitted (see first_valid_uid in config file, uid from userdb lookup). [2] # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 6.1.0-10-amd64 x86_64 Debian 11.7 zfs # Hostname: mail-ng.pangea.org auth_mechanisms = plain login auth_username_format = %Ln default_client_limit = 3000 disable_plaintext_auth = no first_valid_uid = 8 log_path = /var/log/mail.log mail_location = maildir:/home/%n/Maildir mail_plugins = " quota" mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext 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 { driver = pam } plugin { quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to https://laweb.pangea.org/contacte/ for instructions on how to fix this. quota_grace = 10%% quota_max_mail_size = 100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full and cannot receive any more emails quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:~/sieve/;active=~/.dovecot.sieve sieve_user_log = /var/log/sieve.log sieve_vacation_send_from_recipient = yes } protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service imap-login { process_limit = 1024 service_count = 100 } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { process_limit = 1024 service_count = 0 } service pop3 { process_limit = 1024 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1 port = 7777 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { mode = 0666 user = vmail } user = dovecot } ssl_cert = </etc/letsencrypt/live/mail-ng.pangea.org/fullchain.pem ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { driver = passwd } protocol imap { mail_max_userip_connections = 40 mail_plugins = " quota imap_quota" } protocol lmtp { mail_plugins = " quota sieve" }

1 0

Packages for Debian bookworm
by dovecot.org＠schildbach.de 25 Feb '24

25 Feb '24

Is there a reason there are no packages for recent Debian and Ubuntu versions? https://repo.dovecot.org/

2 1

Dovecot Authentication Protocol via SSL?
by dovecot.org＠schildbach.de 24 Feb '24

24 Feb '24

I'm trying to run the Dovecot Authentication Protocol (port 12345) [1] via SSL. Here is my non-SSL config: service auth { inet_listener { port = 12345 haproxy = yes } } Adding ssl=yes to the inner block doesn't seem to change anything, I can't connect via "openssl s_client -connect", for example. I do use SSL for IMAPS, so I know my general SSL configuration is fine and I've got a valid LetsEncrypt cert. Also, Postfix doesn't appear to offer any configuration in terms of running this protocol via SSL. Question: Does it even matter? I'm about to run this protocol over untrusted networks. Is it perhaps designed to handle this situation? I'm using SASL plain authentication. I'm obviously concerned about leaking passwords, but also about leaking usernames and activity logs in general. [1] https://doc.dovecot.org/3.0/developer_manual/design/auth_protocol/

1 0

Add tag support to 'Lua Director'
by William Edwards 24 Feb '24

24 Feb '24

Hi, There's a thread on this mailing list from 2022 called "The end of Dovecot Director?". I lost that email, hence the new conversation. Sorry about that. TL;DR: Is anyone else needing to migrate from Director interested in adding support for 2.x-style tags to the Lua script on https://doc.dovecot.org/3.0/configuration_manual/howto/director_with_lua/? Others on this list know Lua better than I. Background: Director is being removed from 2.4 (CE) / 3.x (Pro). After some notes from the community, the following manual entry popped up: https://doc.dovecot.org/3.0/configuration_manual/howto/director_with_lua/. It provides a Lua script that serves as a kind-of replacement for Director. It expects a list of backends, and maps users to a backend at connection time. The gotcha is in the last sentence: "There are no built-in tools in Dovecot to manage the database (such as adding backends, kicking users, monitoring backends, etc.). You need to build your own tooling." So, I built a CLI tool that provides the following functionality: - CRUD backends. - CRUD user-to-backend mappings. - Health-checking backends (replacing `poolmon`). - Swapping backends (move all users on backend X to backend Y). There's one to-do, though. Director had the concept of 'tags'. This is useful when one has multiple mail clusters, and users should be routed to a specific mail cluster. The Lua script does not know this concept. If a user does not have a mapping, it simply maps the user to any backend. Which could cause users to end up on the wrong backend. Therefore, it would be useful to add tag support to the Lua script: add `user_to_tags` and `tags` tables. Add a `tag_id` column to the `backends` table. Let the Lua script create a mapping to a backend with the same `tag_id` as the user entry in `user_to_tags`. Same logic as the `director_tag` passdb field (Director on 2.x). Alternatively, drop the 'tags' term: create a `user_to_backends` table with a JSON column taking multiple backend IDs (no foreign key relations = bad consistency). Alternatively, one could ensure that the Lua script never creates a mapping itself by manually creating it before the user connects. Pretty fragile in the real world, obviously. After this final to-do, I'd be happy to open-source my CLI. With kind regards, William Edwards

1 0

Help running dovecot with sieve
by pereirar2z＠gmail.com 23 Feb '24

23 Feb '24

Hi all, I'm running dovecot-pigeonhole-2.3.21-1.x86_64 & dovecot-2.3.21-1.x86_64 + roundcube 1.6.6 on my redhat server. Mailserver is working as expected with the exception fo the Filters. I've installed and configure everything that i'm aware of but unfortunatelly its not working. I think my installation is not loading this module: /usr/lib/dovecot/modules/lib90_sieve_plugin.so. But i have no idea what can I do more. Can you please help me? ###### # 2.3.21 (47349e2482): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.21 (f6cd4b8e) # OS: Linux 4.18.0-513.11.1.el8_9.x86_64 x86_64 Red Hat Enterprise Linux release 8.9 (Ootpa) xfs # Hostname: xxxxxx.xxxxx auth_debug = yes auth_verbose = yes disable_plaintext_auth = no first_valid_uid = 1000 listen = * log_path = /var/log/dovecot.log mail_debug = yes mail_location = maildir:/home/vmail/%d/%n/Maildir mail_plugins = acl mail_log notify mail_privileged_group = mail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl 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 = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve sieve_global = /var/lib/dovecot/sieve/global/ } protocols = imap pop3 sieve lmtp service auth-worker { user = vmail } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail } user = dovecot } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 4 service_count = 1 vsz_limit = 64 M } service stats { unix_listener stats-reader { group = wheel mode = 0666 user = dovecot } unix_listener stats-writer { group = wheel mode = 0666 user = dovecot } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/home/vmail/%d/%n/Maildir driver = static } verbose_ssl = yes protocol lmtp { mail_plugins = acl mail_log notify quota sieve } protocol sieve { info_log_path = /var/log/dovecot-sieve.log log_debug = category=sieve managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 64 k } (END ##### Can you guys see anything wrong here? Any help is highly appreciated! Thank-you

1 0

User-configurable time-based mail deletion in specific folders
by Peter Reinhold 21 Feb '24

21 Feb '24

Hi I have been wondering about if Dovecot has a feature that would allow users to setup a rule for a given folder, that mails older than X days should be deleted? Or is this something that would need to be done by an external script? I have looked a bit at autoexpunge, and while the basic feature looks to be what I need, it doesn't seem to be configurable down to a specific folder on a single user. -- Peter Reinhold Hi I have been wondering about if Dovecot has a feature that would allow users to setup a rule for a given folder, that mails older than X days should be deleted? Or is this something that would need to be done by an external script? I have looked a bit at autoexpunge, and while the basic feature looks to be what I need, it doesn't seem to be configurable down to a specific folder on a single user. -- Peter Reinhold

2 1

Valid Docs for Dovecot with postgresql
by burkhardt＠konsultaner.de 19 Feb '24

19 Feb '24

Hi! The docs for dovecot with postgres are outdated and I somehow cannot connect from my dovecot instance to my postgresql database. I tried a lot but the debug output dosn't help me. What user is actually trying to connect to the postgresql? the dovecot user or root or the actual user from the connection config? I want to connect locally. Do I use password or md5 or peer with a map to connect? (tried all) simple console with pgsql command works fine. I found a couple of "How tos" but nothing helped. Are there any potential version conflict? I'm on 2.3.16 with postgresql 16. Thanks! Richi Hi! The docs for dovecot with postgres are outdated and I somehow cannot connect from my dovecot instance to my postgresql database. I tried a lot but the debug output dosn't help me. What user is actually trying to connect to the postgresql? the dovecot user or root or the actual user from the connection config? I want to connect locally. Do I use password or md5 or peer with a map to connect? (tried all) simple console with pgsql command works fine. I found a couple of "How tos" but nothing helped. Are there any potential version conflict? I'm on 2.3.16 with postgresql 16. Thanks! Richi

3 4

[Dovecot] doveadm delete folders ?
by Robert Schetterer 19 Feb '24

19 Feb '24

Hi , is there a feature like doveadm expunge savedbefore ... for imap folder delete ? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

5 10

"Invalid uid in reply"
by J. B. Crawford 18 Feb '24

18 Feb '24

Hello, I am in the process of moving a previously working dovecot setup to a new authentication system. The identity management system, kanidm, uses a Pam module and NSS backend to provide user info. Authentication works normally on the machine, but Dovecot is having a lot of trouble, logging: Error: Invalid uid in reply Error: Invalid gid in reply I ran doveadm -D user jesse(a)waffle.tech as a test, and I see: Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: userdb lookup(jesse(a)waffle.tech): Started userdb lookup Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb: Connecting Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: conn unix:/run/dovecot/auth-userdb (pid=17635,uid=0): Client connected (fd=9) Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: userdb lookup(jesse(a)waffle.tech): auth USER input: jesse system_groups_user=jesse uid=4123057063 gid=4123057063 home=/var/mail/jesse mail=maildir:/var/mail/jesse/Maildir Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Debug: auth-master: userdb lookup(jesse(a)waffle.tech): Finished userdb lookup (username=jesse system_groups_user=jesse uid=4123057063 gid=4123057063 home=/var/mail/jesse mail=maildir:/var/mail/jesse/Maildir) Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Error: Invalid uid in reply Feb 17 21:58:33 doveadm(jesse(a)waffle.tech)<17666><>: Error: Invalid gid in reply We can see the UID and GID in the debug output, but it comes out blank in the final info. I'm having a hard time finding what the cause could be, is it possible that these UID/GID values are too large? that's about the only thing I can think of right now. This is Dovecot 2.3.21 (47349e2482) on Fedora 39. Thanks, jc -- J. B. Crawford jesse(a)jbcrawford.us (575) 303-9001

2 2

long mail_location value formatting
by k v 17 Feb '24

17 Feb '24

Hello! The mail_location value with all the necessary keys can be quite long, for example: mail_location = mdbox:~/mdbox:VOLATILEDIR=/dev/shm/dovecot/volatile/%d/%n:LISTINDEX=/dev/shm/dovecot/listindex/%d/%n/dovecot.list.index:ALT=/var/dovecot-alt/%d/%n/mdbox When trying to split a value into multiple lines like: mail_location = \ mdbox:~/mdbox: \ VOLATILEDIR=/dev/shm/dovecot/volatile/%d/%n: \ LISTINDEX=/dev/shm/dovecot/listindex/%d/%n/dovecot.list.index: \ ALT=/var/dovecot-alt/%d/%n/mdbox according to the documentation https://doc.dovecot.org/configuration_manual/config_file/index.html#long-li…, each new line adds a whitespace, which breaks the value: doveadm config mail_location mail_location = mdbox:~/mdbox: VOLATILEDIR=/dev/shm/dovecot/volatile/%d/%n: LISTINDEX=/dev/shm/dovecot/listindex/%d/%n/dovecot.list.index: ALT=/var/dovecot-alt/%d/%n/mdbox doveadm mailbox list -u mail(a)example.com doveadm(mail(a)example.com): Error: Namespace '': Unknown setting: VOLATILEDIR Is it possible to split the value into multiple lines for better readability? Maybe add functionality to trim extra spaces when reading the mail_location value?

1 1

Doveadm on virtual users. Auth works but user don't
by jenawork＠iol.it 17 Feb '24

17 Feb '24

Hello All. I stumbled in a strange problem. I have some users stored in LDAP directory. They have uid in name.surname form and multiple mail attributes in the form of arbitraty(a)domain-n.it The Auth process works with virtual users on passdb (I can log with arbitraty(a)domain-1.it and arbitraty(a)domain-2.it) The usedb lookup works perfectly, and dovecot correctly creates the mailboxes in the form /home/domain/name.surname/arbitraty(a)domain-1.it/Maildir and /home/domain/name.surname/arbitraty(a)domain-2.it/Maildir The doveadm auth login arbitraty(a)domain-1.it command perfectly works, allowing the login to name.surname and the userdb lookup with the correct parameters. The doveadm user and the doveadm backup commands return "arbitraty(a)domain-1.it" not found I need it to migrate from an old cyrus imap to the new server Do someone have any idea? Thank you very much. (dovecot 2.3.19.1) Example: case 1: doveadm auth login "carlo.mor(a)sybill.it" Password: passdb: carlo.mor(a)sybill.it auth succeeded extra fields: user=carlo.mor original_user=carlo.mor(a)sybill.it userdb extra fields: carlo.mor uid=1001 gid=3001 home=/home/domain/carlo.mor/carlo.mor(a)sybill.it auth_mech=PLAIN auth_user=carlo.mor(a)sybill.it doveadm user "carlo.mor(a)sybill.it" userdb lookup: user carlo.mor(a)sybill.it doesn't exist field value

1 0

shared storage with local indexes?
by Andy Balholm 14 Feb '24

14 Feb '24

I'm trying to figure out how to have multiple Dovecot servers for high availability after replication goes away. The obvious solution would be some kind of shared storage, but the docs have all kinds of warnings about possible data corruption. It seems like Maildir is the safest mailbox format for shared storage, but even with Maildir there are warnings about the possibility of corrupting the index files. Would it make sense to use shared storage for the maildirs themselves, but use the INDEX option in mail_location to store index files locally, and have separate index files for each Dovecot server? That would take care of the potential for index corruption, but what other strange problems would it cause? Andy

2 1

Additional Kerberos (Samba) / GSSAPI auth for intranet users
by r.barclay＠habmalnefrage.de 14 Feb '24

14 Feb '24

Hi, I have a Dovecot (IMAP only) and Postfix (SMTP) based mail server. User names, mailbox settings and password hashes are loaded from a PostgreSQL database. The users use Thunderbird on the desktop and K9mail or Apple Mail on mobile phones. This works fine since a few years. Now I'd like to introduce Single Sign On with Thunderbird to ease up the deployment of clients systems. (No more manual mail password entry.) Users log in on a Samba AD domain, e.g.: johndoe(a)ad.example.internal. The mail addresses (and equally auth user names for Dovecot) are in the format: johndoe(a)example.org Up to now users have different passwords for AD and mail. These systems are not integrated. I have two related questions concerning that: First question: How can I map between these on the Dovecot side? There are no mailboxes or auth users like "johndoe(a)ad.example.internal". Instead, the public domain (e.g. example.org) is used for the mail system. Up to now the mail server doesn't know anything about the Samba domain and has nothing to do with that. Second question: Can I allow GSSAPI auth for intranet users only (e.g. 192.168.42.0/24)? My Internet router forwards the IMAP and SMTP ports to the mail server to allow the mobiles phones to connect to it. But it doesn't make sense to offer GSSAPI auth for Internet users from all over the world. Isn't that somewhat risky? All the M$ish AD stuff feels somewhat Mystery Meat like for me... Thank you very much for all input and help you can provide! Yours, Reg

2 1

Inconsistency in map index with dovecot v2.3.21
by John Alex. 13 Feb '24

13 Feb '24

Hi, since I upgraded dovecot to version 2.3.21 on a FreeBSD 13.2 system, I've been seeing a few occurences of the following warnings daily: Jan 11 13:13:25 dimokritos dovecot[33170]: lmtp(user1)<8209><SId/BlXNn2URIAAA+iYuTQ:T2>: Warning: mdbox /var/vmail/users/user1/mdbox/storage: Inconsistency in map index (5,40 != 5,56) Jan 11 13:13:25 dimokritos dovecot[33170]: lmtp(user1)<8209><SId/BlXNn2URIAAA+iYuTQ:T2>: Warning: fscking index file /var/vmail/users/user1/mdbox/storage/dovecot.map.index Jan 11 13:13:25 dimokritos dovecot[33170]: lmtp(user1)<8209><SId/BlXNn2URIAAA+iYuTQ:T2>: Warning: mdbox /var/vmail/users/user1/mdbox/storage: rebuilding indexes Jan 11 13:13:26 dimokritos dovecot[33170]: lmtp(user1)<8209><SId/BlXNn2URIAAA+iYuTQ:T2>: Warning: fscking index file /var/vmail/users/user1/mdbox/storage/dovecot.map.index The numbers in parentheses seem to always be of the format (x,40 != x,56) or (x,40 != x,72). I also get such errors on some users when purging (doveadm-purge fails with error 75): doveadm(user2): Warning: mdbox /var/vmail/users/user2/mdbox/storage: Inconsistency in map index (5,40 != 5,72) doveadm(user2): Warning: fscking index file /var/vmail/users/user2/mdbox/storage/dovecot.map.index doveadm(user2): Warning: mdbox /var/vmail/users/user2/mdbox/storage: rebuilding indexes doveadm(user2): Error: Purging namespace '' failed: BUG: Unknown internal error If I rerun doveadm purge for this user it completes successfully. Can anyone shed some light on what might be causing these messages? I didn't have these with 2.3.20. Should I be worried about data loss due to these index inconsistencies?

4 4

Enforcing quotas on shared mailboxes
by dovecot＠netrelay.it 12 Feb '24

12 Feb '24

I have configured a shared private namespace in dovecot so that, via ACLs, users can access other users' mailboxes. I set up a quota for each user and this also works well. The quota is monitored and new messages are denied if the quota is exceeded. There is one problem though: apparently dovecot treats shared mailboxes in relation to the current user's quota, it does not consider (as would be appropriate) the shared mailbox owner's quota. I will try to explain better with a couple of examples. ============== Consider the following case: user1 has a quota of 1MB, totally available user2 has a quota of 10MB, totally available user1 shares the "Sales" mailbox with user2 user2 copies a 500KB message to the shared "Sales" mailbox user1's quota will be correctly deducted by 500KB, thus resulting in 0.5MB available At this point, however, let's try another operation: user2 copies an 800KB message to the shared "Sales" mailbox. The server should return error because this way user1 exceeds the allocated quota of 1MB (500KB + 800KB), but instead the copy operation succeeds. This happens because at the time of the copy operation, dovecot considers the quota limit of user2 instead of considering the quota limit of user1. ============== Let us consider another case, performing the same operations but where the user quota limits are reversed (user1 has a larger quota than user2): user1 has a quota of 10MB, totally available user2 has a quota of 1MB, totally available user1 shares the "Sales" mailbox with user2 user2 copies a 500KB message to the shared mailbox "Sales" The operation fails by overquota, because again dovecot considers user2's quota limit instead of considering user1's quota limit. Therefore, it is as if user2, with a 1MB limit, tries to write to a "larger" area (10MB). As a counterevidence, setting user1 and user2 with the same quota limit, the operation succeeds perfectly. ============== Can anyone help me solve the problem? Is this a problem that is related to my configuration? Below I attach the output of dovecot -n =============== # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-16-cloud-arm64 aarch64 Debian 12.4 auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN default_client_limit = 7168 default_process_limit = 1024 deliver_log_format = from=%{from}, envelope_sender=%{from_envelope}, subject=%{subject}, msgid=%m, size=%{size}, delivery_time=%{delivery_time}ms, %$ dict { acl = mysql:/etc/dovecot/dovecot-dict-acl-sql.conf.ext } first_valid_uid = 2000 last_valid_uid = 2000 listen = * [::] login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> mail_gid = 2000 mail_location = maildir:%Lh:INDEX=%Lh mail_plugins = quota mailbox_alias acl mail_log notify mail_uid = 2000 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext editheader metric { filter = event=imap_command_finished metric_name = imap_command } namespace { inbox = yes location = mailbox { auto = no special_use = \Archive name = Archive } mailbox { auto = no special_use = \Archive name = Archives } mailbox { auto = no special_use = \Trash name = Deleted Messages } mailbox { auto = subscribe special_use = \Drafts name = Drafts } mailbox { auto = subscribe special_use = \Junk name = Junk } mailbox { auto = no special_use = \Junk name = Junk E-mail } mailbox { auto = subscribe special_use = \Sent name = Sent } mailbox { auto = no special_use = \Sent name = Sent Items } mailbox { auto = no special_use = \Sent name = Sent Messages } mailbox { auto = no special_use = \Junk name = Spam } mailbox { auto = subscribe special_use = \Trash name = Trash } prefix = separator = / type = private name = } namespace { list = children location = maildir:%%Lh:INDEXPVT=%%Lh/Shared/%{auth_user} prefix = Shared/%%u/ separator = / subscriptions = yes type = shared name = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes result_success = continue } plugin { acl = vfile:/etc/dovecot/dovecot-acl acl_shared_dict = proxy::acl mail_log_events = delete undelete expunge copy mailbox_create mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from subject flags quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:storage=+100M quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = file:/home/vmail/%d/sieve/%n/;active=/home/vmail/%d/sieve/%n/.dovecot.sieve sieve_before = /home/vmail/sieve/sievebefore1 sieve_editheader_forbid_add = X-Verified sieve_editheader_forbid_delete = X-Verified X-Seen sieve_editheader_max_header_size = 1k sieve_extensions = +editheader sieve_global_dir = /home/vmail/sieve sieve_max_redirects = 30 sieve_vacation_default_period = 1d sieve_vacation_min_period = 0 sieve_vacation_send_from_recipient = yes } protocols = pop3 imap sieve lmtp service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service { unix_listener { group = postfix mode = 0666 user = postfix path = /var/spool/postfix/private/auth } unix_listener { group = vmail mode = 0660 user = vmail path = auth-userdb } name = auth } service config { name = config } service dict-async { name = dict-async } service { unix_listener { group = vmail mode = 0660 user = vmail path = dict } name = dict } service login/proxy-notify { name = director } service dns-client { name = dns-client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { process_min_avail = 8 service_count = 0 vsz_limit = 1 G name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service { process_limit = 2048 name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service { unix_listener { group = postfix mode = 0666 user = postfix path = /var/spool/postfix/private/dovecot-lmtp } name = lmtp } service log-errors { name = log } service { inet_listener { port = 4190 name = sieve } name = managesieve-login } service login/sieve { name = managesieve } service old-stats-mail { name = old-stats } service pop3 { service_count = 0 name = pop3-login } service login/pop3 { name = pop3 } service { executable = script /opt/scripts/dovecot/quota-warning.sh unix_listener { group = vmail mode = 0660 user = vmail path = quota-warning } name = quota-warning } service replicator-doveadm { name = replicator } service login/stats-writer { unix_listener { group = vmail mode = 0660 user = vmail path = stats-reader } unix_listener { group = vmail mode = 0660 user = vmail path = stats-writer } name = stats } service submission { name = submission-login } service login/submission { name = submission } ssl = required ssl_cert = </etc/letsencrypt/live/mydomain.com/fullchain.pem ssl_cipher_list = EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_plugins = quota mailbox_alias acl mail_log notify sieve service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns-client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service old-stats-mail { name = old-stats } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/stats-writer { name = stats } service submission { name = submission-login } service login/submission { name = submission } } protocol lmtp { mail_plugins = quota mailbox_alias acl mail_log notify sieve postmaster_address = postmaster(a)mydomain.com recipient_delimiter = + service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns-client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service old-stats-mail { name = old-stats } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/stats-writer { name = stats } service submission { name = submission-login } service login/submission { name = submission } } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 256 mail_plugins = quota mailbox_alias acl mail_log notify imap_quota imap_acl service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns-client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service old-stats-mail { name = old-stats } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/stats-writer { name = stats } service submission { name = submission-login } service login/submission { name = submission } } protocol pop3 { mail_max_userip_connections = 30 mail_plugins = quota mailbox_alias acl mail_log notify pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns-client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service old-stats-mail { name = old-stats } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/stats-writer { name = stats } service submission { name = submission-login } service login/submission { name = submission } }

3 2

SQL Authentication when the password contains spaces
by Yassine Chaouche 12 Feb '24

12 Feb '24

Dear list, I created a dovecot mysql user with a password containing spaces. When I try to run doveadm fetch (to test the sql authentication), I get the following error message in the logs: Feb 11 17:37:32 auth: Fatal: sqlpool: Missing value in connect string: xxx the connect line was: connect = "host=localhost dbname=mail user=dovecot password=xxx xxx xxx" The following code source taken from dovecot's github repo[1], suggests that the parsing relies on spaces as field separators. static int driver_mysql_parse_connect_string(struct mysql_db *db, const char *connect_string, const char **error_r) { const char *const *args, *name, *value; const char **field; db->ssl_cipher = "HIGH"; db->ssl_verify_server_cert = 1; db->connect_timeout = SQL_CONNECT_TIMEOUT_SECS; db->read_timeout = MYSQL_DEFAULT_READ_TIMEOUT_SECS; db->write_timeout = MYSQL_DEFAULT_WRITE_TIMEOUT_SECS; args = t_strsplit_spaces(connect_string, " "); for (; *args != NULL; args++) { value = strchr(*args, '='); if (value == NULL) { *error_r = t_strdup_printf("Missing value in connect string: %s", *args); return -1; } [...] How do I supply the connection string in a suitable way? References: [1] dovecot source code on github https://github.com/dovecot/core/blob/main/src/lib-sql/driver-mysql.c#L194 Troubleshooting info: Dovecot v2.3.19.1 (9b53102964) starting up for imap, lmtp, pop3 (core dumps disabled) on Debian 12 -- yassine -- sysadm +213-779 06 06 23 http://about.me/ychaouche Looking for side gigs.

2 2

doveadm fetch complains as Message was expunged
by Kirill A. Korinsky 11 Feb '24

11 Feb '24

Greeetings, I do have a cron script which runs doveadm NOT mailbox Junk SEEN SINCE 30d Everything works well with one exception, if user removes email when it's running, it may lead to an email from cron like: doveadm(...): Error: fetch(hdr) failed for box=virtual.All uid=145266: Message was expunged (for backend mailbox INBOX) I feel that it is a bug, isn't it? -- wbr, Kirill

2 1

IRC/Matrix
by Duje 10 Feb '24

10 Feb '24

Hi there! Do you have an IRC or Matrix channel, would you consider opening one for more direct response or questions one has using dovecot? - Duje Hi there! Do you have an IRC or Matrix channel, would you consider opening one for more direct response or questions one has using dovecot? - Duje

3 2

Dovecot trusted CAs
by Felix Auringer 09 Feb '24

09 Feb '24

Hello, for our testing environment, I would like to configure a CA that is trusted by Dovecot when making TLS connections. As you can see below in the config snippets, this is for example used when proxying to itself during a login with credentials for the OIDC provider. The Dovecot documentation (https://doc.dovecot.org/configuration_manual/authentication/proxies/) states: "ssl_client_ca_dir or ssl_client_ca_file aren’t currently used for verifying the remote certificate, although ideally they will be in a future Dovecot version. For now you need to add the trusted remote certificates to ssl_ca." Configuring a trusted CA via the `ssl_ca` config option works but is a little bit weird as this option originally is for TLS client authentication. I added the CA certificate to the system trust store and removed `ssl_ca` and `ssl_client_ca_file`, but it seems that Dovecot does not use the system store. Or is there any config option I am missing? Otherwise, are there any plans when `ssl_client_ca_file` will be used for remote connections (the documentation mentions that this would ideally be fixed in a later version)? And could I then use the aggregated Debian system trust store (/etc/ssl/certs/ca-certificates.crt) there? Best regards, Felix `dovecot -n` (shortened): # 2.3.19 (b3ad6004dc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.7.3-arch1-1 x86_64 Debian 11.8 passdb { args = /etc/dovecot/oauth2-token.conf.ext driver = oauth2 mechanisms = xoauth2 oauthbearer } passdb { args = /etc/dovecot/oauth2-password.conf.ext driver = oauth2 mechanisms = plain login } protocols = imap lmtp service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { inet_listener { port = 24 ssl = no } } ssl = required ssl_min_protocol = TLSv1.3 ssl_prefer_server_ciphers = yes protocol lmtp { ssl_cert = </etc/dovecot/tls/lmtp-certificate-chain.pem ssl_key = # hidden, use -P to show it } protocol imap { ssl_cert = </etc/dovecot/tls/imap-certificate-chain.pem ssl_key = # hidden, use -P to show it } `oauth2-password.conf.ext`: client_id = ${DOVECOT_OIDC_CLIENT_ID} client_secret = ${DOVECOT_OIDC_CLIENT_SECRET} introspection_mode = local force_introspection = yes username_attribute = preferred_username username_format = %Lu use_grant_password = yes grant_url = ${OIDC_TOKEN_URL} scope = ${DOVECOT_OIDC_SCOPE} issuers = ${OIDC_ISSUER_URL} pass_attrs = host=dovecot port=993 ssl=yes proxy=y proxy_mech=xoauth2 pass=%{oauth2:access_token} user=%{oauth2:sub} local_validation_key_dict = fs:posix:prefix=/etc/dovecot/keys/ tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt debug = no --- Gesellschaft für interkulturelles Zusammenleben gGmbH (GIZ) Felix Auringer IT Reformationsplatz 2 13597 Berlin Tel: 030/513 0100 00; Fax: 030/513 0100 09 www.giz.berlin; felix.auringer(a)giz.berlin Amtsgericht Charlottenburg HRB 200872 B Geschäftsführerin: Dr. Britta Marschke

1 0

doveadm-backup and quota question
by Thomas Plant 09 Feb '24

09 Feb '24

Hello, I executed a backup on my dovecot installation and saw that after the first backup, the used space in quota doubled. After executing a recalc all went to normal. For this small size mailbox it is not a problem, but I did a backup on a bigger mailbox, and it started to reject messages because of 'over quota'. Here is an example: # doveadm quota get -u info(a)domain.abc Quota name Type Value Limit % User quota STORAGE 16798 16777216 0 User quota MESSAGE 628 - 0 Domain quota STORAGE 32282 67108864 0 Domain quota MESSAGE 645 - 0 [root@vmi792826 ~]# doveadm backup -u info(a)domain.abc mdbox:/tmp/backup/info@plant-systems [root@vmi792826 ~]# doveadm quota get -u info(a)domain.abc Quota name Type Value Limit % User quota STORAGE 33596 16777216 0 User quota MESSAGE 1256 - 0 Domain quota STORAGE 64563 67108864 0 Domain quota MESSAGE 1290 - 0 [root@vmi792826 ~]# doveadm quota recalc -u info(a)domain.abc [root@vmi792826 ~]# doveadm quota get -u info(a)domain.abc Quota name Type Value Limit % User quota STORAGE 16798 16777216 0 User quota MESSAGE 628 - 0 Domain quota STORAGE 32282 67108864 0 Domain quota MESSAGE 645 - 0 Is it normal to have to issue a recalc after backup, or can it be some misconfiguration on my side? Hello, I executed a backup on my dovecot installation and saw that after the first backup, the used space in quota doubled. After executing a recalc all went to normal. For this small size mailbox it is not a problem, but I did a backup on a bigger mailbox, and it started to reject messages because of 'over quota'. Here is an example: # doveadm quota get -u info(a)domain.abc Quota name Type Value Limit % User quota STORAGE 16798 16777216 0 User quota MESSAGE 628 - 0 Domain quota STORAGE 32282 67108864 0 Domain quota MESSAGE 645 - 0 [root@vmi792826 ~]# doveadm backup -u info(a)domain.abc mdbox:/tmp/backup/ info@plant-systems [root@vmi792826 ~]# doveadm quota get -u info(a)domain.abc Quota name Type Value Limit % User quota STORAGE 33596 16777216 0 User quota MESSAGE 1256 - 0 Domain quota STORAGE 64563 67108864 0 Domain quota MESSAGE 1290 - 0 [root@vmi792826 ~]# doveadm quota recalc -u info(a)domain.abc [root@vmi792826 ~]# doveadm quota get -u info(a)domain.abc Quota name Type Value Limit % User quota STORAGE 16798 16777216 0 User quota MESSAGE 628 - 0 Domain quota STORAGE 32282 67108864 0 Domain quota MESSAGE 645 - 0 Is it normal to have to issue a recalc after backup, or can it be some misconfiguration on my side?

1 0

Re: Auth USER lookup failed
by Michael Slusarz 08 Feb '24

08 Feb '24

> On 02/05/2024 10:17 PM MST thecoudge(a)gmail.com wrote: > > I have dovecot working with PAM and Samba DC authentication for IMAP. However when I'm attempting to pass emails from postfix via LMTP > I don't actually need to authenticate LMTP I'm happy to check for valid users upstream. > > I'm getting the error: > Feb 06 15:11:39 Debian-server postfix/local[178200]: ADF0E78713C: passing <dom.username(a)Debian-server.sr.local> to transport=lmtp > Feb 06 15:11:39 Debian-server dovecot[178075]: auth: Error: static(dom.username): passdb doesn't support lookups, can't verify user's existence > Feb 06 15:11:39 Debian-server dovecot[178075]: lmtp(dom.username(a)Debian-server.sr.local)<178233><GJ/9Nou/wWU5uAIAiShiCA:T2>: Error: auth-master: userdb lookup(dom.username(a)Debian-server.sr.local): Auth USER lookup failed You need to define a userdb to return user information. Since LMTP doesn't require auth, it can't use the passdb so that's what the error message is saying. michael

3 2