- dovecot - dovecot.org

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