- dovecot - dovecot.org

Duplicate plugins - FTS Xapian
by Joan Moreau 01 Sep '21

01 Sep '21

Hi There seems to be 2 plugins doing the same thins - https://github.com/slusarz/dovecot-fts-flatcurve/ - https://github.com/grosjo/fts-xapian/ (mine) Both are in the doc of dovecot https://doc.dovecot.org/configuration_manual/fts/ I am currently working hard to push it to RPM package, and plugin is already approved by ArchLinux and Debian Isn't there double work here ? Thanks JM

7 9

User deleted the folder
by Казанцев Владимир Серге евич 01 Sep '21

01 Sep '21

Hello, please tell me what kind of information is stored in this file: doveadm dump -t mailboxlog dovecot.mailbox.log -- С уважением, Казанцев Владимир Сергеевич системный администратор отдела ИТ АО «Елецгидроагрегат» Тел. +7 (47467) 78-1-16, Моб. +7 980 263 26 69 kazantsev.vs(a)gidroagregat.ru <mailto:kazantsev.vs@gidroagregat.ru> /Настоящее почтовое сообщение является собственностью АО «Елецгидроагрегат», конфиденциально и предназначено для получателя письма. Если Вы не являетесь получателем, вероятнее всего Вы получили письмо по ошибке и в этом случае любое его использование, перенаправление, вывод на печать или копирование данного сообщения запрещаются. Если Вы получили сообщение по ошибке, пожалуйста свяжитесь с отправителем письма. Любые взгляды или мнения, представленные в письме, могут не совпадать с точкой зрения АО «Елецгидроагрегат» и отражают только точку зрения отправителя. Однако настоящее почтовое сообщение и любые вложения в него не содержат вирусов или каких-то других недостатков, которые могли бы причинить вред Вашей системе; тем не менее, АО «Елецгидроагрегат» не несет никакой ответственности за причинение ущерба результате получения данного письма./

1 0

User deleted the folder
by Казанцев Владимир Серге евич 01 Sep '21

01 Sep '21

Hello, please tell me what kind of information is stored in this file: doveadm dump -t mailboxlog dovecot.mailbox.log -- С уважением, Казанцев Владимир Сергеевич системный администратор отдела ИТ АО «Елецгидроагрегат» Тел. +7 (47467) 78-1-16, Моб. +7 980 263 26 69 kazantsev.vs(a)gidroagregat.ru <mailto:kazantsev.vs@gidroagregat.ru> /Настоящее почтовое сообщение является собственностью АО «Елецгидроагрегат», конфиденциально и предназначено для получателя письма. Если Вы не являетесь получателем, вероятнее всего Вы получили письмо по ошибке и в этом случае любое его использование, перенаправление, вывод на печать или копирование данного сообщения запрещаются. Если Вы получили сообщение по ошибке, пожалуйста свяжитесь с отправителем письма. Любые взгляды или мнения, представленные в письме, могут не совпадать с точкой зрения АО «Елецгидроагрегат» и отражают только точку зрения отправителя. Однако настоящее почтовое сообщение и любые вложения в него не содержат вирусов или каких-то других недостатков, которые могли бы причинить вред Вашей системе; тем не менее, АО «Елецгидроагрегат» не несет никакой ответственности за причинение ущерба результате получения данного письма./

1 0

indexer crash
by Onno Molenkamp 31 Aug '21

31 Aug '21

Hi, Because I was getting segfaults in libc in calloc calls by the indexer process of Dovecot 2.3.16, I ran indexer with valgrind to look for possible memory corruption. It did indeed find that indexer was accessing memory that had already been freed, I've attached the log file. I've then tried running Dovecot with the fix in commit 97367ef61784a364ccf615cb816be6492329050d, but that didn't make any difference. Reverting (just the code in src/indexer) to the last revision before the recent rewrite to use connection.c (d76761698a06bab60a741c6794252fddec4292ef) did: valgrind doesn't log any errors anymore, and indexer has stopped crashing. Onno

3 3

Dovecot Director: Preferred backend server
by Steven Varco 31 Aug '21

31 Aug '21

Hi All I have a dovecot cluster with directror and two IMAP Servers behind. Since they are in geographical different locations I would like to have users to go to a specific IMAP backend server (if both are up) and only switch to the other if one goes down (failover). As to my current knowledge the PassDB extra field „host=„ is not suitable in this case as it would never route the client to a different backend, even if the „user specific backend“ would be down. Is their a way in dovecot to achive this? As far as I searched the documentation I could not find any information on this so far. If not, it may also help if I could get certain users to „initially" go to a specific backend (since director usually routes a client/user to the same backend server it initially connects) and therefore it would be interesting to know how dovecot director chooses wether a user goes to server1 or server2? And if a client already gets to server2, how to bring it „back“ to server1? thanks in advance, Steven -- https://steven.varco.ch/ https://www.tech-island.com/

4 7

lmtp panic with 2.3.16 (runnung ubuntu) and larger mails
by Friedhelm Buescher 30 Aug '21

30 Aug '21

Hi, when sending larger Mails (> 1MB, for example a jpg attachment), the lmtp crashes: ######################################################################### syslog: Aug 29 17:05:34 mail dovecot: lmtp(xxxx)<720677><5RuZHDCiK2El/woAkAJtwA>: Panic: Buffer write out of range (0 + 1) Aug 29 17:05:34 mail dovecot: lmtp(xxxx)<720677><5RuZHDCiK2El/woAkAJtwA>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x41) [0x7f10ae1fb151] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x22) [0x7f10ae1fb272] -> /usr/lib/dovecot/libdovecot.so.0(+0x1092eb) [0x7f10ae2082eb] -> /usr/lib/dovecot/libdovecot.so.0(+0x109387) [0x7f10ae208387] -> /usr/lib/dovecot/libdovecot.so.0(+0x5d018) [0x7f10ae15c018] -> /usr/lib/dovecot/libdovecot.so.0(+0x5bee1) [0x7f10ae15aee1] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_emit_integer+0x6a) [0x7f10ad79dfea] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_save+0x1e3) [0x7f10ad79c553] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_file_update_resource_usage+0x128) [0x7f10ad79dcc8] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_binary_close+0x7d) [0x7f10ad79ab4d] -> /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3f65) [0x7f10ae0f3f65] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x17a) [0x7f10ae4490ea] -> dovecot/lmtp(lmtp_local_default_deliver+0x1d8) [0x557cc4da83c8] -> dovecot/lmtp(lmtp_local_data+0x5ac) [0x557cc4da8b1c] -> dovecot/lmtp(client_default_cmd_data+0x191) [0x557cc4da74a1] -> dovecot/lmtp(cmd_data_continue+0x180) [0x557cc4da7230] -> /usr/lib/dovecot/libdovecot.so.0(+0x7c286) [0x7f10ae17b286] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6d) [0x7f10ae21e67d] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x145) [0x7f10ae21fd15] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x54) [0x7f10ae21e724] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f10ae21e890] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f10ae1913a7] -> dovecot/lmtp(main+0x22f) [0x557cc4da5edf] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f10adf250b3] -> dovecot/lmtp(_start+0x2e) [0x557cc4da5fee] Aug 29 17:05:34 mail dovecot: lmtp(xxxx)<720677><5RuZHDCiK2El/woAkAJtwA>: Fatal: master: service(lmtp): child 720677 killed with signal 6 (core dumped) ######################################################################### uname -a Linux mail 5.4.0-81-generic #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Installed Packages: dovecot-lmtpd=2:2.3.16-2+ubuntu20.04 dovecot-mysql=2:2.3.16-2+ubuntu20.04 dovecot-imapd=2:2.3.16-2+ubuntu20.04 dovecot-sieve=2:2.3.16-2+ubuntu20.04 dovecot-pop3d=2:2.3.16-2+ubuntu20.04 dovecot-lucene=2:2.3.16-2+ubuntu20.04 dovecot-core=2:2.3.16-2+ubuntu20.04 dovecot-managesieved=2:2.3.16-2+ubuntu20.04 dovecot-solr=2:2.3.16-2+ubuntu20.04 postfix=3.4.13-0ubuntu1.1 Tried to downgrade to dovecot-lmtpd=2:2.3.15-1+ubuntu20.04 dovecot-mysql=2:2.3.15-1+ubuntu20.04 dovecot-imapd=2:2.3.15-1+ubuntu20.04 dovecot-sieve=2:2.3.15-1+ubuntu20.04 dovecot-pop3d=2:2.3.15-1+ubuntu20.04 dovecot-lucene=2:2.3.15-1+ubuntu20.04 dovecot-core=2:2.3.15-1+ubuntu20.04 dovecot-managesieved=2:2.3.15-1+ubuntu20.04 dovecot-solr=2:2.3.15-1+ubuntu20.04 postfix=3.4.10-1ubuntu1 , which does not solve the error. ######################################################################### config: # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: Linux 5.4.0-81-generic x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: xxxx auth_verbose_passwords = plain lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:/var/maildirs/%u mail_plugins = " quota acl fts fts_solr" 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 { list = children location = maildir:%%h:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u prefix = shared.%%u. separator = . subscriptions = no type = shared } namespace inbox { inbox = yes location = prefix = separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile fts = solr fts_autoindex = yes fts_solr = url=http://127.0.0.1:8983/solr/dovecot/ recipient_delimiter = . sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = " imap lmtp sieve pop3" recipient_delimiter = . service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = postfix user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } vsz_limit = 1 G } ssl = required ssl_cert = </etc/letsencrypt/live/xxx/fullchain.pem ssl_cipher_list = ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_client_ca_dir = /etc/ssl/certs 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 lmtp { mail_plugins = " quota acl fts fts_solr sieve notify push_notification" postmaster_address = postmaster@xxx } protocol lda { mail_plugins = " quota acl fts fts_solr sieve fts fts_solr notify push_notification" } protocol imap { mail_plugins = quota imap_quota fts fts_solr } ######################################################################### sieve-file involved: # Sieve Filter # Generated by Ingo (http://www.horde.org/apps/ingo/) (05/17/2019, 06:17:18 PM) require ["fileinto", "imap4flags", "mailbox", "subaddress", "envelope", "variables", "body", "regex", "copy"]; # PDFs nach attachments speichern, damit diese lokal gespeichert werden koennen .. if body :raw :regex ["filename=.+\\.pdf"] { fileinto :create :copy "INBOX.attachments"; }

2 2

Local auth works with dovecot-proxy, remote does not
by Camilo Sperberg 30 Aug '21

30 Aug '21

Hi list! I've configured dovecot-proxy to redirect users to another server if their data is indeed on that other server. Webmail (which runs on the same machine) works perfectly fine, but clients such as Thunderbird and Outlook do not work as intended, I suspect it to be a problem with the IP that dovecot-proxy sees, but I can't figure out what is wrong: I've already done a lot of Googling and also tried to change the login_trusted_networks value, but to no avail. I've enabled debug log and here is the relevant part of a call that fails and another one that succeeds (FYI 10.164.0.3 is the machine that is doing the proxying and where webmail is located, 10.164.0.20 is the 'node', these logs come from that node, doveconf -n is also provided in the gist): https://gist.github.com/unreal4u/64de0f05b6e3b98034cdb0ae52ce1196 So as far as I can interpret the logs, in the failure case it is basically saying it should go to the node, despite it already being on that node: Aug 24 11:29:07 mail-node-2 dovecot: auth: Debug: client passdb out: OK#0112#011user=me(a)XXXXXX.XX #011host=10.164.0.20#011port=143#011proxy#011pass=<hidden> In the success case, I don't see any mention of a proxy: Aug 24 11:35:21 mail-node-2 dovecot: auth: Debug: client passdb out: OK#0116#011user=me(a)XXXXXXXXX.XX What am I missing here? Has this something to do with authentication-allow-nets or authentication-allow-real-nets ? If so: where to define it? Is there something else I'm missing? Thanks in advance for your help, Camilo Sperberg

1 1

tls_early_post_process_client_hello:unsupported protocol
by Elise 30 Aug '21

30 Aug '21

I just read a line in my logfile that I haven't noticed before: Aug 29 22:17:23 <myserver> dovecot[50098]: imap-login: Disconnected: Connection closed: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol (no auth attempts in 2 secs): user=<>, rip=104.152.52.31, lip=10.10.10.37, TLS handshaking: SSL_accept() failed: error:14209102:SSL routines:tls_early_post_process_client_hello:unsupported protocol, session=</w+MZ7jKvLhomDQf> Is this a TLS 1.3 related issue? /elise

2 1

%{cert} variable
by Andrea Gabellini 27 Aug '21

27 Aug '21

Hello, I am using Dovecot version 2.3.16. I'm experimenting with client certificates and the "ssl_verify_client_cert = yes" option. By putting the server in debug mode, I can verify that the client is correctly providing the certificate. I am trying to log using %{cert} adding it to login_log_format_elements, as per the documentation, but I get the error: "Failed to expand log_format_elements=cert=%{cert}: Unknown variable '%cert'" Also the documentation says that the short name is %k, but it overlaps with %{ssl_security}. Is the documentation wrong or is there a bug? Thanks, Andrea -- __________________________ One of the things we can do to help the poor is not to become one of them. __________________________ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

1 0

Logging to remote server
by James Brown 26 Aug '21

26 Aug '21

My Google searches must be off, I couldn’t see how to do this. Is there a way to log to a local file, but also send to a remote server? Eg: Log_path = /var/log/dovecot.log, @mylogserver.example.com:514 Thanks, James

3 2

Creating/Learning about services
by Dan Conway 25 Aug '21

25 Aug '21

Hello, I'm currently researching how services work within Dovecot and what scope these services are capable of. For example, I created a service as such: service myservice { executable = /home/me/executable type = worker unix_listener myservice { mode = 0666 } } When data is provided to the myservice unix socket, Dovecot appears to create a new process by executing "/home/me/executable". I found out about "status updates" through examining the logs. At first I received this: master: Error: service(myservice): Initial status notification not received in 30 seconds, killing the process What is this status notification? I found out that writing to file descriptor 5 from the executable does seem to be valid. When I write out 12 bytes I don't get an error, but when I write out 13 bytes I get the following: master: Error: service(dmon): service sent partial status update (13 bytes) What I've also noticed is that exiting 0 will cause Dovecot to spawn the process again, in what appears to be infinitely. Are there any resources/documentation that I could reference to learn more about how services work on a lower level besides just looking at the source code? Thanks.

2 2

What kind of search response time are you setting with solr full text search?
by Steve Dondley 25 Aug '21

25 Aug '21

MY SETUP: I have apache solr full text search enabled with dovecot. I have an inbox with about 40 subfolders. I'm using the roundcube web-based mail client. The find command is showing 15823 email files and apache solr reports the same number. I'm running a dedicated mail server with a 1 GB of ram. The solr machine is running on a separate machine with 4 GB ram. THE PROBLEM: When I do a full text search through all my inbox and all subfolders on a single word, search results are returned in about 10 to 15 seconds. This is better than the 40 seconds or so I'm getting when I turn off the fts and fts_solr plugins but still a little disappointing. WHAT I'D LIKE: Now, I don't expect instant search results like gmail, but getting the search results to display in less than 5 seconds would be a lot less painful that 10 to 15 seconds. WHAT I'VE TRIED: I have reindexed the emails on solr to try to speed things upit up. ANY ADVICE? Curious to know what response times others are seeing and if there is anything else I might try to speed things up. Maybe the number of subfolders is slowing things down?

6 23

JMAP Support Status
by David Klingenberg 25 Aug '21

25 Aug '21

Hello, what is the current status of JMAP support in Dovecot? Is it already supported or is there any ongoing work on it? I have found some older threads mentioning it as planned, but they are quite old and I haven't found anything new on that topic. Best Regards, David

1 0

Mail duplication on multimaster replication
by Alexey 24 Aug '21

24 Aug '21

Hello. I have 3 machines with dovecot with a circular replication: 1 → 2 → 3 → 1. As I notice there is two anomalies: 1) Mass expunge often not replicated with fast replication (default replicator mode). Replication happens only after incremental replication (full of course too, but it is not necessary). I mean, that after mail was expunged on first server via imap, I can get it with doveadm fetch on second. 2) There is some odd lines in log: doveadm(mail(a)domain.org)<10620><...>: Info: copy from INBOX: box=INBOX, uid=137704, msgid=<...>, size=2877 doveadm(mail(a)domain.org)<10620><...>: Info: expunge: box=INBOX, uid=134812, msgid=<...>, size=2877 What is the copy from INBOX to INBOX. I guess that after this actions of replicator I got a ton of duplicates of removed to Trash mails. Only IMAP is in use. All 3 servers use the same version: # dovecot --version 2.3.15 (0503334ab1) doveconf -n # 2.3.15 (0503334ab1): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.15 (e6a84e31) # OS: Linux 5.10.0-0.bpo.3-amd64 x86_64 Debian 10.10 auth_verbose = yes default_vsz_limit = 30 G doveadm_password = # hidden, use -P to show it doveadm_port = 4545 first_valid_gid = 500 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags last_valid_gid = 500 last_valid_uid = 500 log_path = /var/log/dovecot/dovecot.log mail_attribute_dict = file:%h/dovecot-attributes mail_gid = dmail mail_location = mdbox:~/mdbox mail_log_prefix = "%s(%u): " mail_plugins = " mail_log notify notify replication" mail_uid = dmail 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 { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { fts = xapian fts_autoindex = yes fts_autoindex_exclude = \Trash fts_decoder = decode2text fts_enforced = yes fts_xapian = partial=3 full=20 verbose=1 attachments=0 mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size mail_replica = tcp:10.1.1.137:4545 plugin = fts fts_xapian replication_max_conns = 100 sieve_before = /var/lib/dovecot/sieve.d/vmail/ sieve_dir = ~/sieve sieve_global_extensions = +vnd.dovecot.duplicate sieve_trace_debug = no sieve_trace_level = actions } protocols = " imap lmtp sieve sieve" service aggregator { fifo_listener replication-notify-fifo { group = dmail user = dmail } unix_listener replication-notify { group = dmail user = dmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = dmail mode = 0600 user = dmail } } service decode2text { executable = script /usr/lib/dovecot/decode2text.sh unix_listener decode2text { mode = 0666 } user = dovecot } service doveadm { inet_listener { port = 4545 } } service imap-login { inet_listener imaps { port = 993 ssl = yes } } service indexer-worker { vsz_limit = 15 G } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = dmail mode = 0660 user = dmail } } service stats { unix_listener stats-reader { group = dmail mode = 0660 user = dmail } unix_listener stats-writer { group = dmail mode = 0660 user = dmail } } ssl = required ssl_cert = # hidden, use -^^ to show it ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384 ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " mail_log notify notify replication sieve" } protocol lda { mail_plugins = " mail_log notify notify replication sieve" } protocol imap { mail_plugins = " mail_log notify notify replication fts fts_xapian" }

1 0

Problem deleting a parent folder with child folder(s)
by David Härdeman 24 Aug '21

24 Aug '21

Hi, I'm seeing some odd behavior wrt deleting a parent folder which has child/inferior folders: root@vmtest2:~# telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE LITERAL+ STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot (Debian) ready. 1 LOGIN "test(a)example.com" "foobar" 1 OK [CAPABILITY IMAP4rev1 SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE SNIPPET=FUZZY PREVIEW=FUZZY STATUS=SIZE SAVEDATE LITERAL+ NOTIFY SPECIAL-USE QUOTA] Logged in 2 LIST "" "*" * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 2 OK List completed (0.002 + 0.000 + 0.001 secs). 3 CREATE ParentA.ChildA 3 OK Create completed (0.017 + 0.000 + 0.017 secs). 4 LIST "" "*" * LIST (\Noselect \HasChildren) "." ParentA * LIST (\HasNoChildren) "." ParentA.ChildA * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 4 OK List completed (0.001 + 0.000 secs). 5 EXAMINE ParentA 5 NO Mailbox doesn't exist: ParentA (0.001 + 0.000 secs). 6 DELETE ParentA.ChildA 6 OK Delete completed (0.022 + 0.000 + 0.021 secs). 7 CREATE ParentB 7 OK Create completed (0.019 + 0.000 + 0.018 secs). 8 CREATE ParentB.ChildB 8 OK Create completed (0.009 + 0.000 + 0.008 secs). 9 LIST "" "*" * LIST (\HasChildren) "." ParentB * LIST (\HasNoChildren) "." ParentB.ChildB * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 9 OK List completed (0.001 + 0.000 secs). 10 DELETE ParentB 10 OK Delete completed (0.015 + 0.000 + 0.014 secs). 11 LIST "" "*" * LIST (\HasChildren) "." ParentB * LIST (\HasNoChildren) "." ParentB.ChildB * LIST (\HasNoChildren \UnMarked \Trash) "." INBOX.Trash * LIST (\HasNoChildren \UnMarked \Sent) "." INBOX.Sent * LIST (\HasNoChildren \UnMarked \Junk) "." INBOX.Spam * LIST (\HasNoChildren \UnMarked \Archive) "." INBOX.Read * LIST (\HasNoChildren \UnMarked \Drafts) "." INBOX.Drafts * LIST (\HasChildren) "." INBOX 11 OK List completed (0.001 + 0.000 secs). 12 EXAMINE ParentB 12 NO Mailbox doesn't exist: ParentB (0.001 + 0.000 secs). I would have expected the output from the "11 LIST..." command to be identical to that of the "4 LIST..." command, i.e. that "ParentB" would be listed as "\Noselect" in the response to "11 LIST...". I've tracked the contents of the local /var/vmail/.../Maildir folder while executing the above commands, and it appears to correspond to the expected situation (i.e. ".ParentA.ChildA" is created, then deleted, then ".ParentB" is created, then ".ParentB.ChildB" is created, and finally ".ParentB" is deleted - in other words, neither the ".ParentA" nor the ".ParentB" folders exist at the time when I issue the "4 LIST..." and "11 LIST..." commands). That "ParentB" should have a "\Noselect" flag in the last "LIST" also appears to be what's mandated by RFC3501, section 6.3.4: ... The DELETE command MUST NOT remove inferior hierarchical names. For example, if a mailbox "foo" has an inferior "foo.bar" (assuming "." is the hierarchy delimiter character), removing "foo" MUST NOT remove "foo.bar". It is an error to attempt to delete a name that has inferior hierarchical names and also has the \Noselect mailbox name attribute (see the description of the LIST response for more details). It is permitted to delete a name that has inferior hierarchical names and does not have the \Noselect mailbox name attribute. In this case, all messages in that mailbox are removed, and the name will acquire the \Noselect mailbox name attribute. ... Tested using the default dovecot package in Debian Bullseye, which is version 1:2.3.13+dfsg1-2. The file system is ext4, and Dovecot is running in a virtual (systemd-nspawn) machine for testing purposes. I've tried grepping through the git changelogs and sources, but I couldn't find anything which would appear to be relevant post-2.3.13. Any ideas? (Please CC me on replies, not subscribed) doveconf -n output ================== # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-8-amd64 x86_64 Debian 11.0 # Hostname: localhost auth_default_realm = example.com auth_mechanisms = plain login doveadm_password = # hidden, use -P to show it doveadm_port = 12345 mail_gid = vmail mail_home = /var/vmail/%d/%n mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = vmail 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 imapsieve vnd.dovecot.imapsieve namespace inbox { inbox = yes location = mailbox INBOX.Drafts { auto = subscribe special_use = \Drafts } mailbox INBOX.Read { auto = subscribe special_use = \Archive } mailbox INBOX.Sent { auto = subscribe special_use = \Sent } mailbox INBOX.Spam { auto = subscribe special_use = \Junk } mailbox INBOX.Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot.deny deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf driver = ldap } plugin { imapsieve_mailbox1_before = file:/var/vmail/sieve/global/learn-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = INBOX.Spam imapsieve_mailbox2_before = file:/var/vmail/sieve/global/learn-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = INBOX.Spam imapsieve_mailbox2_name = * quota = maildir:User quota sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /var/vmail/sieve/global/spam-global.sieve sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /usr/bin sieve_plugins = sieve_imapsieve sieve_extprograms } protocols = imap lmtp sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service doveadm { inet_listener doveadm { port = 12345 ssl = yes } } service imap-login { inet_listener imap { address = 127.0.0.1, [::1] port = 143 } inet_listener imaps { port = 993 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } service managesieve-login { inet_listener sieve { port = 4190 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = required ssl_cert = </etc/pki/realms/domain/default.crt ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap } protocol imap { mail_plugins = " notify replication quota imap_sieve imap_quota" } protocol lmtp { mail_plugins = " notify replication quota sieve" postmaster_address = postmaster(a)example.com }

