- dovecot - dovecot.org

submission_add_received_header option?
by Ellie McNeill 05 Feb '24

05 Feb '24

Hi, I've recently upgraded my mail server from Debian 11 to Debian 12. It now runs dovecot 2.3.19.1 (verified with dovecot --version). According to the "Dovecot Core Settings" page, a new setting 'submission_add_received_header' was added in dovecot 2.3.19 to give admins the option of hiding the IP of the sending client when using dovecot's submissiond: https://doc.dovecot.org/3.0/settings/core/ However, when I place this option in my config, dovecot refuses to start and says that the option is not recognised: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/20-submission.conf line 92: Unknown setting: submission_add_received_header Can anyone help me with this? Ellie

5 5

Recommended changes for delivery from Exim
by jgh＠exim.org 05 Feb '24

05 Feb '24

Hi, Security changes to Exim have invalidated certain suggested configurations in the Dovecot wiki. As I do not have a Dovecot installation to test, I am not going to write any updates there. It would be good if someone would test these suggestions and then make updates as needed. 1) The use of $local_part and $domain in commands run by the "pipe" transport will be disallowed in the upcoming Exim release. These are currently noted as optional, with the "-m" flag to dovecot-lda. They should be replaced with validated (untainted) versions, commonly $local_part_data and $domain_data, developed via one of the several de-taint methods documented for Exim. The same applies to $original_local_part and $original_domain. 2) The use of $sender_address will likewise be disallowed. This and the "-f" flag can be dropped from the dovecot-lda command line, and the specification of a null "message_prefix" option removed. The defaults for a pipe transport will then prefix the message with a suitable Mbox "From " header line, which dovecot-lda is documented to extract the sender from. Both of these suggestions are back-compatible to the current 4.95 release of Exim, and will be required with the 4.96 release. -- Cheers, Jeremy Refs: - https://wiki.dovecot.org/LDA/Exim - https://doc.dovecot.org/configuration_manual/protocols/lda/

3 3

Problem with share mailbox
by Frédéric FONDRIEST 05 Feb '24

05 Feb '24

Hi all, we get some problems with sharing mailbox between users. when we share something the dovecot-acl file is updated, but the shared-mailboxes.db file is not created nor updated. Even if we create the file and set permission to 777... strangely the debug log gives : 2024-02-05 09:29:04 imap(xxxxxx)<13741><SA8qQZ4QBIsKDMcL>: Debug: dict(file): dict created (uri=file:/tmp/shared-mailboxes.db, base_dir=/var/run/dovecot) 2024-02-05 09:29:04 imap(xxxxxx)<13741><SA8qQZ4QBIsKDMcL>: Debug: open(/proc/self/io) failed: Permission denied we don't understand why we get this kind of message. we search on this mailing list without any clean explaination. we expect a bug somewhere.. any ideas ? system is : debian 12 dovecot 2.3.19.1 (9b53102964) # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-17-amd64 x86_64 Debian 12.4 auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = %n base_dir = /var/run/dovecot log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_gid = 5000 mail_home = /home/vmail/%u mail_location = /home/vmail/%u/Maildir mail_plugins = acl mail_log acl mail_log mail_privileged_group = mail mail_uid = 5000 namespace { 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 = / type = private } namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf driver = ldap name = ldap } plugin { acl = vfile acl_shared_dict = file:/tmp/shared-mailboxes.db acl_user = %u master_user = %u } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { inet_listener lmtp { address = * port = 24 } user = vmail } ssl_cert = </etc/ssl/mail.crt ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap name = ldap } protocol imap { imap_client_workarounds = delay-newmail imap_max_line_length = 64 k mail_max_userip_connections = 20 mail_plugins = acl imap_acl } protocol lda { info_log_path = log_path = mail_plugins = mail_log postmaster_address = postmaster@xxx quota_full_tempfail = yes syslog_facility = mail } protocol lmtp { info_log_path = log_path = mail_plugins = mail_log postmaster_address = postmaster@xxx quota_full_tempfail = yes } Hi all, we get some problems with sharing mailbox between users. when we share something the dovecot-acl file is updated, but the shared- mailboxes.db file is not created nor updated. Even if we create the file and set permission to 777... strangely the debug log gives : 2024-02-05 09:29:04 imap(xxxxxx)<13741><SA8qQZ4QBIsKDMcL>: Debug: dict(file): dict created (uri=file:/tmp/shared-mailboxes.db, base_dir=/var/run/dovecot) 2024-02-05 09:29:04 imap(xxxxxx)<13741><SA8qQZ4QBIsKDMcL>: Debug: open(/proc/ self/io) failed: Permission denied we don't understand why we get this kind of message. we search on this mailing list without any clean explaination. we expect a bug somewhere.. any ideas ? system is : debian 12 dovecot 2.3.19.1 (9b53102964) # 2.3.19.1 (9b53102964): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.19 (4eae2f79) # OS: Linux 6.1.0-17-amd64 x86_64 Debian 12.4 auth_master_user_separator = * auth_mechanisms = plain login auth_username_format = %n base_dir = /var/run/dovecot log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_gid = 5000 mail_home = /home/vmail/%u mail_location = /home/vmail/%u/Maildir mail_plugins = acl mail_log acl mail_log mail_privileged_group = mail mail_uid = 5000 namespace { 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 = / type = private } namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u:INDEXPVT=~/Maildir/ shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap-passdb.conf driver = ldap name = ldap } plugin { acl = vfile acl_shared_dict = file:/tmp/shared-mailboxes.db acl_user = %u master_user = %u } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { inet_listener lmtp { address = * port = 24 } user = vmail } ssl_cert = </etc/ssl/mail.crt ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf driver = ldap name = ldap } protocol imap { imap_client_workarounds = delay-newmail imap_max_line_length = 64 k mail_max_userip_connections = 20 mail_plugins = acl imap_acl } protocol lda { info_log_path = log_path = mail_plugins = mail_log postmaster_address = postmaster@xxx quota_full_tempfail = yes syslog_facility = mail } protocol lmtp { info_log_path = log_path = mail_plugins = mail_log postmaster_address = postmaster@xxx quota_full_tempfail = yes }

