August 2021 - dovecot

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