1 0

Different userdb per inet_listener
by Miloslav Hůla 24 Aug '21

24 Aug '21

Hello, we are running Dovecot (2.3.4.1-5+deb10u6) with PostgreSQL passdb and userdb and for remote Postfix: auth_mechanisms = plain login inet_listener { address = 127.0.0.1 port = 12345 } It works perfectly. Now we would like to disable authentication for Postfix (SMTP), but allow it for Dovecot (IMAP & POP3). Something like "receive-only". Is there any way we can configure different passdb for mentioned inet_listener? Or is there any variable with "auth requetor name" we can use in SQL query to differentiate the result? Regards Miloslav

2 3

Director vs Proxy
by MRob 24 Aug '21

24 Aug '21

Hello, I understand director is like coordinated state database for the proxies. Is it like a special lookup resource for Dovecot proxy? If correct, makes sense proxies and directors should be deployed in pairs. But few places the docs talk about maybe different number of directors v. proxies or putting directors on different hardware from proxies. What is reason to separate director and proxy? Thank you.

1 0

Problems with anvil-auth-penalty and login_trusted_networks
by Ricardo Machini Barbosa 20 Aug '21

20 Aug '21

Hello, On my environment I have: 1 cluster of webmail servers 1 cluster of dovecot proxy dovecot servers n dovecot backend servers On my dovecot backend servers, I use the login_trusted_networks option with the IP range of my servers in the dovecot proxy cluster. But and I'm having problems where the IP addresses of the webmail cluster servers are receiving anvil-auth-penalty penalty. I tried to use in the login_trusted_networks option both the IP range of the dovecot proxy cluster and IP range of the webmail cluster, but this configuration had no effect and I still have my webmail IP's blocked. Is there anything I can do in this scenario to have the webmail cluster IP's whitelisted in anvil-auth-penalty ? Regards, Ricardo

1 0

handling public namespace (under mdbox/sdbox)
by Michal Soltys 20 Aug '21

20 Aug '21

Besides of course a "dummy" user that has admin rights to all subfloders - and handles delivery via Public/ prefix. For example using: public-dummy+Public/path/to/subfloder. But - with maildir I've been using a dedicated user that sees public namespace as its own mailbox - so all the alises/redirects go w/o Public/ prefix in such case - for example: public-dedicated+path/to/subfloder . This has been working fine with old maildir, but will this be ok for dbox mailboxes as well ?

1 0

dovecot flags lost after move/copy
by ciuga 20 Aug '21

20 Aug '21

Dear Community, I have a issue with our dovecot server ( 2.3.4.1 (f79e8e7e4) ) with maildir Flags are lost after a copy (or move), as you can see on this exemple : * Before doing anything, list detail of a mail : doveadm fetch -u XXX flags mailbox-guid f303160f6df58c5b67040200bc34b0e6 uid 46126 flags: \Seen $Labelimportant File name also contents the 'e' at the end : 1628631415.M671664P17659.mail7,S=14835,W=15111:2,Se * Copy it for testing doveadm copy -u XXX Archive mailbox INBOX mailbox-guid f303160f6df58c5b67040200bc34b0e6 uid 46126 * Fetch flag of this new mail doveadm -v fetch -u XXX flags mailbox Archive flags: \Seen File name also don't content the flags -rw------- 2 XXX users 14835 août 10 23:36 '1628631415.M671664P17659.mail7,S=14835,W=15111:2,S' Do you known how to keep flags after move and/or copy ? Thanks in advance -- Chris

1 0

dovecot 3.16 replicator Problem?
by Günther J. Niederwimmer 20 Aug '21

20 Aug '21

Hello list, I have a problem with the replicator (config) I mean it doesn't work anymore since version 3.16? How can you turn up the log level with this tool? I think the full sync is still possible to some extent. I deleted a test user who was restored after a day. Question: has something changed in the config so that the whole thing works again Thanks for a answer, -- mit freundlichen Grüßen / best regards Günther J. Niederwimmer

2 1

ssl_params error on RHEL7 FIPS enabled
by Brad Partin 19 Aug '21

19 Aug '21

All, The machine I’m running dovecot on is: RHEL7.9 3.10.0-1160.31.1.el7.x86_64 I can run Systemctl restart dovecot then status or /usr/libexec/dovecot/ssl-params and I get the following error. Info: Generating SSL parameters Fatal: ssl_iostream_generate_params(4096) failed: DH_generate_parameters(bits=512, gen=2) failed: error:0506A06E:lib(5):func(106):reason(110), error 0506A003:lib(5):func(106):reason(3) Error: child process failed with status 22784 I can generate a diffie-hellman pem with openssl dhparam -out /etc/dovecot/dh.pem 4096 But dovecot 2.2.36 does not have the option of telling it where the dh.pem file is located in the config like version 2.3 does. Is my error related to FIPS and is there a way around it? My dovecot version is: Dovecot version 2.2.36 release 8.el7 Thanks in advance to anyone willing to help out, I know it’s voluntary 🙏 Thanks, bpartin2009 Sent from my iPhone

2 1

Something obvious in my sieve?
by ＠lbutlr 19 Aug '21

19 Aug '21