4 7

Splitting up packages
by Larry Rosenman 01 Feb '24

01 Feb '24

I'm the maintainer of the dovecot and pigeonhole ports on FreeBSD and am looking to make separate installable packages like the project does for Linux. Can you help me know what needs to go where and what options (if any) change the base? Thanks for any help here. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 I'm the maintainer of the dovecot and pigeonhole ports on FreeBSD and am looking to make separate installable packages like the project does for Linux. Can you help me know what needs to go where and what options (if any) change the base? Thanks for any help here. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106

3 2

We couldn't drop root group privileges
by forumforeign 01 Feb '24

01 Feb '24

Hello. I have - dovecot 2.3.21 (also tried 2.3.5) - postfix 3.8.5 (also tried 3.8.4) It's a new setup where I use postfix + dovecot-delivery for delivery to local mailbox. At logs I have an error and mail deffers in queue: dovecot: [ID 702911 mail.crit] lda(poli(a)domain.com)<7808>: Fatal: We couldn't drop root group privileges (wanted=6(mail), gid=0(root), egid=0(root)) Postfix and dovecot start from root UID, but user dovecot/postfix has corresponding groups to run as specific group: root@solaris:# id -a dovecot uid=110(dovecot) gid=110(dovecot) groups=110(dovecot),6(mail) root@solaris:# id -a postfix uid=26(postfix) gid=26(postfix) groups=26(postfix),6(mail) root@solaris:# id -a root uid=0(root) gid=0(root) groups=0(root),1(other),2(bin),3(sys),4(adm),6(mail),7(tty),8(lp),12(daemon) Also, when I run a dtrace (a system call trace mechanism) I see, that dovecot-lda runs as group "mail" (gid=6), so, there isn't any problem, but dovecot thinks another: UID GID PID PPID ARGS 0 26 7719 7638 pipe -n dovecot -t unix flags=DRhu user=nobody:mail argv=/usr/libexec/dovecot/d 60001 6 7720 7718 /usr/libexec/dovecot/dovecot-lda -f mega(a)domain.com -d poli(a)domain.com 60001 6 7720 7718 /usr/bin/amd64/doveconf -f service=lda -c /etc/dovecot/dovecot.conf -m lda -e / 60001 6 7720 7718 /usr/libexec/dovecot/dovecot-lda -f mega(a)domain.com -d poli(a)domain.com What exactly dovecot wants and how to solve this error? Here is part of "dovecot -n" output which is corresponding to user/group/lda: # 2.3.5.1 (7ec6d0ade): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.6 (92dc263a) # OS: SunOS 5.11 i86pc # Hostname: solaris auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_process_limit = 99 disable_plaintext_auth = no first_valid_gid = 6 first_valid_uid = 60001 last_valid_gid = 6 last_valid_uid = 60001 mail_access_groups = mail mail_debug = yes mail_gid = 6 mail_location = /var/mail/vmail/%u@%d mail_max_userip_connections = 99 mail_privileged_group = mail mail_uid = 60001 maildir_very_dirty_syncs = yes ... service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ... protocol lda { mail_plugins = " sieve" postmaster_address = postmaster } PS. Also, I have aother box with very old setup (dovecot 2.2.27) and it works with the same configuration without any errors. I thought that this is OS specific problem and tried on the same version OS run a dovecot 2.3.21, but still had an errors.

1 1