I get the following error for this: line 24 is the "contains subset" line .active_sieve: line 24: error: expecting test identifier after ',' in test list, but found '('. .active_sieve: line 24: error: expecting ',' or end of test list ')', but found '{'. .active_sieve: error: parse failed. if anyof (body :contains "files transferred: 0", (header :contains "subject" "a specific subject goes here" ) { This clause produces no error if anyof (header :contains "from" "@unwanted", envelope :matches :detail "to" "extension", exists "X-Facebook" ){ What am I missing? -- "Are you pondering what I'm pondering?" "Yes Brain, but if our knees bent the other way, how would we ride a bicycle?"

2 2

Odd config problem in Debian Bullseye / dovecot 2.3.13
by Perry E. Metzger 19 Aug '21

19 Aug '21

Hi all! For a long time, I've been running this out of cron as user "perry": /usr/bin/doveadm expunge -u perry mailbox SPAM not seen before 7d After upgrading to 2.3.13 as a result of a debian upgrade, this broke. I now am suddenly getting: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 132: ssl_key: Can't open file /etc/ssl/private/ssl-cert-snakeoil.key: Permission denied Attempting things like setting "-o ssl_key=/dev/null" and the like don't work. I could of course run this as root but I'd strongly prefer not to. Anyone have any ideas? Perry

2 3

Snarf plugin retirement
by Brent Busby 19 Aug '21

19 Aug '21

I wondered if it's possible to get the Snarf plugin back, if not in the official Dovecot distribution, then at least to somehow build the plugin source on a modern release...because: Though the documented purpose for Snarf was to ease migration off of UW-IMAP, that's not the only thing it was useful for. Unfortunately, every mailreader that I've seen that can run within Emacs -- and I've tried Gnus, VM, and RMAIL -- all _require_ the use of a ~/mbox file when pulling from a local mail spool on the same machine. (This does not affect IMAP usage of those mailreaders, only local file access.) Non-Emacs mailreaders like Alpine and Mutt have sufficiently robust file-locking safety that they can work on the local mail spool in /var/spool/mail or /var/mail or what have you directly without copying your mail somewhere else first, so for Alpine and Mutt, use of ~/mbox is possible but not necessary. But it seems that for every mailreader that does run within Emacs, if the mail source is local rather than IMAP, there is no other way to operate the program than to have it copy your mail from the spool to ~/mbox. On a system where there are users who sometimes work that way, doing local mail access in Emacs, and other times use IMAP via Dovecot, you have a mess without the Snarf plugin. I realize this is a peculiar situation, so I don't expect Snarf to necessarily be put back into Dovecot. I was wondering how it might be possible to build it today though...for any out there who may use Emacs for mail most of the time...but occasionally also want Dovecot IMAP on the same machine where they're normally using an ~/mbox file for Emacs' sake. UW-IMAP may be dead...but long live GNU Emacs! -- + Brent A. Busby + "We've all heard that a million monkeys + Sr. UNIX Systems Admin + banging on a million typewriters will + University of Chicago + eventually reproduce the entire works of + James Franck Institute + Shakespeare. Now, thanks to the Internet, + Materials Research Ctr + we know this is not true." -Robert Wilensky

3 2

BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option
by ean365 17 Aug '21

17 Aug '21

Aki: I have identified a bug in the "*-O*" option of "*doveadm mailbox cryptokey password*" plugin command -- it is expecting an argument, but it is supposed to be a boolean option. I have also identified the (simple) fix to the source on github... /I am a dovecot community noob, so please forgive me if this has already been identified... (if so, I hope it gets fixed soon)... / The "-O" option in *struct doveadm_cmd_mcp_key_password* is set to expect a *STR* parameter, but it should be *BOOL*. See line 1027 in plugins/mail-crypt/doveadm-mail-crypt.c of master branch... Currently: ***DOVEADM_CMD_PARAM**(**'O'**, **"ask-old-password"**, CMD_PARAM_STR, **0**) *Should be: ***DOVEADM_CMD_PARAM**(**'O'**, **"ask-old-password"**, CMD_PARAM_BOOL, **0**)* Workaround is to specify *-O* last on command line with a dummy argument, like this: *doveadm mailbox cryptokey password -N -O ""* Also, a quick question and suggestion -- Why does the *doveadm mailbox cryptokey password* command not ask for a new password twice, with a check that both entries must match before the password is changed? The last thing we would want is to type something wrong accidentally, and change the new password to something unknown -- rendering encrypted email unrecoverable. I would like to suggest that the code in *cmd_mcp_key_password_run* be amended to include verifying password entry twice. (I am writing a simple addition to postfixadmin that changes the user's mail-crypt password whenever they use postfixadmin to change their login password. It calls *doveadm* to change the keys. I came across this bug while working through this.) Thanks for all your help! Eric **

2 5

SSL TLS SNI error certificate is empty
by silvan＠datavenia.nl 16 Aug '21

16 Aug '21

Hello, I’ve tried implementing TLS SNI for my Postfix/Dovecot setup. I have it working in Postfix, but this example for Dovecot: https://doc.dovecot.org/configuration_manual/dovecot_ssl_configuration/#wit… doesn’t seem to work for me. I’m using LetsEncrypt certificates. They work without a problem with the regular ssl_cert and ssl_key settings like this: ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/fullchain.pem ssl_key = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/privkey.pem … but as soon as I put them in local_name blocks like this: local_name datavenia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/fullchain.pem ssl_key = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/privkey.pem } local_name verovia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/verovia.nl/fullchain.pem ssl_key = </docker/rancher-active-proxy/letsencrypt/live/verovia.nl/privkey.pem } and restart dovecot I get the following error: dovecot: imap-login: Error: Failed to initialize SSL server context: Can't load SSL certificate (ssl_cert setting): The certificate is empty: user=<>, rip=213.127.63.224, lip=142.93.135.7, session=<wKjTIaLJtSXVfz/g> I have verified that the certificate paths are correct, the files have content. I’ve already checked permissions (chmodded 777 to debug), as well as the that these are actually symlinks (updated the config to point to the real files) but nothing so far seems to change anything. I have also recreated my dh.pem (4096). I’m hoping anyone has any idea where I might be going wrong. Kind regards, Silvan Output of dovecot -n: # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.11.0-25-generic x86_64 Ubuntu 21.04 ext4 # Hostname: azrael00 auth_mechanisms = plain login mail_location = maildir:/var/mail/vhosts/%d/%n mail_privileged_group = mail 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 } postmaster_address = postmaster(a)datavenia.nl <mailto:postmaster@datavenia.nl> protocols = imap 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 = 0666 user = vmail } user = dovecot } service imap-login { inet_listener imap { port = 0 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = required ssl_dh = # hidden, use -P to show it userdb { args = uid=vmail gid=vmail home=/var/mail/vhosts/%d/%n driver = static } local_name datavenia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/datavenia.nl/fullchain.pem ssl_key = # hidden, use -P to show it } local_name verovia.nl { ssl_cert = </docker/rancher-active-proxy/letsencrypt/live/verovia.nl/fullchain.pem ssl_key = # hidden, use -P to show it }

2 2

auth-worker looses MySQL connection and doesn't reconnect when MySQL/MariaDB has been restarted
by Christian Ruppert 16 Aug '21

16 Aug '21

Hey, I have MariaDB 10.5.10 and Dovecot 2.3.14.1 right now but it's broken since a few months already. I don't remember when it started and what versions I had running of both. As stated in the subject, the Dovecot auth-worker looses connection during a MySQL/MariaDB restart, which is ok so far, but it doesn't reconnect for some reason and instead all further actions fail because of it, like doveadm or IMAP login / commands etc. Aug 15 13:21:28 thor dovecot[20862]: auth-worker(24450): Warning: sqlpool(mysql): Query failed, retrying: Connection was killed Aug 15 13:21:28 thor dovecot[20862]: auth-worker(24450): Error: conn unix:auth-worker (pid=24449,uid=97): auth-worker<376>: sql(user@example.com,::1,<somesession>): Password query failed: Connection was killed Aug 15 13:21:30 thor dovecot[20862]: imap-login: Disconnected (auth service reported temporary failure): user=<user(a)example.com>, method=PLAIN, rip=::1, lip=::1, secured, session=<somesession> This repeats basically for every command / action I do until I restart dovecot or kill the auth-worker process. Both works. dovecot-sql.conf.ext: driver = mysql connect = host=/run/mysqld/mysqld.sock dbname=mail user=dovecot password=SOMEPW Steps to reproduce: Use MySQL in Dovecot Restart MySQL while Dovecot is running Do either some doveadm commands or try to login e.g. using IMAP or just try to navigate through your mailbox See errors / logs pkill -f 'dovecot/auth worker' Try doveadm etc. again Works -- Regards, Christian Ruppert

1 0

i_stream_read_memarea: assertion failed: (!stream->blocking)
by Stuart Henderson 16 Aug '21

16 Aug '21

Continuation of https://dovecot.org/pipermail/dovecot/2021-January/121235.html - I didn't get a reply to my last mail, so ended up deleting the various messages (or in some cases mailboxes) and stopped running into problems for a while, but am now seeing it again. I get "i_stream_read_memarea: assertion failed: (!stream->blocking)" when accessing some messages. Backtrace and doveconf -n below. $ doveadm -D search from abcdefghij [...] Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1177: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1177: Opened mail because: 1/1 headers not cached (first=from) (Mail has other cached fields, reset_id=1470764070) Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Looked up field guid from mail cache Aug 13 17:30:02 doveadm(sthen): Debug: Mailbox trash: UID 1178: Opened mail because: 1/1 headers not cached (first=from) (Mail has other cached fields, reset_id=1470764070) Aug 13 17:30:02 doveadm(sthen): Panic: file istream.c: line 345 (i_stream_read_memarea): assertion failed: (!stream->blocking) Abort trap (core dumped) Some other searches hitting the same message do succeed though e.g. "doveadm search mailbox trash". Somehow after various other searches trying to figure out what triggered the crash and what didn't (e.g. "doveadm -D search mailbox trash uid 1170:12000 from abc" crashed but "uid 1170:1190" didn't) it has stopped failing with that particular message, but I am still hitting it in at least one other mailbox. The messages where I'm seeing this so far seem to all be stored with lz4 (a couple of years old mostly). Any ideas? GNU gdb (GDB) 7.12.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-unknown-openbsd6.9". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from doveadm...Reading symbols from /usr/local/bin/.debug/doveadm.dbg...done. done. [New process 130792] Core was generated by `doveadm'. Program terminated with signal SIGABRT, Aborted. #0 thrkill () at /tmp/-:3 3 /tmp/-: No such file or directory. (gdb) bt #0 thrkill () at /tmp/-:3 #1 0x00000c3b2a1ee58e in _libc_abort () at /usr/src/lib/libc/stdlib/abort.c:51 #2 0x00000c3b2780f876 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:459 #3 0x00000c3b2780dc94 in fatal_handler_real (ctx=0x7f7ffffcb040, format=<error reading variable: Unhandled dwarf expression opcode 0xa3>, args=<error reading variable: Unhandled dwarf expression opcode 0xa3>) at failures.c:471 #4 0x00000c3b2780dc51 in default_fatal_handler (ctx=0x0, format=0x6 <error: Cannot access memory at address 0x6>, args=0x0) at failures.c:479 #5 0x00000c3b2780ded2 in i_panic (format=0x6 <error: Cannot access memory at address 0x6>) at failures.c:524 #6 0x00000c3b2781db26 in i_stream_read_memarea (stream=0xc3b41c94080) at istream.c:345 #7 0x00000c3b27827c2f in read_more (sstream=0xc3b41c80c00) at istream-seekable.c:152 #8 0x00000c3b27827a70 in read_from_buffer (sstream=0xc3b41c80c00, ret_r=0x7f7ffffcb188) at istream-seekable.c:207 #9 0x00000c3b27826f67 in i_stream_seekable_read (stream=0xc3b41c80c00) at istream-seekable.c:269 #10 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b41c80c80) at istream.c:326 #11 0x00000c3b2782568c in i_stream_limit_read (stream=0xc3b1097d000) at istream-limit.c:51 #12 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b1097d080) at istream.c:326 #13 0x00000c3b2781e16c in i_stream_read_copy_from_parent (istream=<optimized out>) at istream.c:400 #14 0x00000c3bc821b24a in i_stream_mail_read (stream=0xc3b41c83200) at istream-mail.c:115 #15 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b41c83280) at istream.c:326 #16 0x00000c3b2781ef0a in i_stream_read (stream=0xc3b41c83280) at istream.c:283 #17 i_stream_read_data (stream=0xc3b41c83280, data_r=0x7f7ffffcb3b8, size_r=0x7f7ffffcb3b0, threshold=1) at istream.c:760 #18 0x00000c3b277e4016 in i_stream_read_bytes (stream=0x0, data_r=<optimized out>, size_r=<optimized out>, wanted=<optimized out>) at ../../src/lib/istream.h:220 #19 message_parse_header_next (ctx=0xc3b109a4300, hdr_r=0x7f7ffffcb470) at message-header-parser.c:85 #20 0x00000c3b277dc5f2 in read_header (mstream=0xc3b41cb0800) at istream-header-filter.c:195 #21 i_stream_header_filter_read (stream=0xc3b41cb0800) at istream-header-filter.c:450 #22 0x00000c3b2781da74 in i_stream_read_memarea (stream=0xc3b41cb0880) at istream.c:326 #23 0x00000c3b2781ef0a in i_stream_read (stream=0xc3b41cb0880) at istream.c:283 #24 i_stream_read_data (stream=0xc3b41cb0880, data_r=0x7f7ffffcb568, size_r=0x7f7ffffcb560, threshold=1) at istream.c:760 #25 0x00000c3b277e4016 in i_stream_read_bytes (stream=0x0, data_r=<optimized out>, size_r=<optimized out>, wanted=<optimized out>) at ../../src/lib/istream.h:220 #26 message_parse_header_next (ctx=0xc3b1097a800, hdr_r=0x7f7ffffcb5b8) at message-header-parser.c:85 #27 0x00000c3b277e4879 in message_parse_header (input=0xc3b41cb0880, hdr_size=0x0, flags=<optimized out>, callback=0xc3bc822a3a0 <search_header>, context=0x7f7ffffcb608) at message-header-parser.c:392 #28 0x00000c3bc8229c62 in search_arg_match_text (args=0xc3b10987110, ctx=0xc3b41c89400) at index-search.c:769 #29 search_match_once (ctx=0xc3b41c89400) at index-search.c:1408 #30 0x00000c3bc822883e in search_match_next (ctx=0xc3b41c89400) at index-search.c:1516 #31 search_more_with_mail (ctx=0xc3b41c89400, mail=<optimized out>) at index-search.c:1632 #32 search_more_with_prefetching (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb770) at index-search.c:1714 #33 search_more (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb770) at index-search.c:1788 #34 0x00000c3bc82282cf in index_storage_search_next_nonblock (_ctx=0xc3b41c89400, mail_r=0x7f7ffffcb848, tryagain_r=0x7f7ffffcb7bf) at index-search.c:1816 #35 0x00000c3bc8282636 in mailbox_search_next_nonblock (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb848, tryagain_r=<optimized out>) at mail-storage.c:2290 #36 mailbox_search_next (ctx=0xc3b41c89400, mail_r=0x7f7ffffcb848) at mail-storage.c:2275 #37 0x00000c38e91eeb31 in cmd_search_box (ctx=<optimized out>, info=<optimized out>) at doveadm-mail-search.c:36 #38 cmd_search_run (ctx=<optimized out>, user=<error reading variable: Unhandled dwarf expression opcode 0xa3>) at doveadm-mail-search.c:61 #39 0x00000c38e91e3ec3 in doveadm_mail_next_user (ctx=0xc3b10980048, error_r=0x7f7ffffcb9b0) at doveadm-mail.c:462 #40 0x00000c38e91e565a in doveadm_mail_cmd_exec (ctx=0xc3b10980048, wildcard_user=0x0) at doveadm-mail.c:653 #41 0x00000c38e91e51e3 in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=<optimized out>) at doveadm-mail.c:1153 #42 0x00000c38e91f7f38 in doveadm_cmd_run_ver2 (argc=3, argv=0x7f7ffffcbc98, cctx=0x7f7ffffcbb70) at doveadm-cmd.c:575 #43 0x00000c38e91f78e5 in doveadm_cmd_try_run_ver2 ( cmd_name=<error reading variable: Unhandled dwarf expression opcode 0xa3>, argc=0, argv=0x6, cctx=0x7f7ffffcbb70) at doveadm-cmd.c:497 #44 0x00000c38e91fb636 in main (argc=6, argv=0x0) at doveadm.c:366 (gdb) frame 6 #6 0x00000c3b2781db26 in i_stream_read_memarea (stream=0xc3b41c94080) at istream.c:345 345 i_assert(!stream->blocking); (gdb) p *stream $1 = { v_offset = 0, stream_errno = 0, mmaped = false, blocking = true, closed = false, readable_fd = false, seekable = false, eof = true, real_stream = 0xc3b41c94000 $ doveconf -n # some parts replaced with <snip> # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.16 (09c29328) # OS: OpenBSD 6.9 amd64 # Hostname: naiad.spacehopper.org dsync_remote_cmd = /usr/bin/ssh <snip> first_valid_uid = 1000 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> %k login_trusted_networks = 127.0.0.1 <snip> mail_location = mdbox:~/mdbox mail_plugins = " zlib notify replication" 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 vacation-seconds spamtest spamtestplus imapsieve vnd.dovecot.imapsieve mbox_write_locks = fcntl mdbox_rotate_interval = 4 days mdbox_rotate_size = 15 M mmap_disable = yes namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { imapsieve_mailbox1_before = file:/etc/dovecot/sieve/report-spam.sieve imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_name = zSpam imapsieve_mailbox2_before = file:/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox2_causes = COPY imapsieve_mailbox2_from = zSpam imapsieve_mailbox2_name = * imapsieve_mailbox3_before = file:/etc/dovecot/sieve/report-ham.sieve imapsieve_mailbox3_causes = COPY imapsieve_mailbox3_name = zHam mail_replica = <snip> sieve = file:~/sieve;active=~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.d/ sieve_extensions = +spamtest +spamtestplus +vacation-seconds sieve_global_extensions = +vnd.dovecot.pipe sieve_pipe_bin_dir = /etc/dovecot/sieve/bin sieve_plugins = sieve_imapsieve sieve_extprograms sieve_spamtest_max_header = X-Spamd-Result: default: [[:alnum:]]+ \[-?[[:digit:]]+\.[[:digit:]]+ / (-?[[:digit:]]+\.[[:digit:]]+)\] sieve_spamtest_status_header = X-Spamd-Result: default: [[:alnum:]]+ \[(-?[[:digit:]]+\.[[:digit:]]+) / -?[[:digit:]]+\.[[:digit:]]+\] sieve_spamtest_status_type = score sieve_vacation_default_period = 6h sieve_vacation_max_period = 0 sieve_vacation_min_period = 1m } protocols = imap pop3 lmtp sieve replication_max_conns = 4 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0660 user = _postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap { vsz_limit = 512 M } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = _postfix mode = 0660 user = _postfix } vsz_limit = 512 M } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } service_count = 1 } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_alt_cert = </etc/letsencrypt/live/junkpile.org/fullchain.pem ssl_cert = </etc/letsencrypt/live/junkpile.org/fullchain.ecpem ssl_cipher_list = TLSv1.2+AEAD+ECDHE:TLSv1.2+AEAD+DHE:ECDHE-RSA-AES128-SHA ssl_curve_list = X25519:P-521:P-384 ssl_dh = # hidden, use -P to show it ssl_min_protocol = TLSv1 ssl_prefer_server_ciphers = yes userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } verbose_proctitle = yes protocol lmtp { mail_plugins = " zlib notify replication sieve" } protocol lda { mail_plugins = " zlib notify replication sieve" postmaster_address = postmaster(a)spacehopper.org } protocol imap { mail_max_userip_connections = 21 mail_plugins = " zlib notify replication imap_sieve imap_zlib" }

2 2

Enabling autoexpunge for mailboxes created by sieve rules
by Salatiel Filho 16 Aug '21

16 Aug '21

Hi everyone. I have global sieve rules that can create mailboxes automatically by using "fileinto :create some/mailbox/that/does/not/exist". The emails are delivered to dovecot using lmtp and I can see the mailboxes created just fine. Is there a way to configure all new mailboxes created by those sieve rules to automatically set to autoexpunge after 15 days ? I tried this , but it did not work. namespace { type = public separator = / prefix = mypublic/ location = maildir:/var/spool/vmail/dovecot/mail/ subscriptions = no list = children mailbox * { autoexpunge=15d } } plugin { acl = vfile } # dovecot --version 2.3.15 (0503334ab1) Thanks!

1 0

Why do so many dovecot list mails fail dmarc?
by dovecot＠ptld.com 16 Aug '21

16 Aug '21

Im trying to get my head around this problem that too many valid emails from the mailing list fail dmarc. Why when other mailing list don't seem to have the same problem? I see today it says "signature verification failed", but why? Is there a problem with protonmail's dkim key? Is the dovecot list altering the message body? Is something wrong on my server's end? The example today was an email from @protonmail.ch, and the headers were: Return-Path: <dovecot-bounces(a)dovecot.org> Delivered-To: dovecot(a)ptld.com Received: from smtp.ptld.com by host.ptld.com with LMTP id +SjBLQqiFmFSbgIAjbxwTg (envelope-from <dovecot-bounces(a)dovecot.org>) for <dovecot(a)ptld.com>; Fri, 13 Aug 2021 12:47:06 -0400 Received: from talvi.dovecot.org (talvi.dovecot.org [94.237.25.159]) by smtp.ptld.com (Postfix) with ESMTPS id 4GmTx61z3fz4l3g2 for <dovecot(a)ptld.com>; Fri, 13 Aug 2021 12:47:06 -0400 (EDT) Authentication-Results: smtp.ptld.com; dmarc=fail (p=quarantine dis=none) header.from=protonmail.ch Authentication-Results: smtp.ptld.com; spf=pass smtp.mailfrom=dovecot.org Authentication-Results: smtp.ptld.com; dkim=fail reason="signature verification failed" (1024-bit key; secure) header.d=protonmail.ch header.i=(a)protonmail.ch header.a=rsa-sha256 header.s=protonmail header.b=ivRoCAz3 Received: from talvi.dovecot.org (localhost.localdomain [127.0.0.1]) by talvi.dovecot.org (Postfix) with ESMTP id 3862D32297F; Fri, 13 Aug 2021 19:46:41 +0300 (EEST) X-Original-To: dovecot(a)dovecot.org Delivered-To: dovecot(a)dovecot.org Received: from mail-41113.protonmail.ch (mail-41113.protonmail.ch [185.70.41.113]) by talvi.dovecot.org (Postfix) with ESMTPS id 07C532E9ADB for <dovecot(a)dovecot.org>; Fri, 13 Aug 2021 19:46:37 +0300 (EEST) Date: Fri, 13 Aug 2021 16:46:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.ch; s=protonmail; t=1628873196; bh=HCYF6+sDiqNN6f9T2srf/HEjnr5eJacuoNxBWXk1XJA=; h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From; b=ivRoCAz3tXqh7Rk7Orxq6sdNGdIZ8eir4AX6OGxorOOza+XFOLQfBBIp4LfFEFV0y hV6b8z8gLmkZaEquwTyh+/Hx3lfpxts6Jvh1zpdL7YvahS2kOjSt0XikXulVgwvvxk BNmFxlLWwyVETRpgm5qsQHsNDjYb8HuYID4r1AXM= To: Aki Tuomi <aki.tuomi(a)open-xchange.com> From: Laura Smith <n5d9xq3ti233xiyif2vp(a)protonmail.ch> Subject: Re: Undefined symbols (macOS Big Sur Intel) during compiling, update Message-ID: <tQIPhn9Wc9ZCxjWv-REC0bXuE3RgBI1H69xIL0TOnDj-kWvhZXEF7ZR6BevaNCeu8AG9Ypvd7gsnbMEZFAAIkvGmNM3y3UealzoYw9HZSCg=(a)protonmail.ch> In-Reply-To: <180775367.20741.1628870488641(a)appsuite-dev-gw1.open-xchange.com> References: <CH2PR06MB6453C343867ECBFD79B73853BCF19(a)CH2PR06MB6453.namprd06.prod.outlook.com> <CH2PR06MB6453D734B09C7D6D2D807787BCFA9(a)CH2PR06MB6453.namprd06.prod.outlook.com> <180775367.20741.1628870488641(a)appsuite-dev-gw1.open-xchange.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.2 required=10.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM shortcircuit=no autolearn=disabled version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on mailout.protonmail.ch ARC-Seal: i=1; s=arc; d=dovecot.org; t=1628873197; a=rsa-sha256; cv=none; b=nuVCke6mta+nYIMyYvb2qRkTUyHSfKXEpp2vTds/ioq0kV4fyIL9oEON09yOoYcrQwci6D /EBrkZQI6nBjz592m7oslCjeNTcprIJr5QqLY6mJwW7mu+tp4rSEppIyD+r+9dbICExfFO p3j43c/m0J2acYc5pzZyJM7gLx/RBj2GURAUrP0JaX+y7moB/XQNPIJir2rE/jjNwojKCX keLRjlzOn7N4dLZxnKHgevDu6tH6gb0OzLPJO7W2IloMxdLZ/ab0PPZOj/M+BaYqnfa1Hs T4EvKhSwDjLyhjUQh7QTkmYm/FryVnIxEawEM+huOW9djJe7pIijuNFTqOR4Xg== ARC-Authentication-Results: i=1; talvi.dovecot.org; dkim=pass header.d=protonmail.ch header.s=protonmail header.b=ivRoCAz3; spf=pass (talvi.dovecot.org: domain of n5d9xq3ti233xiyif2vp(a)protonmail.ch designates 185.70.41.113 as permitted sender) smtp.mailfrom=n5d9xq3ti233xiyif2vp(a)protonmail.ch ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=dovecot.org; s=arc; t=1628873197; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=HCYF6+sDiqNN6f9T2srf/HEjnr5eJacuoNxBWXk1XJA=; b=EYR3Jyq5jrpho8glpLHD60ehlmLaGqrfdZepsfTTJtkjb0AkScBiUB0JX5hGbeyQCdeFvF zr0g/tfST7KEANMdZ0GK+rmwwSZC7LuKzszXWP+Pi5kBxsDPPU4BUivUkP3abCnGIixXfq LrEe+/bDrbMkM01wO8sJ0mZccYwURDMTJc7gFjcdSye+3FfKPZAvT9OG2aD2yQhtIVwpbv +Hg7P5v5Et/muT1E8NHZRBGOPhv4OZ/A2TcOLpafXejddNj2pRtVo8NlFzzT2PBn+KV49M nhI4ZDGk43l66nud7wMGDNdUcqYQl6CBQww+kC4ewfNbTy5D27wQwFzpVWGfFQ== Cc: "dovecot(a)dovecot.org" <dovecot(a)dovecot.org>, Beosdoc <beosdoc(a)hotmail.com> X-BeenThere: dovecot(a)dovecot.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Dovecot Mailing List <dovecot.dovecot.org> List-Unsubscribe: <https://dovecot.org/mailman/options/dovecot>, <mailto:dovecot-request@dovecot.org?subject=unsubscribe> List-Archive: <https://dovecot.org/pipermail/dovecot/> List-Post: <mailto:dovecot@dovecot.org> List-Help: <mailto:dovecot-request@dovecot.org?subject=help> List-Subscribe: <https://dovecot.org/mailman/listinfo/dovecot>, <mailto:dovecot-request@dovecot.org?subject=subscribe> Reply-To: Laura Smith <n5d9xq3ti233xiyif2vp(a)protonmail.ch> Errors-To: dovecot-bounces(a)dovecot.org Sender: "dovecot" <dovecot-bounces(a)dovecot.org>

4 3

Help to setup a Unix socket based authentication server for dovecot in Python
by Sherin A 15 Aug '21

15 Aug '21

Hi, I am building a custom server platform in which dovecot is used for imap/pop . But the default authentication mechanism is not suitable for me becuase each domain will have different system users and different location for mail storage . So I need to create a custom authentication mechanism using python . There is an option to use Key-value authentication (dict) database via socket as per https://doc.dovecot.org/configuration_manual/authentication/dict/#complete-… The above documentation link have a sample perl script too to send authentication to uri = proxy:/var/run/auth_proxy_dovecot/socket:somewhere So my question is how the inputs are send to the socket file ? in which format ? How the result return ? and in which format ? Let us say I can create a python socket program that can listen to /var/run/auth_proxy_dovecot/socket for getting the inputs from dovecot , but what is the format Is it like the following AUTH PLAIN USER test(a)myemail.com PASS mypassword I looked into the documentation and developer documentation, I am unable to see how dovecot send the data , I can see a sample perl for answering dict lookups. Any one have a python alternative for it. ? -- *Sherin Abdulkhareem* Chairman & Managing Director email Email sherin(a)sherin.in <mailto:sherin@sherin.in> mobile Mobile (+91)9496533234 office Office (+91)4716007799 *Syslint Technologies India Private Limited* First Floor,Asiatic Business Center Kazhakkootam, Trivandrum PIN-695582 India Facebook <https://facebook.com/sherin.co.in> LinkedIn <https://linkedin.com/in/sherina> Google+ <https://plus.google.com/+sherinAbdulkhareem> sherin.in <http://sherin.in>

2 1

Sieve Rule help
by Jorge Bastos 15 Aug '21

15 Aug '21

Howdy, I have an user with the rule below. Since it's discarding the match first, should it be stop there and don't redirect it to the next rule? Thanks in advanced, ### require ["date","relational","vacation"]; # rule:[xxx] if header :contains "from" "icnf.pt" { discard; } # rule:[redir] if true { redirect "jorge(a)myemail.pt"; stop; } ###

2 3

Undefined symbols (macOS Big Sur Intel) during compiling
by Beosdoc 13 Aug '21

13 Aug '21

Hi, I’m trying to compile Dovecot 2.3.15 on a Intel Mac with Big Sur and Xcode 12.5.1 with command line. I’ve compiled openSSL -1.1.1k in its own directory and pointed dovecot to use that directory. I’m getting undefined symbols during the linking (see below). I’ve been trying to figure out what’s missing but not having any luck Here’s the configure: CPPFLAGS="-I/Library/MWSrvrSrvcs/openssl/include" LDFLAGS="-L/Library/MWSrvrSrvcs/openssl/lib" ./configure --prefix=/Library/MWSrvrSrvcs/dovecot --with-ssl=openssl --with-gnu-ld --with-pgsql=auto --with-mysql=auto --with-sqlite=auto --with-gssapi=yes --with-ldap=auto --with-solr=no --with-libwrap=auto --with-ioloop=no --with-bzlib --with-zlib --with-notify=no --without-shared-libs --sysconfdir=/Library/MWSrvrSrvcs/Mail/Config --datadir=/Library/MWSrvrSrvcs/Mail/Data Here’s where it errors out: /bin/sh ../../libtool --tag=CC --mode=link gcc -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 -module -avoid-version -L/Library/MWSrvrSrvcs/openssl/lib -o libssl_iostream_openssl.la -rpath /Library/MWSrvrSrvcs/dovecot/lib/dovecot dovecot-openssl-common.lo iostream-openssl.lo iostream-openssl-common.lo iostream-openssl-context.lo istream-openssl.lo ostream-openssl.lo -lssl -lcrypto libtool: link: gcc -o .libs/libssl_iostream_openssl.so -bundle .libs/dovecot-openssl-common.o .libs/iostream-openssl.o .libs/iostream-openssl-common.o .libs/iostream-openssl-context.o .libs/istream-openssl.o .libs/ostream-openssl.o -L/Library/MWSrvrSrvcs/openssl/lib -lssl -lcrypto -g -O2 -fstack-protector-strong Undefined symbols for architecture x86_64: "_buffer_append", referenced from: _openssl_iostream_error in iostream-openssl-common.o _o_stream_ssl_sendv in ostream-openssl.o "_buffer_create_dynamic", referenced from: _o_stream_ssl_sendv in ostream-openssl.o "_buffer_delete", referenced from: _o_stream_ssl_flush_buffer in ostream-openssl.o "_buffer_free", referenced from: _o_stream_ssl_destroy in ostream-openssl.o "_buffer_get_writable_size", referenced from: _o_stream_ssl_sendv in ostream-openssl.o _o_stream_ssl_get_buffer_avail_size in ostream-openssl.o "_default_pool", referenced from: _openssl_iostream_set_error in iostream-openssl.o _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _openssl_iostream_set_log_prefix in iostream-openssl.o _openssl_iostream_free in iostream-openssl.o ... "_i_debug", referenced from: _openssl_iostream_set_error in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _openssl_info_callback in iostream-openssl.o _openssl_iostream_verify_client_cert in iostream-openssl.o _ssl_iostream_context_init_common in iostream-openssl-context.o _ssl_servername_callback in iostream-openssl-context.o ... "_i_error", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _ssl_tmp_dh_callback in iostream-openssl-context.o "_i_fatal", referenced from: _ssl_iostream_openssl_init in iostream-openssl.o _ssl_iostream_context_init_common in iostream-openssl-context.o _ssl_ctx_use_certificate_chain in iostream-openssl-context.o "_i_fatal_status", referenced from: _dovecot_openssl_malloc in dovecot-openssl-common.o _dovecot_openssl_realloc in dovecot-openssl-common.o _openssl_iostream_error in iostream-openssl-common.o "_i_info", referenced from: _openssl_iostream_verify_client_cert in iostream-openssl.o "_i_panic", referenced from: _dovecot_openssl_common_global_unref in dovecot-openssl-common.o _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_unref in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o ... "_i_strdup", referenced from: _openssl_iostream_set_error in iostream-openssl.o _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _openssl_iostream_set_log_prefix in iostream-openssl.o _openssl_iostream_verify_client_cert in iostream-openssl.o ... "_i_strdup_printf", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_alloc", referenced from: _i_stream_ssl_read in istream-openssl.o "_i_stream_close", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _i_stream_ssl_close in istream-openssl.o "_i_stream_create", referenced from: _openssl_i_stream_create_ssl in istream-openssl.o (maybe you meant: _openssl_i_stream_create_ssl) "_i_stream_free_buffer", referenced from: _i_stream_ssl_destroy in istream-openssl.o "_i_stream_get_data", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_get_data_size", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _i_stream_ssl_read in istream-openssl.o "_i_stream_get_error", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_get_fd", referenced from: _openssl_i_stream_create_ssl in istream-openssl.o "_i_stream_get_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_get_root_io", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_read_data", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_ref", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o "_i_stream_set_input_pending", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_set_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_i_stream_skip", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_i_stream_try_alloc", referenced from: _i_stream_ssl_read in istream-openssl.o "_i_stream_unref", referenced from: _openssl_iostream_free in iostream-openssl.o _o_stream_ssl_destroy in ostream-openssl.o "_i_strocpy", referenced from: _pem_password_callback in iostream-openssl-context.o "_io_stream_set_error", referenced from: _i_stream_ssl_read in istream-openssl.o _o_stream_ssl_flush in ostream-openssl.o _o_stream_ssl_flush_buffer in ostream-openssl.o "_iostream_ssl_module_init", referenced from: _ssl_iostream_openssl_init in iostream-openssl.o "_o_stream_close", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _o_stream_ssl_close in ostream-openssl.o "_o_stream_cork", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_create", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o (maybe you meant: _openssl_o_stream_create_ssl) "_o_stream_flush", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_handshake in iostream-openssl.o _plain_flush_callback in ostream-openssl.o "_o_stream_get_buffer_avail_size", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_get_buffer_used_size", referenced from: _o_stream_ssl_flush in ostream-openssl.o _o_stream_ssl_get_buffer_used_size in ostream-openssl.o "_o_stream_get_error", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_get_fd", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o "_o_stream_get_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_o_stream_ref", referenced from: _plain_flush_callback in ostream-openssl.o "_o_stream_send", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o "_o_stream_set_flush_callback", referenced from: _openssl_o_stream_create_ssl in ostream-openssl.o "_o_stream_set_flush_pending", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _o_stream_ssl_sendv in ostream-openssl.o _o_stream_ssl_flush in ostream-openssl.o _o_stream_ssl_flush_pending in ostream-openssl.o _plain_flush_callback in ostream-openssl.o "_o_stream_set_max_buffer_size", referenced from: _o_stream_ssl_set_max_buffer_size in ostream-openssl.o "_o_stream_set_name", referenced from: _openssl_iostream_create in iostream-openssl.o "_o_stream_set_no_error_handling", referenced from: _openssl_iostream_create in iostream-openssl.o "_o_stream_switch_ioloop_to", referenced from: _o_stream_ssl_switch_ioloop_to in ostream-openssl.o "_o_stream_uncork", referenced from: _openssl_iostream_bio_sync in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o "_o_stream_unref", referenced from: _openssl_iostream_free in iostream-openssl.o _plain_flush_callback in ostream-openssl.o "_pool_alloconly_create", referenced from: _ssl_iostream_context_init_common in iostream-openssl-context.o "_safe_memset", referenced from: _openssl_iostream_load_key in iostream-openssl-context.o "_ssl_iostream_check_cert_validity", referenced from: _openssl_iostream_handshake in iostream-openssl.o "_ssl_iostream_context_ref", referenced from: _openssl_iostream_create in iostream-openssl.o _openssl_iostream_change_context in iostream-openssl.o "_ssl_iostream_context_unref", referenced from: _openssl_iostream_change_context in iostream-openssl.o _openssl_iostream_free in iostream-openssl.o _openssl_iostream_context_init_client in iostream-openssl-context.o _openssl_iostream_context_init_server in iostream-openssl-context.o "_ssl_iostream_handshake", referenced from: _openssl_iostream_shutdown in iostream-openssl.o _openssl_iostream_more in iostream-openssl.o "_ssl_iostream_has_valid_client_cert", referenced from: _openssl_iostream_cert_match_name in iostream-openssl.o _openssl_iostream_get_peer_name in iostream-openssl.o "_ssl_iostream_settings_init_from", referenced from: _ssl_iostream_context_init_common in iostream-openssl-context.o "_ssl_iostream_unref", referenced from: _openssl_iostream_destroy in iostream-openssl.o _i_stream_ssl_destroy in istream-openssl.o _o_stream_ssl_destroy in ostream-openssl.o "_str_c", referenced from: _openssl_iostream_error in iostream-openssl-common.o "_str_printfa", referenced from: _openssl_iostream_error in iostream-openssl-common.o "_t_malloc0", referenced from: _openssl_iostream_get_peer_name in iostream-openssl.o _openssl_iostream_error in iostream-openssl-common.o "_t_str_new", referenced from: _openssl_iostream_error in iostream-openssl-common.o "_t_strconcat", referenced from: _openssl_iostream_create in iostream-openssl.o "_t_strdup_noconst", referenced from: _openssl_iostream_use_certificate in iostream-openssl.o _openssl_iostream_load_key in iostream-openssl-context.o _ssl_iostream_context_init_common in iostream-openssl-context.o _ssl_ctx_use_certificate_chain in iostream-openssl-context.o "_t_strdup_printf", referenced from: _dovecot_openssl_common_global_set_engine in dovecot-openssl-common.o _openssl_iostream_handle_error in iostream-openssl.o _openssl_iostream_create in iostream-openssl.o _openssl_iostream_get_security_string in iostream-openssl.o _openssl_iostream_use_certificate in iostream-openssl.o _openssl_iostream_verify_client_cert in iostream-openssl.o _openssl_cert_match_name in iostream-openssl-common.o ... ld: symbol(s) not found for architecture arm64 clang: error: linker command failed with exit code 1 (use -v to see invocation) make[3]: *** [libssl_iostream_openssl.la] Error 1 make[2]: *** [all-recursive] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Thanks Mitch

3 4

Preventing clients from trying to create folders under inbox
by Bryan K. Walton 13 Aug '21

13 Aug '21

Our Dovecot installation is configured as such: mail_location = mbox:/var/vmail/%u:DIRNAME=.mboxdata:INBOX=/var/vmail/%u/INBOX:INDEX=/var/vmail/indexes/%u This allows us to continue using mbox formatted files, storing those mbox data files in a file called .mboxdata. This allows our users to create folders and subfolders. The only exception to this is our inboxes, which are more traditional mbox files. However, we have some Outlook users that insist on trying to create subfolders of their inbox. This doesn't work, since the inbox is a file. But Outlook still does it and it causes sync issues, as there is now a subfolder under the user's inbox, but that subfolder is ONLY present in Outlook (it isn't present on the server). Is there anything that we can configure so that Dovecot instructs Outlook that it cannot attempt to create subfolders under the inbox, but allow subfolders elsewhere? Thanks! Bryan

2 1

Re: Help to setup a Unix socket based authentication server for dovecot in Python
by dovecot＠ptld.com 13 Aug '21

13 Aug '21

> So this is a single system user with single email, there are a > number of system users and email accounts, I don't need to use SQL or > LDAP or another password file. I can write python script to analyze > the logins and the mail folders including quota and send to socket file > , But how the formats as dict ? How the user input ( email/password > ) send to that unix socket ? I mean the format The documentation > doesn't say anything about it. https://doc.dovecot.org/configuration_manual/authentication/dict/ There is an example script done in perl at the bottom of the page. Maybe it can give you hints as to the format needed for a python script. On the same page it also says: When given a proxy URL the Dict backend speaks a simple protocol over a UNIX socket. The protocol is defined in src/lib-dict/dict-client.h https://github.com/dovecot/core/blob/master/src/lib-dict/dict-client.h

1 0

Help to setup a Unix socket based authentication server for dovecot in Python
by Sherin A 13 Aug '21

13 Aug '21

Hi, I am building a custom server platform in which dovecot is used for imap/pop . But the default authentication mechanism is not suitable for me becuase each domain will have different system users and different location for mail storage . So I need to create a custom authentication mechanism using python . There is an option to use Key-value authentication (dict) database via socket as per https://doc.dovecot.org/configuration_manual/authentication/dict/#complete-… The above documentation link have a sample perl script too to send authentication to uri = proxy:/var/run/auth_proxy_dovecot/socket:somewhere So my question is how the inputs are send to the socket file ? in which format ? How the result return ? and in which format ? Let us say I can create a python socket program that can listen to /var/run/auth_proxy_dovecot/socket for getting the inputs from dovecot , but what is the format Is it like the following AUTH PLAIN USER test(a)myemail.com PASS mypassword I looked into the documentation and developer documentation, I am unable to see how dovecot send the data , I can see a sample perl for answering dict lookups. Any one have a python alternative for it. ? -- *Sherin Abdulkhareem* Chairman & Managing Director email Email sherin(a)sherin.in <mailto:sherin@sherin.in> mobile Mobile (+91)9496533234 office Office (+91)4716007799 *Syslint Technologies India Private Limited* First Floor,Asiatic Business Center Kazhakkootam, Trivandrum PIN-695582 India Facebook <https://facebook.com/sherin.co.in> LinkedIn <https://linkedin.com/in/sherina> Google+ <https://plus.google.com/+sherinAbdulkhareem> sherin.in <http://sherin.in>

2 1

Sharing or not sharing the INBOX
by Stephane Magnier 13 Aug '21

13 Aug '21

Hi, I am using Dovecot and Sendmail ( as lmtp server ) I would like to consider having some users using there emails and having their "private Ibox" ( I would say as a normal use ) and some users sharing their Inbox 1) Should I consider using and configure 2 different email servers ? ( one sharing the inbox of any users, the other one, not sharing the inbox...) or I can have this config with the same email server ? 2) if so, how to tell Dovecot to get for user1 and user2 the same Inbox and (user3 and user4) Not sharing their inbox ? - ... like private emails and a tech support, which should share the same folder 3) or Can I say : User1 -> User 4 have private emails Inbox.. but user3 and user4 are also sharing the same folder /var/spool/mail/support/ for example I should admit that I don't know where to go :-( Thanks for your help

1 1

dovecot 2.3.16 fail one test on s390x, alpine linux
by Milan P. Stanić 13 Aug '21

13 Aug '21

Hi, I'm trying to upgrade dovecot from version 2.3.15 to 2.3.16 for alpine linux. Build and 'make check' pass on all alpine architectures except on s390x which is big-endian while all other are little-endian. here is the part from CI build log which fails: ------------ mail cache size corruption ........................................... : ok 0 / 10 tests failed test-mail-cache-fields.c:50: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision test-mail-cache-fields.c:65: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision test-mail-cache-fields.c:94: Assert failed: cache_field.last_used == priv->field.last_used && cache_field.decision == priv->field.decision mail cache fields read-write ......................................... : FAILED 1 / 1 tests failed make[3]: *** [Makefile:1279: check-local] Error 1 make[3]: Leaving directory '/builds/alpine/aports/main/dovecot/src/dovecot-2.3.16/src/lib-index' make[2]: *** [Makefile:1049: check-am] Error 2 make[2]: Target 'check' not remade because of errors. make[2]: Leaving directory '/builds/alpine/aports/main/dovecot/src/dovecot-2.3.16/src/lib-index' Making check in lib-storage ------------ Full log is here: https://gitlab.alpinelinux.org/alpine/aports/-/jobs/459182/raw -- Kind regards

3 8

Dovecot (>= 2.3.15) is not properly replicating Expunge commands running in a containerised environment
by A. Schulze 12 Aug '21

12 Aug '21

Hello *, migrating a mailbox setup for several tens of thousands of customers to Docker containers running on Debian VMs, we are currently observing Expunge commands not being replicated properly between two Dovecot containers. Delivering a new message into someones' inbox is replicated instantly via dsync (using TLS). However, expunging a message from the very same inbox via > doveadm expunge -u [users' email address] mailbox '*' header Message-ID [MID of the message in question] is not replicated, since a > doveadm fetch -u [users' email address] text header Message-ID [MID of the message in question] still returns the mail on the replica. Sometimes, a > doveadm replicator replicate [users' email address] fixes this, but mostly, it does not. While doing all of this, these messages are logged by Dovecot: > doveadm: Info: copy from INBOX: box=INBOX, uid=13, msgid=<[MID of the message in question]>, size=1793 > doveadm: Info: expunge: box=INBOX, uid=12, msgid=<[MID of the message in question]>, size=1793 > doveadm: Error: dsync(x): I/O has stalled, no activity for 600 seconds (last sent=handshake, last recv=handshake) > doveadm: Error: Timeout during state=slave_recv_last_common > doveadm: Error: dsync(x): I/O has stalled, no activity for 600 seconds (last sent=mailbox_delete, last recv=mailbox_delete) > doveadm: Error: Timeout during state=slave_recv_mailbox > doveadm: Error: dsync(SSL x): I/O has stalled, no activity for 600 seconds (version not received) > doveadm: Error: Timeout during state=slave_recv_handshake Unfortunately, these errors do not seem to be reproducible very well - the underlying behaviour however is. Setting > replication_sync_timeout = 2s , as mentioned in https://doc.dovecot.org/settings/plugin/replication-plugin/ (the "s" seems to be bogus, though, as Dovecot complains about an invalid timeframe given) results in these messages: > doveadm(x): Error: doveadm client disconnected before handshake: Connection closed > replicator: Panic: data stack: Out of memory when allocating 268435496 bytes > replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(backtrace_append+0x3d) [0x7ff8f55343dd] -> /usr/local/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7ff8f55344fe] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfcc6b) [0x7ff8f5540c6b] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xfcd01) [0x7ff8f5540d01] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x533e7) [0x7ff8f54973e7] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x52dcb) [0x7ff8f5496dcb] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xf6625) [0x7ff8f553a625] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x11c248) [0x7ff8f5560248] -> /usr/local/lib/dovecot/libdovecot.so.0(+0xf2655) [0x7ff8f5536655] -> /usr/local/lib/dovecot/libdovecot.so.0(buffer_write+0x67) [0x7ff8f5536867] -> dovecot/replicator(replicator_queue_push+0xe9) [0x5619b1b81a39] -> dovecot/replicator(+0x61f8) [0x5619b1b811f8] -> dovecot/replicator(+0x58ef) [0x5619b1b808ef] -> dovecot/replicator(+0x5ab2) [0x5619b1b80ab2] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7ff8f5556b99] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x131) [0x7ff8f5558101] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7ff8f5556c3c] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7ff8f5556db0] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff8f54cb7b3] -> dovecot/replicator(main+0x18f) [0x5619b1b7fc4f] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7ff8f52a309b] -> dovecot/replicator(_start+0x2a) [0x5619b1b7fd0a] > replicator: Fatal: master: service(replicator): child 175 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set /proc/sys/fs/suid_dumpable to 2) Not having observed this behaviour on physical or virtual Linux machines, we are pretty much out of ideas on what to do. https://dovecot.org/pipermail/dovecot/2019-November/117467.html sounds like being a related issue. Thank you in advance for any hints and replies. root@x:/# doveconf -n # 2.3.15 (0503334ab1): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.15 (e6a84e31) # OS: Linux 4.9.0-16-amd64 x86_64 Debian 10.10 # Hostname: x auth_cache_negative_ttl = 1 mins auth_cache_size = 10 k auth_master_user_separator = "#" auth_mechanisms = plain login auth_verbose_passwords = sha1 doveadm_password = # hidden, use -P to show it doveadm_port = 12345 first_valid_uid = 8 imap_hibernate_timeout = 1 mins imap_id_log = * lmtp_save_to_detail_mailbox = yes log_path = /dev/stderr log_timestamp = login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> %k mail_access_groups = dovecot mail_attribute_dict = file:%h/Maildir/dovecot-attributes mail_gid = mail mail_location = maildir:~/Maildir/ mail_plugins = acl quota mail_log notify replication mail_uid = 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 vacation-seconds passdb { args = /etc/dovecot/conf.d/ldap-searches/ldap.conf driver = ldap } plugin { acl = vfile acl_defaults_from_inbox = yes acl_shared_dict = file:/data/acl_shared_dict/acl_shared_dict mail_replica = tcps:x sieve_extensions = +vacation-seconds sieve_vacation_min_period = 1m } pop3_uidl_format = %f postmaster_address = x protocols = imap lmtp pop3 sieve replication_dsync_parameters = -d -N -l 60 -U service aggregator { fifo_listener replication-notify-fifo { group = mail mode = 0666 user = mail } unix_listener replication-notify { group = mail mode = 0666 user = mail } } service auth-worker { user = $default_internal_user } service auth { unix_listener /socket/dovecot/x/sasl-server { group = postfix mode = 0660 user = postfix } } service doveadm { inet_listener { port = 12345 ssl = yes } } service imap-hibernate { unix_listener imap-hibernate { user = mail } } service imap { unix_listener imap-master { group = dovecot mode = 0660 } } service lmtp { inet_listener { port = 24 ssl = yes } unix_listener /socket/dovecot/x/lmtp-server { mode = 0600 user = postfix } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { group = mail mode = 0600 user = mail } } ssl_cert = </acme/live/x/cert+intermediate.pem ssl_cipher_list = ECDHE+AESGCM:ECDHE+CHACHA20 ssl_client_ca_dir = /etc/ssl/certs/ ssl_client_cert = </acme/live/x/cert+intermediate.pem ssl_client_key = # hidden, use -P to show it ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_options = no_ticket ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/conf.d/ldap-searches/ldap.conf driver = ldap } userdb { args = /etc/dovecot/conf.d/ldap-searches/ldap-catchall.conf driver = ldap } verbose_proctitle = yes protocol imap { imap_metadata = yes mail_plugins = acl quota mail_log notify replication fts fts_squat imap_acl imap_quota mail_log notify } protocol lmtp { mail_plugins = acl quota mail_log notify replication sieve notify mail_log ssl = required ssl_ca = </etc/ssl/certs/ca-certificates.crt ssl_min_protocol = TLSv1.3 ssl_verify_client_cert = yes }

1 1

Panic: lib-sql: Too many bind args
by Joseph D Wagner 12 Aug '21

12 Aug '21

From /etc/dovecot/dovecot.conf: mail_attribute_dict = proxy::attr dict { attr = pgsql:/etc/dovecot/dovecot-attr-sql.conf.ext } From /etc/dovecot/dovecot-attr-sql.conf.ext: map { pattern = $key table = attributes fields { attr_name = $key } username_field = username value_field = attr_value } From /var/log/maillog: dovecot[51153]: dict(51395): Panic: lib-sql: Too many bind args (2) for statement: SELECT attr_name FROM attributes WHERE attr_name LIKE AND username = ? dovecot[51153]: dict(51395): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0xf8cab) [0x7f4c92274cab] -> /usr/lib64/dovecot/libdovecot.so.0(+0xf8d47) [0x7f4c92274d47] -> /usr/lib64/dovecot/libdovecot.so.0(+0x55c1d) [0x7f4c921d1c1d] -> dovecot/dict(+0x649a) [0x55921892349a] -> dovecot/dict(sql_statement_query+0x3e) [0x55921892a14e] -> dovecot/dict(+0xa296) [0x559218927296] -> /usr/lib64/dovecot/libdovecot.so.0(dict_iterate+0x23) [0x7f4c92238a23] -> dovecot/dict(+0x7860) [0x559218924860] -> dovecot/dict(+0x808c) [0x55921892508c] -> dovecot/dict(+0x8200) [0x559218925200] -> dovecot/dict(dict_command_input+0xee) [0x55921892534e] -> dovecot/dict(+0x6b9b) [0x559218923b9b] -> /usr/lib64/dovecot/libdovecot.so.0(connection_input_default+0x1b2) [0x7f4c9226fd42] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x73) [0x7f4c9228c413] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x135) [0x7f4c9228dac5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x50) [0x7f4c9228c4c0] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x7f4c9228c628] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x17) [0x7f4c92203fd7] -> dovecot/dict(main+0x185) [0x559218923895] -> /lib64/libc.so.6(__libc_start_main+0xf3) [0x7f4c91dda493] -> dovecot/dict(_start+0x2e) [0x5592189238ee] Joseph D Wagner

2 3

ACL's using SQL Backend
by Joseph D Wagner 11 Aug '21

11 Aug '21

I don't want to use vfile as the acl backend. I want to use sql, but it seems to be sparsely documented. Would this work? create table acls ( acl_name varchar(255) not null, username varchar(320) not null default '', acl_value varchar not null, constraint acls_pk primary key (acl_name, username) ); map { pattern = $key table = acls fields { acl_name = $key } username_field = username value_field = acl_value } Thanks. Joseph D. Wagner

1 0

Get Director vhostCount
by William Edwards 11 Aug '21

11 Aug '21

Hi, I would like to monitor each mail server's amount of available vhosts, so I can take action when a certain threshold is reached (e.g. adding mail servers). I'm using Dovecot 2.3.4.1 with Director. My first idea was to use the Doveadm HTTP API, but the 'directorStatus' command doesn't return the 'vhostCount' attribute (although the 'directorAdd' and 'directorUpdate' commands take it as input). My second idea was to directly connect to the 'director-admin' socket and look at the output of 'HOST-LIST'. I can find all the information I need in doveadm-connection.c, but I'm not getting the impression that we're meant to interact with the socket directly. I can't find protocol documentation, and the error message "doveadm not compatible with this server (mixed old and new binaries?)" when passing faulty input gives me the impression that the socket is only meant to be used by Dovecot directly. My third idea is to parse 'doveadm director status', but in that case I'd like to know if that output is likely to change in the future. New major versions aside, of course. Or, if anyone else has a better idea, which could very well be the case, I'd love to hear how people monitor this in the real world. TIA. -- With kind regards, William Edwards

1 1

JWT local validation
by Tomas Habarta 11 Aug '21

11 Aug '21

Hello, I have a working setup with Roundcube using OAuth2 -- introspection works without any problem, unfortunately local validation does not as tokens are missing "typ" header (seems that one is indeed optional per RFC7519 and therefore not present in the implementation in place). Is there any parameter to assert the token type or any other workaround to make local validation work as it currently fails with: oauth2 failed: Local validation failed: Cannot find 'typ' field. dovecot v2.3.15 Roundcube 1.5beta CentOS 8 Thanks, regards Tomas

2 3

Test for implicit keep within a sieve script
by Eric Durand 11 Aug '21

11 Aug '21

Hi folks, Is there a good way to test for an implicit keep in a sieve script ? At the end of my sieve script, if a message still has an implicit keep, it will end up in my inbox, and I would like to push a notification. Right now I am doing this with an ad-hoc variable that is essentially emulating the implicit keep, is there a better way to do this ? Thanks! Eric

2 1

pigeonhole-0.5.16 compilation error?
by Sylvain Robitaille 11 Aug '21

11 Aug '21