Emails automatically thread by subject, no matter how old or unrelated
by wakod67943＠flexvio.com 01 Feb '24

01 Feb '24

To preface, I’m using the Crossbox mail client hosted by MXroute. I was directed to Dovecot support when I made my inquiry to the former’s developers. Apparently, when you write an email subject that is verbatim to another, previously sent email, the two become linked in a conversation thread. I could have an email from 1996 titled “Groceries” and if I make one today titled “Groceries” my inbox would have them connected as one long thread. I’m getting email threads in the 100s because of this. Crossbox people have told me it’s not something they have control over. They mentioned it being a Dovecot problem. Has anyone encountered this? It would be tremendously inconvenient to ensure that every email I ever send from now on has a unique subject so to as not have them threaded together. Let me be clear, email threading and conversation views are extremely useful. I just want them to be…relevant to the chain of emails that are being looked at. Is there a way to group threads by unique header information? It is becoming borderline unusable to sift through invoices.

3 2

JMAP support?
by Mark Constable 31 Jan '24

31 Jan '24

On Fri Jan 25 2019 Aki wrote: > There is no JMAP support in any dovecot version yet. Two years on so what is the status of JMAP support in Dovecot now?

7 10

doveadm sync failed after adding "mechanisms = plain login" to passdb
by James 31 Jan '24

31 Jan '24

Hello, After adding `mechanisms = plain login` to passdb (passwd-file), `doveadm -D sync -u e(a)example.com -d -N -l 30 -U` failed with ``` Jan 26 06:49:22 doveadm(e(a)example.com): Error: remote(server2.example.com:61526): doveadm(1.1.1.1,e(a)example.com): auth-master: passdb lookup(e(a)example.com): Auth PASS lookup failed Jan 26 06:49:22 doveadm(e(a)example.com): Error: remote(server2.example.com:61526): doveadm(1.1.1.1,e(a)example.com): /run/dovecot/auth-userdb: passdb lookup failed (to see if user is proxied, because doveadm_port is set) ``` With `auth_debug=yes`, I found these lines. ``` Jan 26 04:55:37 server2 dovecot: auth: Debug: skipping passdb: mechanism filtered Jan 26 04:55:37 server2 dovecot: auth: Error: All password databases were skipped ``` What should I do to fix it without deleting `mechanisms = plain login`? More information could be found on [this link](https://github.com/orgs/docker-mailserver/discussions/3836#discussion…. Thanks

1 0

Re: JMAP support?
by Marcel Schmidt 30 Jan '24

30 Jan '24

Hi, is there any progress on this? Since the IETF draft is long completed, will you integrate JMAP in a coming dovecot version or is this topic completely abandoned? Marcel Hi, is there any progress on this? Since the IETF draft is long completed, will you integrate JMAP in a coming dovecot version or is this topic completely abandoned? Marcel

1 0

One Way sync is deleting emails
by Steve Moser 30 Jan '24

30 Jan '24

Hello, I am hoping that you can help me. I am running this command on my main email server, one way backup/sync to the backup server. sudo doveadm sync -1 -A remote:root@x.x.x.x x.x.x.x is my remote server. I will add a new email on the main, run the command and it shows up on the backup. - Great! Now I delete that email from the main, run the command and the email is removed from the backup. That should not delete anything from the backup, correct? I prefer Not to delete anything, only update/add. Do you see what I am doing wrong? Thank You!!!! Here my installed versions dovecot-core 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-imapd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-lmtpd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-mysql 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-pop3d 1:2.3.16+dfsg1-3ubuntu2.2 postfix 3.6.4-1ubuntu1.2 amd64 High-performance mail transport agentpostfix-mysql 3.6.4-1ubuntu1.2 amd64 MySQL map support for Postfixpostfix-policyd-spf-python 2.9.3-1 all Postfix policy server for SPF checking Hello, I am hoping that you can help me. I am running this command on my main email server, one way backup/sync to the backup server. sudo doveadm sync -1 -A remote:root@x.x.x.x x.x.x.x is my remote server. I will add a new email on the main, run the command and it shows up on the backup. - Great! Now I delete that email from the main, run the command and the email is removed from the backup. That should not delete anything from the backup, correct? I prefer Not to delete anything, only update/add. Do you see what I am doing wrong? Thank You!!!! Here my installed versions dovecot-core 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-imapd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-lmtpd 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-mysql 1:2.3.16+dfsg1-3ubuntu2.2 dovecot-pop3d 1:2.3.16+dfsg1-3ubuntu2.2 postfix 3.6.4-1ubuntu1.2 amd64 High-performance mail transport agent postfix-mysql 3.6.4-1ubuntu1.2 amd64 MySQL map support for Postfix postfix-policyd-spf-python 2.9.3-1 all Postfix policy server for SPF checking

2 1