Hello Dovecot folks ... In response to the recent announcement of Dovecot-2.3.16 and pigeonhole-0.5.16, we decided to update our installation (full disclosure: this is really an update from dovecot-1.2.x in progress; we're working on a development system where we already had dovecot-2.3.x installed and running). The update of dovecot itself (compiled from source), to version 2.3.16 was quite uneventful, and I can report that it's working. We're seeing some behaviour with indexing that will need attention, but I suspect that that's a matter of configuration, and is completely unrelated to what I'm reporting. More disclosure: we've never used nor compiled pigeonhole on our systems before. We've been using procmail for decades, but are now looking into potentially switching to sieve, and as I understand it, that means installing pigeonhole. I downloaded dovecot-2.3-pigeonhole-0.5.16 at the same time that I downloaded dovecot-2.3.16, a few days ago. My build-time configure and make for pigeonhole is relatively simple, but fails to build: ./configure --prefix=/local/pkg/pigeonhole-0.5.16/root \ --sbindir=/local/pkg/pigeonhole-0.5.16/root/bin \ --localstatedir=/var \ --mandir=/local/pkg/pigeonhole-0.5.16/root/man \ --with-dovecot=/local/pkg/dovecot-CURRENT/root/lib/dovecot make -j2 "/local/pkg/dovecot-CURRENT/root/lib/dovecot" is correct for us, if I understand the installation instructions correctly: -rw-r--r-- 1 root root 1324 Aug 3 14:03 /local/pkg/dovecot-CURRENT/root/lib/dovecot/dovecot-config The make fails, while compiling sieve-extprograms-common.c: sieve-extprograms-common.c: In function ‘sieve_extprogram_run’: sieve-extprograms-common.c:639:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE: ^ sieve-extprograms-common.c:639:7: note: each undeclared identifier is reported only once for each function it appears in sieve-extprograms-common.c:641:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_FAILURE’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_FAILURE: ^ sieve-extprograms-common.c:643:7: error: ‘PROGRAM_CLIENT_EXIT_STATUS_SUCCESS’ undeclared (first use in this function) case PROGRAM_CLIENT_EXIT_STATUS_SUCCESS: ^ I decided to check against dovecot-2.3-pigeonhole-0.5.15, figuring that problems compiling that version likely would have been reported already, and sure enough I find the following difference in this file: --- ./dovecot-2.3-pigeonhole-0.5.15/src/plugins/sieve-extprograms/sieve-extprograms-common.c 2021-06-14 09:41:29.000000000 -0400 +++ ./dovecot-2.3-pigeonhole-0.5.16/src/plugins/sieve-extprograms/sieve-extprograms-common.c 2021-08-06 05:26:46.000000000 -0400 @@ -635,6 +635,14 @@ int sieve_extprogram_set_input_mail int sieve_extprogram_run(struct sieve_extprogram *sprog) { - return program_client_run(sprog->program_client); + switch (program_client_run(sprog->program_client)) { + case PROGRAM_CLIENT_EXIT_STATUS_INTERNAL_FAILURE: + return -1; + case PROGRAM_CLIENT_EXIT_STATUS_FAILURE: + return 0; + case PROGRAM_CLIENT_EXIT_STATUS_SUCCESS: + return 1; + } + i_unreached(); } ... and no mention of these PROGRAM_CLIENT_EXIT_STATUS_* constants anywhere else in the code, in either version. Have I stumbled onto an omission in the packaged sources, or is there some other package missing on my system, or is there perhaps even some other explanation for what I'm seeing? I've checked the mailing list archive and found no mention of anyone else having the same (or similar) problem, so I do think it's possible that I'm just missing something ... Thanks in advance for any insight folks might be able to give me ... -- ---------------------------------------------------------------------- Sylvain Robitaille syl(a)encs.concordia.ca Systems analyst / AITS Concordia University Faculty of Engineering and Computer Science Montreal, Quebec, Canada ----------------------------------------------------------------------

1 1

GSSAPI mail home mapping problem
by Lucas Castro 10 Aug '21

10 Aug '21

Hello, I'm trying to map authenticated kerberos users to mail_location, The problem when I set mail_home = /var/mail/virtual/domain1.zw.loca/%n works fine. But if mail_home is set as /var/mail/virtual/%d/%n I get Apr 12 19:53:18 postfix10 dovecot: imap-login: Login: user=<user0>, method=GSSAPI, rip=172.16.0.44, lip=10.16.0.220, mpid=2428, session=<iPA4Yc6/lJCsEAAs> Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Added userdb setting: plugin/=yes Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Effective uid=5000, gid=5000, home=/var/mail/virtual/domain1.zw.local =login_user=user0/user0 Right here, I can't figure out why login_user=user0/user0 Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail Now login_user=user0 Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: maildir++: root=/var/mail/virtual/domain1.zw.local =login_user=user0/user0/mail, index=, indexpvt=, control=, inbox=/var/mail/virtual/domain1.zw.local =login_user=user0/user0/mail, alt= then login_user=user0/user0/mail Apr 12 19:53:18 postfix10 dovecot: imap(user0(a)domain1.zw.local =login_user=user0)<2428><iPA4Yc6/lJCsEAAs>: Debug: Mailbox INBOX: Mailbox opened because: SELECT doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 5.10.0-7-amd64 x86_64 Debian 10.6 # Hostname: postfix10.zw.local auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/imap.keytab auth_mechanisms = gssapi auth_verbose = yes disable_plaintext_auth = no import_environment = TZ KRB5CCNAME=/etc/dovecot/imap.ticket KRB5_KTNAME=/etc/dovecot/imap.keytab mail_debug = yes mail_gid = 5000 mail_home = /var/mail/virtual/%d/%n mail_location = maildir:~/mail mail_privileged_group = mail mail_uid = 5000 namespace inbox { disabled = no inbox = yes list = 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 = type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = " imap lmtp pop3" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl = no ssl_cert = </etc/dovecot/private/dovecot.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 { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { driver = prefetch } protocol lmtp { postmaster_address = postmaster(a)zw.local } egrep -v "^$|^#" /etc/dovecot/dovecot-ldap.conf.ext uris = ldap://ldap10.zw.local auth_bind = yes sasl_bind = yes sasl_mech = gssapi sasl_realm = zw.local debug_level = -1 ldap_version = 3 base = dc=zw,dc=local user_attrs = \ =user=%{ldap:mail} \ =login_user=%{ldap:uid} user_filter = (uid=%n) pass_attrs = \ =user=%{ldap:uid},\ =k5principals=%{ldap:krbPrincipalName} pass_filter = (&(objectClass=krbPrincipalAux)(uid=%n)) -- Lucas Castro

1 1

Replication stalled by failed attemts to read attachments (mail_attachment_dir)
by Ralf Becker 09 Aug '21

09 Aug '21

I'm migrating an older Dovecot 2.2.19 installation with dbox and mail_attachment_dir to 2.3.15 with replication to a second server. The storage from the old server was rsync'ed to a new server running Dovecot 2.3.15 in a container using similar configuration with dbox and mail_attachments. That servers alone seems to run fine. As a next step I tried to establish replication to the second empty server, which is configured to use mdbox and no mail_attachment_dir, as the rest of my Dovecot servers. Looking at "doveadm replicator status '*'" some of the mailboxes replicate correct, but roughly half of them fail :( Looking a the Dovecot log with mail_debug=yes shows the replication fails on the source (server with dbox and mail_attachment_dir) typically with one of two errors: a) attachment has different size: Aug 05 15:41:58 doveadm: Debug: Mailbox INBOX: UID 30: Looked up field date.received from mail cache Aug 05 15:41:58 doveadm: Error: dsync(cdaf50f7580e): read(attachments-connector(/var/dovecot/imap/<domain>/<user>/mailboxes/INBOX/dbox-Mails/u.30)) failed: read(/var/dovecot/imap/attachments/64/4e/644ecfbc09223b8ccafc6f36aa86603cde91e76716b9b5ed0cf875bc0e183b6b4581d671f8321647be99f26d2d22088e999714529e189b25a6e7d5b428fbf5d5-1a6b701e68c9c050b10a0000838cbfe1-f86a701e68c9c050b10a0000838cbfe1-30[base64:18 b/l]) failed: Stream is larger than expected (262658 > 262657, eof=1) (last sent=mail, last recv=mail_request (EOL)) showing on the other log as: Aug 05 15:49:18 doveadm: Debug: Mailbox INBOX: UID 29: Looked up field guid from mail cache Aug 05 15:49:19 doveadm: Error: dsync(142878d8d6bf): read() failed: read(10.44.99.1) failed: dot-input stream ends without '.' line (last sent=mail_request (EOL), last recv=mail) b) attachment is not found at all: Aug 05 15:43:58 doveadm(<user>@<domain> 1441): Debug: fs-sis: fs-sis: fs-posix: open(/var/dovecot/imap/attachments/e2/0a/e20ab165f3a2e7164520341cddb06cd053dc1a87fdd5c6360b45c20a2c9d33576c8ea2daa42062f9bb0fd94f9c5f9919ad86fb11e29effe3bdf4e853fa7c0e1d-20a0b63613e6c050620b0000838cbfe1-c8d5221c39a40b61250900007dc04144-3) failed: No such file or directory Aug 05 15:43:58 doveadm(<user>@<domain> 1441): Error: dsync(cdaf50f7580e): read(attachments-connector(/var/dovecot/imap/<domain>/<user>/mailboxes/INBOX/dbox-Mails/u.3)) failed: read(/var/dovecot/imap/attachments/e2/0a/e20ab165f3a2e7164520341cddb06cd053dc1a87fdd5c6360b45c20a2c9d33576c8ea2daa42062f9bb0fd94f9c5f9919ad86fb11e29effe3bdf4e853fa7c0e1d-20a0b63613e6c050620b0000838cbfe1-c8d5221c39a40b61250900007dc04144-3[base64:19 b/l]) failed: open(/var/dovecot/imap/attachments/e2/0a/e20ab165f3a2e7164520341cddb06cd053dc1a87fdd5c6360b45c20a2c9d33576c8ea2daa42062f9bb0fd94f9c5f9919ad86fb11e29effe3bdf4e853fa7c0e1d-20a0b63613e6c050620b0000838cbfe1-c8d5221c39a40b61250900007dc04144-3) failed: No such file or directory (last sent=mail, last recv=mail_request (EOL)) That caused the replication to fail and not newer mails to be replicated for the given user and mailbox, which can be verified eg. with "doveadm mailbox status -u <user>@<domain> all inbox". The concerned mails are pretty old / the attachment itself can not be recovered, and nothing can be done about them. But how can I repair the mailbox, so all unaffected mails / attachments get replicated? I already tried multiple "doveadm force-resync -u <user>@<domain> INBOX" in case a) with no visible effect / still same error. Both Dovecot configurations are attached, in case they matter ... Ralf -- Ralf Becker EGroupware GmbH [www.egroupware.org] Handelsregister HRB Kaiserslautern 3587 Geschäftsführer Birgit und Ralf Becker Leibnizstr. 17, 67663 Kaiserslautern, Germany Telefon +49 631 31657-0

2 4

Pigeonhole Sieve Config Warning
by dovecot＠ptld.com 09 Aug '21

09 Aug '21

In the sieve plugin settings i have plugin { ... sieve_user_email = %u } Variables pages says %u = full username (e.g. user@domain) This config seems to work in practice, the email is from: the users email address. However on starting dovecot im getting a warning twice: dovecot[35893]: managesieve: Warning: sieve: Invalid address value for setting `sieve_user_email': Missing domain dovecot[35893]: master: Dovecot v2.3.8 (9df20d2db) starting up for imap, lmtp, sieve dovecot[35897]: managesieve: Warning: sieve: Invalid address value for setting `sieve_user_email': Missing domain So is there really an issue? Or just an improper warning?

2 3

v2.3.16 released
by Timo Sirainen 09 Aug '21

09 Aug '21

Hi, One interesting thing in this release is the support for configuring OAUTH2 openid-configuration element. It would be nice if IMAP clients started supporting this feature to enable OAUTH2 for all IMAP servers, not just Gmail and a few others. This would allow all kinds of new authentication methods for IMAP and improve the authentication security in general. https://dovecot.org/releases/2.3/dovecot-2.3.16.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.16.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in https://hub.docker.com/r/dovecot/dovecot <https://hub.docker.com/r/dovecot/dovecot> * Any unexpected exit() will now result in a core dump. This can especially help notice problems when a Lua script causes exit(0). * auth-worker process is now restarted when the number of auth requests reaches service auth-worker { service_count }. The default is still unlimited. + Event improvements: Added data_stack_grow event and http-client category. See https://doc.dovecot.org/admin_manual/list_of_events/ + oauth2: Support RFC 7628 openid-configuration element. This allows clients to support OAUTH2 for any server, not just a few hardcoded servers like they do now. See openid_configuration_url setting in dovecot-oauth2.conf.ext. + mysql: Single statements are no longer enclosed with BEGIN/COMMIT. + dovecot-sysreport --core supports multiple core files now and does not require specifying the binary path. + imapc: When imap_acl plugin is loaded and imapc_features=acl is used, IMAP ACL commands are proxied to the remote server. See https://doc.dovecot.org/configuration_manual/mail_location/imapc/ + dict-sql now supports the "UPSERT" syntax for SQLite and PostgreSQL. + imap: If IMAP client disconnects during a COPY command, the copying is aborted, and changes are reverted. This may help to avoid many email duplicates if client disconnects during COPY and retries it after reconnecting. - master process was using 100% CPU if service attempted to create more processes due to process_min_avail, but process_limit was already reached. v2.3.15 regression. - Using attachment detection flags wrongly logged unnecessary "Failed to add attachment keywords" errors. v2.3.13 regression. - IMAP QRESYNC: Expunging UID 1 mail resulted in broken VANISHED response, which could have confused IMAP clients. v2.3.13 regression. - imap: STORE didn't send untagged replies for \Seen changes for (shared) mailboxes using INDEXPVT. v2.3.10 regression. - rawlog_dir setting would not log input that was pipelined after authentication command. - Fixed potential infinite looping with autoexpunging. - Log event exporter: Truncate long fields to 1000 bytes - LAYOUT=index: ACL inheritance didn't work when creating mailboxes - Event filters: Unquoted '?' wildcard caused a crash at startup - fs-metawrap: Fix to handling zero sized files - imap-hibernate: Fixed potential crash at deinit. - acl: dovecot-acl-list files were written for acl_ignore_namespaces - program-client (used by Sieve extprograms, director_flush_socket) may have missed status response from UNIX and network sockets, resulting in unexpected failures.

7 16

Problem migrating POP accounts into dovecot
by Jesús Ángel del Pozo Domínguez 09 Aug '21

09 Aug '21

Hello, I am trying to migrate mailboxes from an old pop/imap server to a new one using Dovecot 2.3.15. The old server uses tpop3d and courier as POP and IMAP servers, respectively. Whereas I can migrate IMAP mailboxes without many problems, I am facing difficulties while trying to do the same with POP ones. The problem is that dsync opens simultaneous connections to the remote POP server, so the remote mailbox gets locked and dsync can not copy the messages. This is the command I am using to migrate POP mailboxes: # doveadm -Dv -c dovecot-migration.conf -o pop3c_password="*******" backup -R -u test2(a)testemail.domain.com pop3c: And these are some interesting lines from the output of the above command: Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field pop3.uidl to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: UID 1: Opened mail because: virtual size (Cache file is unusable) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: quota: quota_over_flag check: STORAGE ret=3value=3 limit=104857600 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: quota: quota_over_flag check: MESSAGE ret=4value=1 limit=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: quota: quota_over_flag=0((null)) vs currently overquota=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Locking done locally in /var/mail/testemail.domain.com/test2/.dovecot-sync.lock (local hostname=tremedal.domain.com, remote hostname=tremedal.domain.com) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain S: Namespace has location pop3c: Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field pop3.uidl to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain S: Local mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1628081654 uid_next=2 subs=no last_change=0 last_subs=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Remote mailbox tree: INBOX guid=c92f64f79f0d1ed01e6d5b314f04886c uid_validity=1628081654 uid_next=2 subs=no last_change=0 last_subs=0 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Mailbox INBOX: local=00000000000000000000000000000000/0/0, remote=c92f64f79f0d1ed01e6d5b314f04886c/0/1: mailbox not selectable yet Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : /var/mail/testemail.domain.com/test2/Mailbox/inbox doesn't exist yet, using default permissions Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : Using permissions from /var/mail/testemail.domain.com/test2/Mailbox: mode=0700 gid=default Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : /var/mail/testemail.domain.com/test2/Mailbox/inbox doesn't exist yet, using default permissions Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Namespace : Using permissions from /var/mail/testemail.domain.com/test2/Mailbox: mode=0700 gid=default Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain S: Mailbox INBOX: local=c92f64f79f0d1ed01e6d5b314f04886c/0/1, remote=00000000000000000000000000000000/0/0: mailbox not selectable yet Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field pop3.uidl to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: doveadm-sieve: Iterating Sieve mailbox attributes Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: Pigeonhole version 0.5.15 (e6a84e31) initializing Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: include: sieve_global is not set; it is currently not possible to include `:global' scripts. Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Storage path `/var/mail/testemail.domain.com/test2/sieve' not found Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Using active Sieve script path: /var/mail/testemail.domain.com/test2/.dovecot.sieve Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Using script storage path: /var/mail/testemail.domain.com/test2/sieve Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Using permissions from defaults: mode=0700 gid=-1 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Created storage directory /var/mail/testemail.domain.com/test2/sieve/tmp Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: Relative path to sieve storage in active link: sieve/ Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: sieve: file storage: sync: Synchronization active Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Import INBOX: Last common UID=0. Delayed expunges= Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: brain M: Import INBOX: Import change type=save GUID=1a82a18794d50d5de2b3f0faa8a6e27c UID=1 hdr_hash= result=Mail's UID is above local UIDNEXT - No more local mails found Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: UID 1: Opened mail because: mail stream Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field size.virtual to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox INBOX: Adding field size.physical to cache for the first time (uid=1) Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: Mailbox POP3-MIGRATION-NS/INBOX: Mailbox opened because: pop3_migration Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Looking up IP address Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Connecting to 10.0.0.104:110 Aug 04 14:54:14 dsync(test2(a)testemail.domain.com): Debug: pop3c(10.0.0.104): Authenticating as 'test2(a)testemail.domain.com' (with USER+PASS) Aug 04 14:54:22 dsync(test2(a)testemail.domain.com): Error: pop3_migration: Couldn't sync mailbox POP3-MIGRATION-NS/INBOX: Unable to open mailbox; it may be locked by another concurrent session. In the remote server I get these lines from the tpop3d log: Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [6]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:14 lmail1 tpop3d[2270]: mailspool_new_from_file: indexed mailspool /var/spool/mail/testemail.domain.com/test2 (2831 bytes) in 0.000s Aug 4 14:54:14 lmail1 tpop3d[2270]: connections_post_select: connection_read: client [6]test2(a)testemail.domain.com(10.0.0.105): closed connection Aug 4 14:54:14 lmail1 tpop3d[2270]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [5]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:14 lmail1 tpop3d[2272]: mailspool_new_from_file: indexed mailspool /var/spool/mail/testemail.domain.com/test2 (2831 bytes) in 0.000s Aug 4 14:54:14 lmail1 tpop3d[2272]: connections_post_select: connection_read: client [5]test2(a)testemail.domain.com(10.0.0.105): closed connection Aug 4 14:54:14 lmail1 tpop3d[2272]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [5]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:14 lmail1 tpop3d[2273]: mailspool_new_from_file: indexed mailspool /var/spool/mail/testemail.domain.com/test2 (2831 bytes) in 0.000s Aug 4 14:54:14 lmail1 tpop3d[1887]: authcontext_new_user_pass: began session for `test2(a)testemail.domain.com' with mysql; uid 30018, gid 8 Aug 4 14:54:14 lmail1 tpop3d[1887]: fork_child: [5]test2(a)testemail.domain.com(10.0.0.105): successfully authenticated with mysql Aug 4 14:54:22 lmail1 tpop3d[2274]: mailspool_new_from_file: failed to lock /var/spool/mail/testemail.domain.com/test2: Resource temporarily unavailable Aug 4 14:54:22 lmail1 tpop3d[2274]: dotfile_unlock(/var/spool/mail/testemail.domain.com/test2): lockfile does not have our PID Aug 4 14:54:22 lmail1 tpop3d[2274]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql Aug 4 14:54:22 lmail1 tpop3d[2273]: connections_post_select: connection_read: client [5]test2(a)testemail.domain.com(10.0.0.105): closed connection Aug 4 14:54:22 lmail1 tpop3d[2273]: authcontext_delete: finished session for `test2(a)testemail.domain.com' with mysql As you can see, in the first five lines the first connection from dsync is opened and closed. Then, the same sequence is repeated again (second connection from dsync). However, on opening the third connection, it is not closed before the fourth one is opened. On authenticating a user, the tpop3d server locks the mailbox to prevent other clients wirting to it. That is why the fourth connection fails as it can not get a lock for the mailbox: Aug 4 14:54:22 lmail1 tpop3d[2274]: mailspool_new_from_file: failed to lock /var/spool/mail/testemail.domain.com/test2: Resource temporarily unavailable Aug 4 14:54:22 lmail1 tpop3d[2274]: dotfile_unlock(/var/spool/mail/testemail.domain.com/test2): lockfile does not have our PID Could you please tell me how can I avoid this problem? I wonder why dsync opens so many connections to the remote server, and why it does not close the previous connections before opening new ones. Regards,

2 2

dsync and sieve script
by Andrea Gabellini 09 Aug '21

09 Aug '21

Hello, I'm testing the migration from and old dovecot server 2.2.24 to a new one with 2.3.15 using this command: doveadm -c /etc/dovecot/dovecot-migration.conf -o mail_fsync=never backup -x "shared" -x "shared/*" -x "dovecot/sieve" -R -T 60 -u andrea.gabellini.sc(a)telecomitalia.sm imapc: This command replicate email messages but not the sieve scripts. The esclusion of "dovecot/sieve" is mandatory because the old server is misconfigured and doesn't have a separate home and maildir location. Is dsync able to replicate the sieve scripts or I'm doing something wrong? Thanks, Andrea -- __________________________ The less a man knows the easier it is to convince him he knows it all. __________________________ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 1

doveadm Mail storage autodetection failed
by Joseph D Wagner 09 Aug '21

09 Aug '21

I have a mixture of virtual mailboxes and local mailbox. I got this: # doveadm quota get -A doveadm(nobody): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(systemd-coredump): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(polkitd): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(unbound): Error: Namespace '': Mail storage autodetection failed with home=/etc/unbound doveadm(libstoragemgmt): Error: Namespace '': Mail storage autodetection failed with home=/var/run/lsm doveadm(clevis): Error: Namespace '': Mail storage autodetection failed with home=/var/cache/clevis doveadm(cockpit-ws): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(setroubleshoot): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/setroubleshoot doveadm(sssd): Error: Namespace '': Mail storage autodetection failed with home=/ doveadm(insights): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/insights doveadm(chrony): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/chrony doveadm(cockpit-wsinstance): Error: Namespace '': Mail storage autodetection failed with home=/nonexisting doveadm(rngd): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/rngd doveadm(dovenull): Error: Namespace '': Mail storage autodetection failed with home=/usr/libexec/dovecot doveadm(opendkim): Error: Namespace '': Mail storage autodetection failed with home=/run/opendkim doveadm(vmail): Error: Namespace '': Mail storage autodetection failed with home=/home/vmail doveadm(policyd-spf): Error: Namespace '': Mail storage autodetection failed with home=/home/policyd-spf doveadm(nginx): Error: Namespace '': Mail storage autodetection failed with home=/var/lib/nginx ... plus valid and expected output here. Is there some way I can get rid of these errors while preserving local delivery for valid local mailboxes? Thanks. Config below. Joseph D. Wagner # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.8 (b7b03ba2) # OS: Linux 4.18.0-315.el8.x86_64 x86_64 CentOS Stream release 8 # Hostname: <localdomain> auth_mechanisms = plain login auth_username_format = %{if;%d;eq;<localdomain>;%Ln;%Lu} dict { attr = pgsql:/etc/dovecot/dovecot-dict-sql.conf.ext } imap_metadata = yes mail_attribute_dict = proxy::attr mail_plugins = " quota" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Archive { auto = create special_use = \Archive } mailbox "Deleted Items" { auto = create special_use = \Trash } mailbox Drafts { auto = create special_use = \Drafts } mailbox "Junk Email" { auto = create special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Items" { special_use = \Sent } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { driver = pam } plugin { imap_compress_deflate_level = 9 quota = count:User quota quota_vsizes = yes sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { port = 995 ssl = yes } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = AESGCM:CHACHA20:AESCCM:ARIA:+AES128:+ARIA128:!aNULL:!eNULL:!aDH:!kRSA ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } userdb { driver = passwd } protocol lmtp { mail_plugins = " quota sieve" } protocol imap { mail_plugins = " quota imap_quota imap_zlib" }

2 1

Block insecure connections
by Andrea Gabellini 09 Aug '21

09 Aug '21

Hello, I am writing for advice on how to deal with a problem. I have a Dovecot Proxy/Director -> Backend installation, all with version 2.3 Encryption on POP3 / IMAP connections is currently optional. I would like to set it as mandatory but despite the numerous reminders many users have not taken steps to adapt. Setting it as mandatory would mean having too many calls to support. I would therefore like to block the connection to only some of them and slowly reach my target. I can't find how and where to fit in to be able to do such a thing. At first I thought about postlogin, but the user ended up on a proxy and I can't use it. I tried to use the forwarding function on the proxy and postlogin on the backend, but I didn't succeed in the first part. In pseudo code, I would like to do this: if connection is not secured { if user is in my list { block the connection; } } Thanks in advance for any suggestions, Andrea -- __________________________ People says "more memory increases the computerspeed" and they are right: More memory Windows detects, the sooner it crashes. __________________________ TIM San Marino S.p.A. Andrea Gabellini Engineering R&D TIM San Marino S.p.A. - https://www.telecomitalia.sm Via Ventotto Luglio, 212 - Piano -2 47893 - Borgo Maggiore - Republic of San Marino Tel: (+378) 0549 886237 Fax: (+378) 0549 886188 -- Informativa Privacy Questa email ha per destinatari dei contatti presenti negli archivi di TIM San Marino S.p.A.. Tutte le informazioni vengono trattate e tutelate nel rispetto della normativa vigente sulla protezione dei dati personali (Reg. EU 2016/679). Per richiedere informazioni e/o variazioni e/o la cancellazione dei vostri dati presenti nei nostri archivi potete inviare una email a privacy(a)telecomitalia.sm. Avviso di Riservatezza Il contenuto di questa e-mail e degli eventuali allegati e' strettamente confidenziale e destinato alla/e persona/e a cui e' indirizzato. Se avete ricevuto per errore questa e-mail, vi preghiamo di segnalarcelo immediatamente e di cancellarla dal vostro computer. E' fatto divieto di copiare e divulgare il contenuto di questa e-mail. Ogni utilizzo abusivo delle informazioni qui contenute da parte di persone terze o comunque non indicate nella presente e-mail potra' essere perseguito ai sensi di legge.

2 2

doveadm pw
by Doug Hardie 07 Aug '21

07 Aug '21

mail# doveadm pw Enter new password: Retype new password: {CRYPT}$2y$05$oSB6end9V.YumJMzON7lfeOL9N8TXK6jhYqjHOEnPd1NLZ9.QNaTy I thought the default was supposed to be CRAM-MD5. I don't find anywhere I have entered CRYPT. There is one reference to it in auth-passwdfile.conf.ext, but changing that has no effect. Is this a bug, change, or my mistake? Thanks, mail# doveconf -n # 2.3.15 (0503334ab1): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.15 (e6a84e31) # OS: FreeBSD 13.0-RELEASE-p1 amd64 ufs # Hostname: mail auth_mechanisms = plain cram-md5 auth_stats = yes base_dir = /var/run/home_mail/ first_valid_gid = 0 lda_mailbox_autocreate = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k session=<%{session}> port=%a mail_gid = 2222 mail_home = /var/mail/home_mail/%n mail_location = maildir:/var/mail/home_mail/%n/Maildir mail_log_prefix = "%s(%u)[%r]<%{session}>: " mail_uid = 2222 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 { autoexpunge = 5 days special_use = \Drafts } mailbox Junk { autoexpunge = 2 days special_use = \Junk } mailbox Sent { autoexpunge = 1 weeks special_use = \Sent } mailbox "Sent Messages" { autoexpunge = 2 days special_use = \Sent } mailbox Trash { autoexpunge = 2 days special_use = \Trash } prefix = } passdb { args = scheme=CRYPT username_format=%n /usr/local/etc/dovecot/users driver = passwd-file } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size from sieve = file:/var/mail/home_mail/%n/sieve;active=/var/mail/home_mail/%n/.dovecot.sieve stats_refresh = 30 secs stats_track_cmds = yes } postmaster_address = doug(a)sermon-archive.info protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } inet_listener imaps2 { port = 998 ssl = yes } } service stats { unix_listener stats-reader { group = vmail mode = 0660 user = vmail } unix_listener stats-writer { group = vmail mode = 0660 user = vmail } } ssl_cert = </etc/ssl/certs/mail.pem ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it syslog_facility = local0 userdb { args = home=/var/mail/home_mail/%d/%n allow_all_users=yes driver = static } verbose_proctitle = yes protocol lda { mail_plugins = " sieve" } protocol imap { mail_plugins = " mail_log notify" } protocol pop3 { mail_plugins = " mail_log notify" } -- Doug

3 3

Dovecot GSSAPI Authentication problem
by Lucas Castro 06 Aug '21

06 Aug '21

Hello, I'm getting problem to setup dovecot imap/pop service authentication through Kerberos. Already read https://wiki.dovecot.org/Authentication/Kerberos. My guess is kerberos is working but something goes wrong after. The keytab and ticket ( for ldap userdb lookup ) -rw------- 1 dovecot dovecot 498 ago 3 20:20 /etc/dovecot/imap.keytab -rw------- 1 dovecot root 1503 ago 4 11:40 /etc/dovecot/imap.ticket dovecot --version 2.3.13 (89f716dc2) the dovecot setting # 2.3.13 (89f716dc2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.13 (cdd19fe3) # OS: Linux 5.10.0-7-amd64 x86_64 Debian 11.0 # Hostname: postfix10.zw.local auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/dovecot/imap.keytab auth_mechanisms = gssapi auth_username_translation = /@ import_environment = TZ KRB5CCNAME=/etc/dovecot/imap.ticket KRB5_KTNAME=/etc/dovecot/imap.keytab mail_gid = 5000 mail_home = /var/mail/virtual/%d/%n mail_location = maildir:~/mail mail_privileged_group = mail mail_uid = 5000 namespace inbox { disabled = no inbox = yes list = 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 = type = private } protocols = " imap lmtp pop3" service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } ssl_cert = </etc/dovecot/private/dovecot.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 { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol lmtp { postmaster_address = postmaster(a)zw.local } When I launch Thunderbird, mail log raise this Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: AUTH#0111#011GSSAPI#011service=pop3#011session=Q3GdfL7IvLmsEAAs#011lip=10.16.0.220#011rip=172.16.0.44#011lport=110#011rport=47548 Aug 4 13:42:23 postfix10 dovecot: auth: Debug: gssapi(?,172.16.0.44,<Q3GdfL7IvLmsEAAs>): Using all keytab entries Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client passdb out: CONT#0111#011 Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: CONT<hidden> Aug 4 13:42:23 postfix10 dovecot: auth: Debug: gssapi(user0(a)zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): security context state completed. Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client passdb out: CONT#0111#011YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvsoco75BA/W0B9tS+UmJnunUg6vIcO5wr0fzZ7iGmCpsz0K2vL/qniGISDIwF9hDXXxs79bljbZE8Yx4dujqVuTPGMtewfhDtNfRNgYGNk/z28sDz7fs/dpIMKF2FAA1m9pFjBupQ1VkGbzMYc77U Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: CONT<hidden> Aug 4 13:42:23 postfix10 dovecot: auth: Debug: gssapi(user0(a)zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): Negotiated security layer Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client passdb out: CONT#0111#011BQQF/wAMAAAAAAAAAdf8bQH///86U2L5ErmqfWFYNQA= Aug 4 13:42:23 postfix10 dovecot: auth: Debug: client in: CONT<hidden> Aug 4 13:42:23 postfix10 dovecot: auth: Error: gssapi(user0(a)domain1.zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): All password databases were skipped Aug 4 13:42:23 postfix10 dovecot: auth: Debug: auth(user0(a)domain1.zw.local,172.16.0.44,<Q3GdfL7IvLmsEAAs>): Auth request finished Aug 4 13:42:25 postfix10 dovecot: auth: Debug: client passdb out: FAIL#0111#011user=user0@domain1.zw.local#011code=temp_fail#011original_user=user0@ZW.LOCAL Aug 4 13:42:25 postfix10 dovecot: pop3-login: Debug: Ignoring unknown passdb extra field: original_user Can someone help on this? -- Lucas Castro

2 2

Pigeonhole v0.5.16 released
by Timo Sirainen 06 Aug '21

06 Aug '21

Hi, Pigeonhole release for Dovecot v2.3.16. https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t… <https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t…> https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t… <https://pigeonhole.dovecot.org/releases/2.3/dovecot-2.3-pigeonhole-0.5.16.t…> Binary packages in https://repo.dovecot.org/ <https://repo.dovecot.org/> Docker images in https://hub.docker.com/r/dovecot/dovecot <https://hub.docker.com/r/dovecot/dovecot> * .dovecot.sieve.log file now includes year in the header. * Change Sieve script result execution to delay definitive action execution to the end of a successful Sieve script execution session. This is part of an effort to solve problems with the Sieve duplicate test. As a side-effect, some rare temporary-error cases yield different results, in which partial failure is more likely.

1 0

Dovecot Debian repo instructions need updating
by Laura Smith 05 Aug '21

05 Aug '21

Re: https://doc.dovecot.org/installation_guide/dovecot_community_repositories/d… The instructions need updating for two reasons: 1) Keep up to date with Debian releases (https://wiki.debian.org/DebianReleases) i.e. remove reference to 8.0 "Jessie" and replace with 10.0 "Buster". 2) The instructions presented for key handling are not inline with Debian best-practices. As per https://wiki.debian.org/DebianRepository/UseThirdParty: "The key MUST be downloaded over a secure mechanism like HTTPS to a location only writable by root, which SHOULD be /usr/share/keyrings. The key MUST NOT be placed in /etc/apt/trusted.gpg.d or loaded by apt-key add. A sources.list entry SHOULD have the signed-by option set. The signed-by entry MUST point to a file, and not a fingerprint."

2 4

quota_grace
by dovecot＠ptld.com 05 Aug '21

05 Aug '21

There isn't much documentation on quota_grace. How would you disable quota grace? quota_grace = 0 quota_grace = 0% quota_grace = 0m quota_grace = -1 Assuming "0" isn't an "unlimited" setting?

2 1

dovecot + Procmail -> junk emails
by Stephane Magnier 03 Aug '21

03 Aug '21

Hi, Having moved from 'mbox' to 'Maildir', I'm trying to use a way to move a spam email to the Junk folder I declared the junk folder as; namespace inbox { type = private disabled = no ignore_on_failure = no list = yes subscriptions = yes #hidden = no #inbox = yes #prefix = INBOX/ mailbox "Drafts" { auto = subscribe special_use = \Drafts } mailbox "Junk" { auto = subscribe autoexpunge = 12 weeks special_use = \Junk } mailbox "Trash" { auto = no autoexpunge = 12 weeks special_use = \Trash } mailbox "Sent" { auto = subscribe special_use = \Sent } and spamassassin, very basic loadplugin Mail::SpamAssassin::Conf required_hits 5 required_score 5 rewrite_header subject [** SPAM ** ] add_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_ spf_timeout 60 rewrite_header to [Email could be SPAM ] fold_headers 0 #defang_mime 0 report_safe 0 and Procmail.. basic and I used what I found on the webpage : https://wiki.dovecot.org/procmail <https://wiki.dovecot.org/procmail> DELIVER="/usr/lib/dovecot/deliver -d $LOGNAME" SHELL="/bin/bash" SENDMAIL="/usr/sbin/sendmail -oi -t" LOGFILE="/var/log/procmail.log" DEFAULT="/var/spool2/mail/%u :0fw | /bin/spamc -s any ####################################### #:0 #* ^X-Spam-Status: Yes #$DEFAULT ####################################### :0 w * ^X-Spam-Status: Yes | $DELIVER -m Junk # ## deliver to INBOX and stop # deliver to INBOX and stop :0 w | $DELIVER But with this config, a spam email, stay into the Inbox :-( /var/log/procmail.log... doesn't exist Thanks for you help

3 3

Multiple Quota Limit Configurations
by Joseph D Wagner 02 Aug '21

02 Aug '21

Is this a valid quota rule? *:storage=0,messages=0 Or do I need to make them two separate rules? Joseph D Wagner

1 0

Timo - is the v2.3.15 GCC limitation really necessarily or it's just a bug?
by Mart Pirita 02 Aug '21

02 Aug '21

Hello. So far I have successfully built Dovecot until v2.3.14 on Centos 4-6 (yes I know, they are old, but as they are remote servers, distros can't upgraded), and sometimes I have also met compilation issues, but after highlighting them, Timo have fixed the code. Found from similar thread (Dovecot 2.3.15 compilation fails https://dovecot.org/list/dovecot/2021-June/122412.html ) that new GCC is needed. However I can't find such requirement in v2.3.15 change log. As seems that I'm not the only one with compilation issues, then @Timo - can You please fix the code so that also v2.3.15 can compiled on older distros? Compilation options: ./configure --prefix=/usr --with-ssl=openssl --with-ssldir=/etc/ssl --sysconfdir=/etc --with-pam --without-bsdauth --without-sql --without-nss --without-ldap --without-pgsql --without-mysql --without-sqlite --with-rundir=/var/run/dovecot --without-cassandra --without-lucene --without-solr --without-textcat --without-libcap --without-stemmer --disable-rpath --disable-dependency-tracking --disable-silent-rules --without-gssapi --without-cdb Compilation error: builtin-strftime -c -o test-smtp-params.o test-smtp-params.c test-smtp-params.c:29: error: unknown field `data' specified in initializer test-smtp-params.c:29: warning: missing braces around initializer test-smtp-params.c:29: warning: (near initialization for `test_params_buffer1.<anonymous>') test-smtp-params.c:30: warning: missing initializer test-smtp-params.c:30: warning: (near initialization for `test_params_buffer1.<anonymous>.<anonymous>.used') test-smtp-params.c:30: error: unknown field `used' specified in initializer test-smtp-params.c:31: warning: excess elements in struct initializer test-smtp-params.c:31: warning: (near initialization for `test_params_buffer1') test-smtp-params.c:33: error: unknown field `data' specified in initializer test-smtp-params.c:33: warning: missing braces around initializer test-smtp-params.c:33: warning: (near initialization for `test_params_buffer2.<anonymous>') test-smtp-params.c:34: warning: missing initializer test-smtp-params.c:34: warning: (near initialization for `test_params_buffer2.<anonymous>.<anonymous>.used') test-smtp-params.c:34: error: unknown field `used' specified in initializer test-smtp-params.c:35: warning: excess elements in struct initializer test-smtp-params.c:35: warning: (near initialization for `test_params_buffer2') make[3]: *** [test-smtp-params.o] Error 1 make[3]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.3.15/src/lib-smtp' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.3.15/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/redhat/BUILD/dovecot-2.3.15' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.7364 (%build) -- Mart

9 12

SQL Backend for IMAP METADATA Dictionary
by Joseph D Wagner 01 Aug '21

01 Aug '21

I've seen documentation on using a SQL backend for quota dictionary and passdb&userdb dictionary. However, I can't find any examples of a SQL backend for IMAP METADATA / mail_attributes_dict. Is this combination possible? If so, is there an example somewhere? I am unsure what data structures it's expected or how to create the map entries for it. Thanks in advance. Joseph D. Wagner

2 4

Disable authentication for submission service
by Dan Conway 01 Aug '21

01 Aug '21

Hello, Is it possible to disable the requirement for authentication on the submission service? I'm trying to require authentication for all, except for a handful of IP addresses. Thank you. ehlo test.com 250-aaa 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-DSN 250-ENHANCEDSTATUSCODES 250-SIZE 250 PIPELINING MAIL FROM:<test(a)test.com> 530 5.7.0 Authentication required.

8 11

Re: check_policy_service sends size=0
by dovecot＠ptld.com 01 Aug '21

01 Aug '21

> It sounds like a better approach would be to make Dovecot reject any > email no matter what the size is (even size=0) if a user is over > quota. I'll take further discussion to the dovecot mailing list then. If you are not aware, dovecot has by default a 10% over quota grace. So even being a couple of bytes over quota it would still accept a small message.

3 3

Re: Monitoring of director back end nodes
by Tom Sommer 31 Jul '21

31 Jul '21

On 2021-07-31 19:28, darkc0de wrote: > So dovemon for Dovecot pro, but nothing for community? https://github.com/brandond/poolmon --- Tom

1 0

Monitoring of director back end nodes
by Dan Conway 31 Jul '21

31 Jul '21

Hello, When working with director, the state of the backend nodes are not checked by Dovecot. The state always remains as "up". I understand that there are external applications documented that monitor backend nodes, and changes the state of them to "down" if they become unresponsive. The question I have is are there plans to implement something built into Dovecot that would monitor and change states based on backend "health"? Or will it always be dependent on an external service? Thanks.

3 2

quota-status fails when size=0 from Postfix
by Christoph Haas 30 Jul '21

30 Jul '21

Dear list, I've been pulling my hair out today and kindly ask you for help. I'm on Debian Bullseye with Dovecot 2.3.13 and Postfix 3.5.6. Users are stored in SQL and I want to use quotas. Basically I followed https://doc.dovecot.org/configuration_manual/quota_plugin/#quota-service With mail_debug enabled I see that the information from SQL is fetched correctly: dovecot: quota-status(test(a)bullseye.example.org)<45148><>: Debug: auth-master: userdb lookup(test(a)bullseye.example.org): auth USER input: test(a)bullseye.example.org quota_rule=*:bytes=1000 home=/var/vmail/bullseye.example.org/test uid=5000 gid=5000 So the quota rule "*:bytes=1000" is loaded as intended for testing. Before handing the email over to Dovecot through LMTP Postfix should call the quota-service (policy daemon) to determine if the user is over quota: smtpd_recipient_restrictions = \ reject_unauth_destination \ check_policy_service inet:localhost:12340 This is still by the book. What I found: - sending a test mail with Thunderbird properly returns a 5xx status (over quota) - sending a test mail with SWAKS returns DUNNO (swaks is an SMTP test tool) I have used tcpdump to look into the communication on port 12340 and the difference appears to be the "size=0" line that Postfix sends if I use SWAKS. Output from SWAKS: -> RCPT TO:<test(a)bullseye.example.org> <- 250 2.1.5 Ok However if Thunderbird sends an email it uses something like -> RCPT TO:<test(a)bullseye.example.org> SIZE=12345 If I understand the situation correctly then Postfix extracts the SIZE=… value and uses that to send it to the quota-status policy daemon. The user however is definitely over quota: $> doveadm quota get -u test(a)bullseye.example.org Quota name Type Value Limit % User quota STORAGE 1 1 100 User quota MESSAGE 1 - 0 So whatever the size of the incoming email is, it should be rejected. As quota-status returns DUNNO, Postfix will send the email to Dovecot through LMTP. And LMTP in turn does another quota check and correctly rejects the email: postfix/lmtp[45153]: 573419D6A3: to=<test(a)bullseye.example.org>, relay=iredmail-test[private/dovecot-lmtp], delay=0.08, delays=0.05/0.01/0.01/0.01, dsn=5.2.2, status=bounced (host iredmail-test[private/dovecot-lmtp] said: 552 5.2.2 <test(a)bullseye.example.org> Quota exceeded (mailbox for user is full) (in reply to end of DATA command)) Problem here is that a bounce is created and Postfix is sending backscatter. Had "quota-service" indicated that the mailbox is over quota then Postfix had instantly rejected the email without any bounce. I can also reproduce this effect by talking to the quota-status daemon: printf "recipient=test(a)bullseye.example.org\nsize=0\n\n" | nc localhost 12340 action=DUNNO printf "recipient=test(a)bullseye.example.org\nsize=10000\n\n" | nc localhost 12340 action=554 5.2.2 Quota exceeded (mailbox for user is full) Is this a feature? A bug? An evil coincidence? Thanks for reading this far. I know that this matter seems a bit complicated. But it feels like Dovecot's behavior leads to backscatter and of course I'd like to avoid that. Kindly… Christoph

4 14

[bug 2.3.15] seeing user-shared mailboxes across different storage types requires manual change to subscriptions
by Michal Soltys 29 Jul '21

29 Jul '21

Hi, While I was checking old bug I once reported (that one seems to be fixed, https://www.dovecot.org/list/dovecot/2017-January/106593.html) I discovered another issue happening under current version when user sharing his mailbox (with Maildir storage) is not visible under user using mdbox (or sdbox, also tested) - unless subscriptions file is manually adjusted (after subscribing). Consider following config: # 2.3.15 (0503334ab1): /etc/dovecot/dovecot.conf # OS: Linux 5.12.14-arch1-1 x86_64 Arch Linux btrfs # Hostname: hakai auth_debug = yes auth_mechanisms = plain login disable_plaintext_auth = no first_valid_uid = 1 listen = * mail_debug = yes mail_gid = dovecot mail_location = maildir:/var/mail1/%n/Maildir mail_plugins = acl mail_uid = dovecot namespace { inbox = yes location = prefix = separator = / type = private } namespace shared1 { inbox = no list = yes location = maildir:%%h/Maildir/ prefix = shared1/%%n/ separator = / subscriptions = no type = shared } namespace shared2 { inbox = no list = yes location = mdbox:%%h/mdbox/ prefix = shared2/%%n/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/local-maildir driver = passwd-file } passdb { args = /etc/dovecot/local-mdbox driver = passwd-file } plugin { acl = vfile acl_shared_dict = file:/var/mail-data/shared-database/shared-mailboxes.db } protocols = imap service auth { unix_listener auth-userdb { group = mail mode = 0660 user = dovecot } user = dovecot } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } user = dovecot } service imap { executable = /usr/lib/dovecot/imap } userdb { driver = prefetch } userdb { args = /etc/dovecot/local-maildir driver = passwd-file } userdb { args = /etc/dovecot/local-mdbox driver = passwd-file } protocol imap { mail_max_userip_connections = 100 mail_plugins = acl imap_acl } /etc/dovecot/local-maildir: user1:{PLAIN}test:::user1:/var/mail1/user1::userdb_mail=maildir:/var/mail1/user1/Maildir userdb_home=/var/mail1/user1 user2:{PLAIN}test:::user2:/var/mail1/user2::userdb_mail=maildir:/var/mail1/user2/Maildir userdb_home=/var/mail1/user2 /etc/dovecot/local-mdbox: user3:{PLAIN}test:::user3:/var/mail2/user3::userdb_mail=mdbox:/var/mail2/user3/mdbox userdb_home=/var/mail2/user3 There are two shared namespaces - shared1 for Maildir mailboxes and shared2 for mdbox ones. 'user1' is sharing his 'qwer' folder to user3. doveadm mailbox create -u user1 -s qwer doveadm acl add -u user1 qwer user=user3 read lookup doveadm mailbox subscribe -u user3 shared1/user1/qwer This produces subscriptions file such as: 14:44 # cat /var/mail2/user3/mdbox/subscriptions V 2 Trash shared1 user1 qwer With all that in place, 'qwer' won't be visible to user3. But if we change the 'shared1 user1 qwer' to shared1/user1/qwer - then everything will be working fine. Sharing mdbox folder to maildir user (user3 -> user1) as well as maildir to maildir (user1 -> user2) works without issues.

1 1

Shared mailbox strange behaviors
by Ervin Hegedüs 27 Jul '21

27 Jul '21

Hi there, I've set up my Dovecot instance for shared mail accounts. I'm using Debian 10, Dovecot 2.3.4. This is what I did: #namespace { # type = private # separator = / # prefix = # location = # inbox = yes #} namespace { type = shared separator = / prefix = Osztott/%%u/ location = maildir:%%h:INDEX=~/shared/%%u subscriptions = no list = yes } Note, the word "Osztott" means "Shared" in my language. The strange behaviors: 1: as you can see, the first empty namespace is commented. This is because when I restarted the Dovecot instance, it sent this message to the log: Error: namespace configuration error: Duplicate namespace prefix: "" When I commented out these lines, the error message left. Why did that happen? What's the real solution? 2: with this config, I see the shared accounts under my account, with prefix "Osztott" - but the shared account is duplicated. There are two instances with similar names. In first mailbox I see the e-mails, this is fine. But under the "regular" name of the shared mailbox, there is the other mailbox with the same name + a suffix "-1", which is empty. Why is that second maildir there? Thank you for your help, a.

1 0

Submission server and Outlook delivery notification
by Tobia Grosselle [ Terralink ] 26 Jul '21

26 Jul '21

Version: 2.3.15 (0503334ab1) Hello everyone, it seems that the delivery notification function on Outlook doesn't work with Dovecot Submission service, is expected? Will it be implemented? Thanks in advance

1 0

Dovecot and Android's Gmail app
by Jakub Filo 26 Jul '21

26 Jul '21

Hello, does anyone else have this problem with connecting to dovecot (imap) via gmail app on Android, where after removing messages, they reappear shortly after? It happens seemingly randomly, not always. -- Jakub Filo jakub(a)plantroon.com

2 1

Set vhost count in config
by William Edwards 23 Jul '21

23 Jul '21

Hi, Can we do `doveadm director update ... 100` in the on-disk config, so the vhost count is retained after the ring goes down? I could not find such an option in doveconf. -- With kind regards, William Edwards

1 0

Quick Question
by Stephane Magnier 23 Jul '21

23 Jul '21

Hi, Is there a way to transform a "*mbox*" structure ( in the folder : like /var/spool/mail/........ ) into a *maildir* structure ? I would dream to see a doveadm instruction doing something like : */doveadm /var/spool/mail/%u /var/spool2/./*...... something like this.. That would be great !! :-) Thanks and regards

2 2

dovecot and auth cache
by Maciej Milaszewski 23 Jul '21

23 Jul '21

Hi In my lab I have tested auth cache in dovecot like: 1) test auth doveadm auth login ala(a)domain.ltd pass passdb: ala(a)domain.ltd auth succeeded - user ala(a)domain.ltd is in mysql (klater galera) 2)I stop the galley cluster 3)test auth - via cache doveadm auth login ala(a)domain.ltd pass passdb: ala(a)domain.ltd auth succeeded 4)flush cache root@msmtp3:~# doveadm auth cache flush 2 cache entries flushed root@msmtp3:~# doveadm auth cache flush 0 cache entries flushed - cache is emty 5)test auth doveadm auth login ala(a)domain.ltd pass passdb: ala(a)domain.ltd auth succeeded Why 5 step give - successed ? doveconf -n # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10.9 ... auth_cache_negative_ttl = 5 mins auth_cache_ttl = 5 mins ... If I restart dovecot works correctly - I mean: doveadm auth login ala(a)domain.ltd pass not auth I dont have any idea

1 1

BDAT to DATA translation on submission service when checkpassword is involved
by Dan Conway 23 Jul '21

23 Jul '21

Hello, I'm having issues with Dovecot translating "BDAT" commands (CHUNKING) into "DATA" commands when the backend does not support it in the submission service. I use "checkpassword" to authenticate users and judging by older mailing list entries the presence of "submission_*" directives must be in place for Dovecot to translate. Even with these directives set, the translation doesn't seem to occur. checkpassword returns "director_tag=remote_smtp" (along with other fields such as nopassword=y proxy=y) which in turn sets the backend host to relay the connection to. I have a feeling the use of checkpassword has something to do with this lack of translation. If the "submission_*" directives must be in place for this translation to occur, which ones are they? Can I return these fields from checkpassword? Output of doveconf -n: # 2.3.15 (0503334ab1): /etc/dovecot/dovecot.conf # OS: Linux 4.15.0-147-generic x86_64 Ubuntu 18.04.5 LTS # Hostname: xyz auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes director_mail_servers = x.x.x.x@remote_smtp director_servers = x.x.x.x disable_plaintext_auth = no mail_log_prefix = "%Us(%u) [%r]: " passdb { args = /usr/local/bin/checkpassword driver = checkpassword } protocols = " imap pop3 submission" service anvil { client_limit = 3553 } service auth { client_limit = 3550 } service director { fifo_listener login/proxy-notify { mode = 0600 user = $default_login_user } inet_listener { address = x.x.x.x port = 9090 } unix_listener director-admin { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director inet_listener imap { address = x.x.x.x port = 143 } inet_listener imaps { address = x.x.x.x port = 993 ssl = yes } process_limit = 1000 process_min_avail = 0 service_count = 1 } service imap { process_limit = 2048 process_min_avail = 0 service_count = 1 vsz_limit = 384 M } service pop3-login { executable = pop3-login director inet_listener pop3 { address = x.x.x.x port = 110 } inet_listener pop3s { address = x.x.x.x port = 995 ssl = yes } process_limit = 450 } service pop3 { process_limit = 190 process_min_avail = 0 service_count = 1 } service submission-login { executable = submission-login director inet_listener smtp { address = x.x.x.x port = 25 } inet_listener smtps { address = x.x.x.x port = 465 ssl = yes } inet_listener submission { address = x.x.x.x port = 587 } process_limit = 2000 } ssl_cert = </etc/... ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.1 submission_backend_capabilities = submission_host = x.x.x.x submission_relay_host = x.x.x.x submission_relay_port = 465 submission_relay_ssl = smtps submission_relay_trusted = yes userdb { args = /etc/dovecot/userdb.conf driver = ldap } protocol imap { imap_logout_format = bytes=%i/%o, del=%e mail_max_userip_connections = 20 } protocol pop3 { mail_max_userip_connections = 20 pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s } protocol submission { mail_max_userip_connections = 10 } local_name *.domain.com { ssl_cert = </etc/... ssl_key = # hidden, use -P to show it }

2 1

folders and subfolders
by Stephane Magnier 22 Jul '21

22 Jul '21

Hi, Still looking for the way to create folders and sub folders.. Today, I am using "mbox", which apparently doesn't work for this ? correct ? So, I would probably need to use maildir.. ( https://doc.dovecot.org/configuration_manual/mail_location/Maildir/ ] Today, what I am using is :*mbox, *which is gather all the mailboxes of user 1, user 2 in one folder... like : mbox:/var/spool2/mail/%u 1) I suppose, that If I am using "mbox" with .. : LAYOUT=fs, I won't get these folders and subfolders ? - Correct ? 2) Instead of having : "maildir:~/Maildir " which, I suppose got each_user folder into their own home directory_ .. correct ? Can I have : *maildir:/var/spool2/mail/%u *? ( I would prefer to gather all users' mailbox into one folder like /var/spool2/mail/ ) 3) if so, *mbox:/var/spool2/mail/%u:INBOX=/var/spool/mail/%u* => can become : *maildir:/var/spool2/mail/%u:LAYOUT=fs:INBOX=/var/spool/mail/%u* What do you think ?... before trying and breaking everything :-)... if so, I will be killed Thanks and regards

5 20

Doveadm encrypt/decrypt files manually with per-user folder keys
by Ben Burk 21 Jul '21

21 Jul '21

There is an example of manually encrypting/decrypting mail processed by the mail_crypt plugin here: https://doc.dovecot.org/configuration_manual/mail_crypt_plugin/ It outlines how one would manually encrypt/decrypt messages using global keys: doveadm fs get/put crypt private_key_path=foo:public_key_path=foo2:posix:prefix=/path/to/files/root path/to/file Is there a way to accomplish this using per-user folder keys? Is there some way of making sense of the information in the dovecot-attributes file to accomplish this? -- Ben Burk BURK.TECH System Administrator

2 6

Traffic accounting
by Jesús Ángel del Pozo Domínguez 20 Jul '21

20 Jul '21

Hello, Could you please tell me whether is it possible to do traffic accounting using Dovecot 2.3.4? What I'd like to do is to collect network traffic (both in & out) for each user (both POP and IMAP traffic). Regards,

4 4

dovecot-lmtp crashing when setting lmtp_proxy=yes
by Camilo Sperberg 19 Jul '21

19 Jul '21

Hi all: We are currently in the process of setting up dovecot proxy so that we can deploy multiple machines in order to keep growing. We are trying now to create an entry point, and from there send the traffic to either the same machine or another node. For this, we are using a MySQL database with information about which server hosts which mailboxes, which turns out to be working great for sending out mail and general authentification. This was really simple to set up, kudos for that! However, whenever I want to *receive* email, I just have to enable the lmtp_proxy setting which makes the lmtp process segfault. This happens everytime as I can reliable reproduce it + get a stack trace of it. The process will crash on every incoming email. I have attached: - Complete output of dovecot-sysreport - A core dump of the crashed process Main information: Using dovecot v2.3.14 (cee3cbc0d) on Ubuntu 18.04 LTS: Linux 5.4.0-1046-gcp x86_64 Ubuntu 18.04.5 LTS. Our MTA is postfix. Logs around the crashed process: Jul 15 14:53:21 server postfix/postscreen[19402]: CONNECT from [XX.XX.XX.XX]:36411 to [10.164.0.18]:25 Jul 15 14:53:22 server postfix/dnsblog[19406]: addr XX.XX.XX.XX listed by domain dnsbl.sorbs.net as 127.0.0.6 Jul 15 14:53:27 server postfix/postscreen[19402]: PASS NEW [XX.XX.XX.XX]:36411 Jul 15 14:53:27 server postfix/smtpd[19408]: connect from mail-XX.google.com [XX.XX.XX.XX] Jul 15 14:53:28 server postfix/smtpd[19408]: B765F401DB: client= mail-XX.google.com[XX.XX.XX.XX] Jul 15 14:53:28 server postfix/cleanup[19411]: B765F401DB: message-id=< XX+5j3RpXXXXXOK7GHdiDSGSPXXXX(a)mail.gmail.com> Jul 15 14:53:29 server postfix/qmgr[1414]: B765F401DB: from=< unreal4u(a)gmail.com>, size=2815, nrcpt=1 (queue active) Jul 15 14:53:29 server dovecot: lmtp(19413): Connect from local Jul 15 14:53:29 server kernel: [1738624.857507] lmtp[19413]: segfault at 0 ip 00007fd486cd0a37 sp 00007ffc12a6c118 error 4 in libdovecot.so.0.0.0[7fd486ba1000+1aa000] Jul 15 14:53:29 server kernel: [1738624.857514] Code: eb de 90 48 85 d2 75 1e eb 33 66 0f 1f 84 00 00 00 00 00 84 c0 74 18 48 83 c7 01 48 83 c6 01 88 47 ff 48 83 ea 01 48 83 fa 01 <0f> b6 06 77 e4 c6 07 00 31 c0 80 3e 00 0f 95 c0 f7 d8 c3 b8 ff ff Jul 15 14:53:29 server dovecot: lmtp(19413): Fatal: master: service(lmtp): child 19413 killed with signal 11 (core dumped) Jul 15 14:53:29 server postfix/lmtp[19412]: B765F401DB: to=<YYY(a)YYYY.YY>, relay=ZZZ.ZZZ.ZZ[private/dovecot-lmtp], delay=0.88, delays=0.84/0.01/0.01/0.03, dsn=4.4.2, status=deferred (lost connection with ZZZ.ZZZ.ZZ[private/dovecot-lmtp] while sending RCPT TO) Jul 15 14:53:29 server postfix/smtpd[19408]: disconnect from mail-XX.google.com[XX.XX.XX.XX] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Am I missing something in the conf? Did I encounter a bug? If you need more information, please let me know. Greetings, Camilo Sperberg

2 2

Major upgrade of mail server
by Shawn Heisey 18 Jul '21

18 Jul '21

I have a mail server in AWS that is currently running Ubuntu 18. Every time I log in, I am reminded that I can upgrade to Ubuntu 20. On Ubuntu 18, the dovecot version is 3.3.0-1ubuntu0.3. On Ubuntu 20, it is 2.3.7.2-1ubuntu3. Many other packages, probably including the mysql server, would also be upgraded. Dovecot and Postfix use a postfixadmin database in mysql for users, and postfix is using dovecot-lda to deliver mail. I am using managesieve from dovecot on roundcube webmail. As far as I know, my own user is the only one with sieve scripts actually in use ... and I have a LOT of filters/folders for various mailing lists. I've been a little bit terrified of doing an upgrade, because I do have a couple of people using my mail server for real work email and I don't want to disrupt them. I'm writing today to find out what are the likely pain points I might encounter when doing this kind of major upgrade, and if there is any helpful information that can help me get through those problems. I'm hoping that it will go smoothly and everything just works. Here's the doveconf -n output: https://apaste.info/FUgF If I have been silly enough to include sensitive data from the config, I would appreciate a heads up so I know what passwords to change. I did a quick glance and didn't see anything. Thanks, Shawn

5 5

Dovecot book for a newbie
by techlists＠phpcoderusa.com 16 Jul '21

16 Jul '21

Hi, Please recommend a Dovecot book for a newbie... I have a fair amount of Linux PHP hosting experience - LAMP virtual host configurations. I'm new to BIND, Postfix, and Dovecot. I'm running Ubuntu 20.04lts. I have a test server almost working. Can send but not receive. Would like to understand more. I'm guessing it is a Zone (MX) / SSL / Client configuration issue. Thanks in advance!!

5 8

OT somewhat, how to unsubscribe?
by Christy S 16 Jul '21

16 Jul '21

Hi folks, It's been a while since I've subscribed and I don't remember how to get off the mailing list. We've changed how we're handling mail now, so dovecot is no longer being used. Can anyone help? MOst mailing lists have a blurb at the bottom with instructions but this one doesn't seem to. Thanks Christy

3 2

Dovecot geographically distributed
by Claudio Corvino 16 Jul '21

16 Jul '21

Hi, I have a single Dovecot (2.3.4.1) IMAP/LMTP server on HQ "A" and I would like to create a backup server distributed to HQ "B", two HQ are connected through an IPsec tunnel. User mailboxes (type mbox) are on NFS storage. I don't need HA, it could even be an active / passive configuration with a floating IP, but I don't know how to keep in sync the two remote NFS filesystems. I don't know if Dovecot replication is suitable for me. Thanks -- *Claudio Corvino IT Systems Administrator*

1 0

2FA/MFA with IMAP & postfix/submission
by Alex 16 Jul '21

16 Jul '21

Hi, I have a dovecot-2.3.13 system on fedora34 with a few hundred IMAP4 accounts, as well as postfix users using submission. Clients are using primarily Outlook on Windows and old squirrelmail. Are there multi-factor options available? If it is not available, do you have any recommendations on where I should look to do this? All of the links related to this topic appear to be very old, or limited to Linux PAM users.

12 19

function for whitelisting IPs
by White, Daniel E. (GSFC-770.0)[NICS] 16 Jul '21

16 Jul '21

Sebastian, Do you have any examples of such a function and how/where it is used ? -----Original Message----- From: dovecot <dovecot-bounces(a)dovecot.org> on behalf of Sebastian <sebastian(a)sebbe.eu> Reply-To: Dovecot Mailing List <dovecot(a)dovecot.org> Date: Thursday, July 15, 2021 at 01:19 To: 'Mailing List' <dovecot(a)dovecot.org> Subject: [EXTERNAL] Sv: 2FA/MFA with IMAP & postfix/submission Main problem is that not many clients do natively support multifactor. Some clients, do popup a login dialog if the server rejects the password as invalid, which can be used to create a "cheaty variant" of multifactor, but some clients just popup an error dialog and tell the user to just correct password in settings. Some clients even go as long as requiring the user to delete the account with wrong password and set up a new connection. So no, it cannot be relied upon. I have a better idea: Have a function for whitelisting IPs, possible /24's or similiar, where a login to roundcube or other webmail client (with 2FA) will add the IP onto a whitelist for that account. Or perhaps, just "set" the country of the account based on GeoIP. When an account tries to login via IMAP or SMTP, you just check if IP and/or GeoIP country is right, and reject the login as invalid if so not. The only thing a client needs to do to get his IMAP or SMTP client to work again if it stops working, is to login once via the web client. -----Ursprungligt meddelande----- Från: dovecot-bounces(a)dovecot.org <dovecot-bounces(a)dovecot.org> För Alex Skickat: den 15 juli 2021 02:10 Till: dovecot(a)dovecot.org Ämne: 2FA/MFA with IMAP & postfix/submission Hi, I have a dovecot-2.3.13 system on fedora34 with a few hundred IMAP4 accounts, as well as postfix users using submission. Clients are using primarily Outlook on Windows and old squirrelmail. Are there multi-factor options available? If it is not available, do you have any recommendations on where I should look to do this? All of the links related to this topic appear to be very old, or limited to Linux PAM users.

7 10

TLS Security
by Stefan Schumacher 15 Jul '21

15 Jul '21

Hi, I wish to build a new secure email server. It seems I am on the right way – at least I get no more error messages for Postfix – but Dovecot is still making trouble. I am using Dovecot 1:2.3.4.1-5+deb10u6 and I am using ISPconfig 3.25 to do the rough configuring and nano and whats left of my brain to do the finer details. Lets start with what I added to conf.d/10-ssl.conf ssl_cert = </etc/letsencrypt/live/servername/fullchain.pem ssl_key = </etc/letsencrypt/live/servername/privkey.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aR$ ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 ssl_min_protocol = TLSv1.2 As you can see, I clearly do not want to use TLS before v1.2. I think this is not unreasonable in the year 2021. Now, after the changes I ran Kali (I use it to verify the results of my experiments) and - this is a mailing list, so no screenshots: It says: SSL/TLS Deprecated TLS v1.0 and TLS v1.1 Detection. I get this for the ports 143, 110, 993 and 995. I thought I had done everything one could to disable old TLS-Versions. What am I doing wrong? Yours sincerely Stefan Schumacher

4 6

AW: TLS Security
by Stefan Schumacher 15 Jul '21

15 Jul '21

Hi Justina, Kali tools is of course extremly unprecise. Excuse me, I had a long stressful day and wanted to get this out before the end of the Day. Kali is a rolling release and I keep it up to date by upgrading every few days. I also update the feeds. What I actually use for security scans is the former OpenVAS, which now has been relegated to being a part of the Community Edition of the Greenbone suite. You have seen the values I have in Dovecot. What follows now are my settings in the postfix main.cf. As you can clearly see it, it should prevent connections from TLS below 1.2. Dovecot is of course not very fresh because it's Debian 10 and Debian 11 is just around the corner (a few days). These are the settings of my postfix main.cf. I am very tempted to grab an Image of Debian 11 and install ISPConfig and my Dovecot and Postfix settings there. I am of course open to any other suggestions. A the moment I consider to install a new Bullseye RC2 and then put my configuration on it. I am of course open for any other suggestions. Yours sincerely Stefan smtpd_use_tls = yes smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_tls_eecdh_grade = strong smtpd_tls_protocols= !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_mandatory_protocols= !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtpd_tls_mandatory_ciphers = high smtpd_tls_security_level=may smtpd_tls_ciphers = high tls_preempt_cipherlist = yes smtpd_tls_mandatory_exclude_ciphers = aNULL, MD5 , DES, ADH, RC4, PSD, SRP, 3DES, eNULL smtpd_tls_exclude_ciphers = aNULL, MD5 , DES, ADH, RC4, PSD, SRP, 3DES, eNULL smtp_tls_mandatory_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 smtp_tls_protocols = !SSLv2, !SSLv3, !TLSv1, !TLSv1.1 ________________________________ Von: justina colmena ~biz <justina(a)colmena.biz> Gesendet: Mittwoch, 14. Juli 2021 18:50 An: dovecot(a)dovecot.org <dovecot(a)dovecot.org>; Stefan Schumacher <s.schumacher(a)consulting1x1.com> Betreff: Re: TLS Security Interesting. Assuming your "Kali" tools are in fact up to date to test with newer protocols TLS1.2+, is Dovecot compiled against a recent version of the OpenSSL or GnuTLS library or whatever it uses to support the newer TLS protocols? Definitely an outdated cipher issue, on Postfix as well as Dovecot.... On July 14, 2021 6:55:19 AM AKDT, Stefan Schumacher <s.schumacher(a)consulting1x1.com> wrote: Hi, I wish to build a new secure email server. It seems I am on the right way – at least I get no more error messages for Postfix – but Dovecot is still making trouble. I am using Dovecot 1:2.3.4.1-5+deb10u6 and I am using ISPconfig 3.25 to do the rough configuring and nano and whats left of my brain to do the finer details. Lets start with what I added to conf.d/10-ssl.conf ssl_cert = </etc/letsencrypt/live/servername/fullchain.pem ssl_key = </etc/letsencrypt/live/servername/privkey.pem ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aR$ ssl_protocols = !SSLv2 !SSLv3 !TLSv1 !TLSv1.1 ssl_min_protocol = TLSv1.2 As you can see, I clearly do not want to use TLS before v1.2. I think this is not unreasonable in the year 2021. Now, after the changes I ran Kali (I use it to verify the results of my experiments) and - this is a mailing list, so no screenshots: It says: SSL/TLS Deprecated TLS v1.0 and TLS v1.1 Detection. I get this for the ports 143, 110, 993 and 995. I thought I had done everything one could to disable old TLS-Versions. What am I doing wrong? Yours sincerely Stefan Schumacher -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

1 0

Verifying replication
by Arnold Hendriks 15 Jul '21

15 Jul '21

Dear Dovecot people, I've set up Dovecot replication a couple of years ago. I'm watching the general server health and having Nagios check doveadm replicator status regularly. I'm seeing accounts replicating, disk space usage obviously shows that things work in principle, however, I still wonder whether the replication actually works properly. Accounts I check work, but 1-5% of the messages could easily be missing without me noticing it. These servers have I think about 50K accounts (a lot of them dormant) and between 1 to 2TB of mail. I'm trying to get some more confidence as to whether replication is actually working properly and whether I'm not missing anything that will burn me if I ever have to 'fallback'. Has anyone ever done some verification outside of simply watching doveadm replication stats, to see if they are missing anything ? Eg, I could imagine a process that generates a list of accounts, and then generates hashes on both sides of the replication for each mailbox folder. If the hashes match, the folder gets removed from the list, and once all folders are removed, the account gets removed. Iterating the account list should finally reduce it to 0, or a few extremely high traffic accounts which can be checked manually or be ignored. But I'm trying to avoid reinventing the wheel. Has anyone done anything like this, or can suggest a different approach? With regards, Arnold Hendriks

1 1

Forcing replication - difference is a 0x0D 0x0D 0xA sequence?
by Arnold Hendriks 15 Jul '21

15 Jul '21

I've found a few mailboxes on my system that were being replicated where the mailboxes are not in sync. On server 1 I see: dovecot1:/# doveadm fetch -u s0000000 "size.physical size.virtual" mailbox-guid c92f64f79f0d1ed01e6d5b314f04886c uid 115 size.physical: 1815 size.virtual: 1843 On server 2 I see: dovecot2:/# doveadm fetch -u s0000000 "size.physical size.virtual" mailbox-guid c92f64f79f0d1ed01e6d5b314f04886c uid 115 size.physical: 1805 size.virtual: 1833 Running ' doveadm replicator replicate -f s0000000 "*" ' does not fix the issue. I've compared the mails and the difference appears to be that the primary server (where the mail comes in) has a few occurences of "0D 0D 0A" (hex) which on the replicated server looks like "0D 0A". (ie, \r\r\n was replicated as \r\n ?) Is there a way to force these two messages to be in sync again ? Is the \r\r\n being replicated as \r\n a known issue ? (I'm not sure if I could replicate this, this message dates back to 2007 so probably wasn't even received originally on this server. Replication was configured much later than 2007)

1 0

folders management
by Stephane Magnier 15 Jul '21

15 Jul '21

Hi, Sorry to ask you , maybe a silly question :-) On my folders' architecture, I can see all the folders underneeth each other fodler1 folder2 etc.... I would like to have the possibility to have _folders INTO folders_, like Folder1 Folder2 .......folder 21 ......folder 22 Folders 3 Apparently, this is link to this déclaration :__*_mbox_:/var/spool2/mail/%u. *Is that correct ? is that the "mbox" declaration? or Am I complety wrong ? If I have need to change...I have to change it for what ? * Can I use this new structure with NFS shares ? * What is the backside of it ? Now, if I make this modification.. on an existing dovecot system... , Will it make a true disaster ? or I can change the declaration easily? Thanks and regards,

2 1

Restrict number of mail moved/copied
by Amol Kulkarni 14 Jul '21

14 Jul '21

Hello, I need to restrict number of mail moved/copied by end user using imap in operation. Is there any configuration for that ? Thanks and regards, Amol

1 0

dsync I/O Stalled
by Paolo Daniele 14 Jul '21

14 Jul '21

Hi guys, i've a strange problem between 2 servers. It happened after a changing on our network core routing infrastructure. We've moved to Juniper network and eBGP and iBGP of our server. One of this server is behind a firewall and communicate with another server in another country to sync our emails. Doveadmin replica seems to be fine, but sometimes i get this error message: dsync-server(aaaaa(a)bbb.bb): Error: Timeout during state=sync_mails (send=done recv=mails) It seems like the remote server has troubles to reach our local server but if i do a stupid ping i'm not losing anything. Maybe is there something am i missing? I thought that it could be related to a MTU problem but i'm not so sure and i've increased MTU on the routers involved in routing process without success. I wa missing that both servers are behind a load balancer wich is in our local DC. Can you give me some hints? Regards, Paolo -- Paolo Daniele Intendo s.r.l. E-mail: paolo.daniele(a)intendo.it Business Unit TLCWEB Tel.: +39 0968 430786 Via Coschi, 11 Skype: paolo_daniele1 88046 - Lamezia Terme, Cz Web: http://www.tlcweb.it Italia Web: http://www.intendo.it

2 2

Potential bug: Assumption that POSIX time functions do not clobber errno
by Florian Weimer 13 Jul '21

13 Jul '21

We accidentally ran the dovecot 2.3.14 testsuite on a host where clock_gettime (and probably time and gettimeofday) succeed, but set errno to ENOSYS. This behavior is unusual, but permitted by POSIX: successful function calls can overwrite errno, as long as they don't set it to 0. The relevant log excerpt looks like this: make[3]: Entering directory '/builddir/build/BUILD/dovecot-2.3.14/src/master' for bin in test-auth-client test-auth-master test-master-login-auth; do \ if ! ./$bin; then exit 1; fi; \ done test-common.c:200: Assert failed: suppress == TRUE connection refused: run (ret == -1) .................................. : ok: Connection failed CLIENT: Error: auth-client: conn unix:./auth-client-test: connect(./auth-client-test) failed: Function not implemented connection refused ................................................... : FAILED connection timed out: run (ret == -1) ................................ : ok: Connection failed connection timed out: timeout ........................................ : ok connection timed out ................................................. : ok bad version: run (ret == -1) ......................................... : ok: Connection failed bad version .......................................................... : ok disconnect version: run (ret == -1) .................................. : ok: Internal failure disconnect version ................................................... : ok auth PLAIN disconnect: run (ret < 0) ................................. : ok auth PLAIN disconnect ................................................ : ok auth PLAIN reconnect: run (ret < 0) .................................. : ok auth PLAIN reconnect ................................................. : ok auth PLAIN failure: run (ret < 0) .................................... : ok auth PLAIN failure ................................................... : ok auth PLAIN success: run (ret == 0) ................................... : ok auth PLAIN success ................................................... : ok auth LOGIN failure 1: run (ret < 0) .................................. : ok auth LOGIN failure 1 ................................................. : ok auth LOGIN failure 2: run (ret < 0) .................................. : ok auth LOGIN failure 2 ................................................. : ok auth LOGIN success: run (ret == 0) ................................... : ok auth LOGIN success ................................................... : ok auth PLAIN parallel failure: run (ret < 0) ........................... : ok auth PLAIN parallel failure .......................................... : ok auth PLAIN parallel success: run (ret == 0) .......................... : ok auth PLAIN parallel success .......................................... : ok auth LOGIN parallel failure 1: run (ret < 0) ......................... : ok auth LOGIN parallel failure 1 ........................................ : ok auth LOGIN parallel failure 2: run (ret < 0) ......................... : ok auth LOGIN parallel failure 2 ........................................ : ok auth LOGIN parallel success: run (ret == 0) .......................... : ok auth LOGIN parallel success .......................................... : ok 1 / 49 tests failed make[3]: Leaving directory '/builddir/build/BUILD/dovecot-2.3.14/src/master' “Function not implemented” suggests that dovecot somehow used the clock_gettime (or gettimeofday) ENOSYS error instead of the expected ECONNREFUSED error code. Unfortunately, I have not figured out where this exactly happens. I don't expect that the problematic glibc build escapes to the wild It was a glibc 2.34 development snapshot, and this particular source of ENOSYS errors is gone again. So fixing this is not urgent. Thanks, Florian

1 0

move mails between mailboxes
by Tom Doenen 13 Jul '21

13 Jul '21

Hello, i am using dovecot 2.3.4.1 I am tyring to make a script using the doveadm move command to move old emails into a subfolder of the users INBOX ; say all mails from 2016 into INBOX/2016. Selecting and moving is not the issue; everything works just i am amazed that the (test) mail client Thunderbird downloads all mails in INBOX/2016 after the move. When i make an IMAP move of all 2016-mails in Thunderbird; mails are moved between the mailboxes without any mails being (re-)downloaded. So what am i missing here? Thank for the tip :) Kind regards, Tom the doveadm move debug output is : Debug: Loading modules from directory: /usr/lib/dovecot/modules Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib20_listescape_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/lib20_zlib_plugin.so Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_sieve_plugin.so Debug: Skipping module doveadm_fts_lucene_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_lucene_plugin.so: undefined symbol: lucene_index_iter_deinit (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_user_get_language_list (this is usually intentional, so just ignore this message) Debug: Skipping module doveadm_mail_crypt_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/libdoveadm_mail_crypt_plugin.so: undefined symbol: mail_crypt_box_get_pvt_digests (this is usually intentional, so just ignore this message) doveadm(tom(a)somedomain.org)<17541><>: Debug: auth USER input: tom(a)somedomain.org uid=5000 gid=5000 home=/mailstore/somedomain.org/to/tom/ doveadm(tom(a)somedomain.org): Debug: Effective uid=5000, gid=5000, home=/mailstore/somedomain.org/to/tom/ doveadm(tom(a)somedomain.org): Debug: Quota root: name=User quota backend=maildir args= doveadm(tom(a)somedomain.org): Debug: Quota rule: root=User quota mailbox=* bytes=8589934592 messages=0 doveadm(tom(a)somedomain.org): Debug: Quota rule: root=User quota mailbox=Trash bytes=+104857600 messages=0 doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8589934592 (100%) messages=0 reverse=no command=quota-warning 100 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8504035246 (99%) messages=0 reverse=no command=quota-warning 99 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8418135900 (98%) messages=0 reverse=no command=quota-warning 98 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8246337208 (96%) messages=0 reverse=no command=quota-warning 96 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8074538516 (94%) messages=0 reverse=no command=quota-warning 94 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=7902739824 (92%) messages=0 reverse=no command=quota-warning 92 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=7730941132 (90%) messages=0 reverse=no command=quota-warning 90 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=7301444403 (85%) messages=0 reverse=no command=quota-warning 85 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=6871947673 (80%) messages=0 reverse=no command=quota-warning 80 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=6012954214 (70%) messages=0 reverse=no command=quota-warning 70 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota warning: bytes=8589934592 (100%) messages=0 reverse=yes command=quota-warning 0 tom(a)somedomain.org doveadm(tom(a)somedomain.org): Debug: Quota grace: root=User quota bytes=47185920 doveadm(tom(a)somedomain.org): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/mailstore/somedomain.org/to/tom:INDEX=/indexes/somedomain… doveadm(tom(a)somedomain.org): Debug: maildir++: root=/mailstore/somedomain.org/to/tom, index=/indexes/somedomain.org/to/tom, indexpvt=, control=, inbox=/mailstore/somedomain.org/to/tom/.INBOX, alt= doveadm(tom(a)somedomain.org): Debug: quota: quota_over_flag check: quota_over_script unset - skipping doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: Mailbox opened because: move doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: Mailbox opened because: move doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52642: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52643: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52644: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52645: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52646: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52963: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52964: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52965: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52967: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52968: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52969: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52970: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX/2016: saving UID 0: Opened mail because: mail stream doveadm(tom(a)somedomain.org): Debug: Mailbox INBOX: UID 52972: Opened mail because: mail stream etc etc... obscured config : # 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 () # OS: Linux 4.19.194-rt81 x86_64 Debian 10.0 ext4 # Hostname: hardy.somedomain.org auth_cache_negative_ttl = 7 mins auth_cache_size = 20 M auth_cache_ttl = 12 mins auth_cache_verify_password_with_worker = yes auth_failure_delay = 9 secs auth_mechanisms = plain login auth_username_chars = auth_worker_max_count = 90 default_client_limit = 2500 default_process_limit = 500 default_vsz_limit = 4 G hostname = post.somedomain.org imap_capability = +SPECIAL_USE imap_fetch_failure = no-after imap_hibernate_timeout = 15 secs imap_idle_notify_interval = 4 mins imap_max_line_length = 512 k lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lda_original_recipient_header = X-Original-To listen = * lmtp_rcpt_check_quota = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_cache_min_mail_count = 15 mail_fsync = never mail_location = maildir:/mailstore/%d/%2n/%n:INDEX=/indexes/%d/%2n/%n:INBOX=/mailstore/%d/%2n/%n/.INBOX:VOLATILEDIR=/tmp/dovecot:NO-NOSELECT:UTF-8 mail_max_keyword_length = 100 mail_plugins = quota zlib listescape mail_prefetch_count = 20 mail_privileged_group = mail mail_temp_scan_interval = 0 mailbox_idle_check_interval = 55 secs mailbox_list_index_include_inbox = yes mailbox_list_index_very_dirty_syncs = yes maildir_broken_filename_sizes = yes maildir_very_dirty_syncs = yes namespace inbox { inbox = yes location = mailbox Concepts { auto = no special_use = \Drafts } mailbox "Deleted Messages" { auto = no special_use = \Trash } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = no special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /etc/dovecot/passwd--%d driver = passwd-file } plugin { listescape_char = } quota = maildir:User quota quota_grace = 45M quota_rule = *:storage=8G quota_rule2 = Trash:storage=+100M quota_status_overquota = 552 5.2.2 User mailbox is full.. quota_status_succes = DUNNO quota_warning = storage=100%% quota-warning 100 %u quota_warning10 = storage=70%% quota-warning 70 %u quota_warning11 = -storage=100%% quota-warning 0 %u quota_warning2 = storage=99%% quota-warning 99 %u quota_warning3 = storage=98%% quota-warning 98 %u quota_warning4 = storage=96%% quota-warning 96 %u quota_warning5 = storage=94%% quota-warning 94 %u quota_warning6 = storage=92%% quota-warning 92 %u quota_warning7 = storage=90%% quota-warning 90 %u quota_warning8 = storage=85%% quota-warning 85 %u quota_warning9 = storage=80%% quota-warning 80 %u sieve = ~/dovecot.sieve sieve_extensions = +notify +imapflags +envelope +vacation +fileinto +date +relational +vacation-seconds sieve_user_log = /dev/null sieve_vacation_min_period = 1h sieve_vacation_send_from_recipient = yes virtual_overquota_bounce = yes zlib_save = gz zlib_save_level = 3 } pop3_fast_size_lookups = yes protocols = imap lmtp pop3 service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-hibernate { unix_listener imap-hibernate { group = $default_internal_group mode = 0660 } } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = 100.100.100.104 port = 993 ssl = yes } process_min_avail = 20 service_count = 0 } service imap { extra_groups = $default_internal_group process_limit = 5000 unix_listener imap-master { user = $default_internal_user } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = 100.100.100.99 port = 995 ssl = yes } process_min_avail = 10 service_count = 0 } service pop3 { process_limit = 1000 } service quota-warning { executable = script /etc/dovecot/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } service submission-login { inet_listener submission { address = 127.0.0.1 port = 587 ssl = yes } process_min_avail = 5 service_count = 1 } service submission { process_limit = 150 } ssl = required ssl_cert = </etc/ssl/private/somedomain.org.crta ssl_cipher_list = ALL:!SSLv2:!SSLv3:!DH:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW@STRENGTH:!EXP:!SEED:!IDEA:!RSA:!CAMELLIA:!SHA1:!SHA256:!SHA384 ssl_client_ca_dir = /etc/ssl/certs ssl_dh = # hidden, use -P to show it ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 ssl_prefer_server_ciphers = yes submission_host = 127.0.0.1 syslog_facility = local2 userdb { args = /etc/dovecot/passwd--%d driver = passwd-file result_failure = return-fail result_internalfail = return-fail } valid_chroot_dirs = /var/spool/vmail verbose_proctitle = yes protocol lmtp { mail_fsync = optimized mail_plugins = quota zlib listescape quota sieve zlib postmaster_address = postmaster(a)somedomain.org } protocol lda { mail_fsync = optimized } protocol imap { mail_max_userip_connections = 25 mail_plugins = quota zlib listescape imap_quota zlib } protocol pop3 { mail_max_userip_connections = 6 }

2 1

doveadm backup Error: Mailbox INBOX sync
by Pierre Sablé 13 Jul '21

13 Jul '21

Hi, the command "doveadm backup -u {user@mail} maildir:/home/backup/{user@mail}/mails/" returns the following error : dsync(user@mail): Error: Mailbox INBOX sync: mailbox_delete failed: INBOX can't be deleted. ...and nothing in dovecot logs dovecot actual version 2.3.15 I did not have this pb in dovecot 2.3.2 /Should this be considered a bug report?/ -- Pierre Sablé Formateur & Administrateur Systèmes Linux - DevOps Tel : 07.63.88.76.21 psable(a)dawan.fr www.dawan.fr

1 0

[ENHANCEMENT] Doveadm HTTP API and the mail-crypt plugin
by Kevin N. 13 Jul '21

13 Jul '21

Hello everybody, I was wondering, are there any plans for the near future to include the mail-crypt plugin related functions, like changing the user key password, into the doveadm http api? It would probably be possible to implement it in a more secure way than any other external ad-hoc solution. Wouldn't it? Cheers, K.

2 2

getting rid of the passwd file unknown user messages
by Marc 12 Jul '21

12 Jul '21

I have configured a userdb file, so I can test with some accounts and override settings. But it is a bit annoying getting unkown user messages for the majority of accounts not in this userdb. Is there a way to skip this reporting? dovecot: auth: passwd-file(aaaaaaaaaaaa,X.X.X.X,<lGapvOzGS5tNPz8/>): unknown user

2 3

Mailbox lost
by Stephane Magnier 12 Jul '21

12 Jul '21

Hi, Any idea why * * *list "" * *-> displays all I want to see but *lsub "" ** -> doesn't display anything ? and AFAIK, this is what I need to get in order any Email clients see my folders ? - Correct ? how can I make visible, by "lsub" all my folders ? Thanks and regards,

4 4

doveadm altmove -r still broken in 2.3.15
by María Arrea 12 Jul '21

12 Jul '21

2 1