- dovecot - dovecot.org

doveadm/doveconf as user tries and fails to read host key
by jimc 24 Aug '20

24 Aug '20

Distro: OpenSuSE Tumbleweed for x86_64 Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18 Reverting to previous version works: dovecot23-2.3.10.1-2.3.x86_64 (Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite) How to make it fail: As the user, execute doveadm expunge mailbox Spam37 savedbefore 3day #User's actual cmd doveadm who #The simplest possible command, for testing It says: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 12: ssl_cert: Can't open file /etc/ssl/hostcerts/hostw.cia: Permission denied The actual EPERM occurs trying to traverse a directory in /etc/letsencrypt, but the next configuration item to be read (in the SSL section) is the host's private key, and the user is surely not ever going to get permission to read that. (I did test giving the user permission to the 750 directory and it did attempt to read the private key, failing.) If you run it as root, of course it works because root has read permission. The initial failure was seen running as the user from cron. Behavior seen in strace: doveadm execs doveconf; doveconf reads the configuration and saves it somewhere (shared memory?); doveconf execs the next program which in this case is doveadm with its original command line; and doveadm now knows its configuration. I can re-do and post the strace if needed. I don't know why doveconf is reading the SSL keys in 2.3.11.3 when it didn't in 2.3.10.1, but if the idea is to read the complete configuration in case it might be needed in obscure situations, a possible workaround is to not die on unreadable secrets and to report those either as unset or as a new "error" symbol, letting the consumer (doveadm) deal with the fallout, or in this case ignore it. Attached: sysreport.gz ; doveconf-n.out Dovecot's working files and user mailboxes are on ext4 filesystems; NFS is not involved. The mail reader is Roundcube webmail. -- James F. Carter Email: jimc(a)jfcarter.net Web: http://www.math.ucla.edu/~jimc (q.v. for PGP key)

2 2

2 factor authentication
by The Doctor 24 Aug '20

24 Aug '20

Is 2 factor authentication possible on dovecot? -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca Yahweh, Queen & country!Never Satan President Republic!Beware AntiChrist rising! Look at Psalms 14 and 53 on Atheism https://www.empire.kred/ROOTNK?t=94a1f39b New Brunswick Save The PRovince Vote Liberal 14 Sept!!

3 2

2.3.11.3 on 32bit platforms
by Michael Ströder 22 Aug '20

22 Aug '20

HI! I'm trying to update openSUSE package on OBS [1] which builds for various OS versions and hardware platforms. To me it seems that a test fails on 32bit platforms: Info: invalid token 3: structure length disagrees with data size test rpa ..................................... : ok Info: invalid NTLM response: buffer length out of bounds test ntlm ............................: ok 1 / 86 tests failed [1] https://build.opensuse.org/package/show/home:stroeder:branches:server:mail/… Ciao, Michael.

4 6

Dovecot on Ubuntu 20.04
by spamvoll＠googlemail.com 22 Aug '20

22 Aug '20

Hi, is anyone using the "Bionic (18.04 LTS)" packages on Focal Fossa (20.04 LTS) ? I'm not sure if its working after the upgrade Hans

5 7

RHEL7/CentOS7 RPM of dovecot 2.3.11.3-3 seems to have dropped tcpwrap support
by Thomas Scheunemann 21 Aug '20

21 Aug '20

Using the Repo http://repo.dovecot.org/ce-2.3-latest after upgrading from 2.3.10.1-3 to 2.3.11.3-3 we get numerous error messages like: dovecot: imap-login: Error: connect(tcpwrap) failed: No such file or directory We use tcpwrap support in dovecot, which worked flawlessly in the older version. I can see that the socket /var/run/dovecot/login/tcpwrap is not created anymore. And comparing with RPMs, the new one seems to be missing the file: /usr/libexec/dovecot/tcpwrap which leads me to conclusion that the new version is just not compiled with tcpwrap support. Thomas Scheunemann

5 6

dovecot-SASL for Postfix: EXTERNAL does not work.
by Steffen Nurpmeso 21 Aug '20

21 Aug '20

Hello. I am not subscribed and new here, so first of all i want to thank you for dovecot. I personally do not use it in "production" (yet), but it is my sole point of interaction for testing the little MUA i maintain for quite some years. I also have used its code for affirmation purposes. (Interesting that OAUTHBEARER treats hostname and port as optional. I currently do OAUTHBEARER.) So then i stumbled over GSSAPI not being usable anymore with the latest release, but it seems there is an ML thread with a fix. I have not tried it, i reverted to the last release here, though. When i implemented EXTERNAL authentication last year i could not figure out how to make postfix+dovecot-SASL work with it. First of all i had to switch configs back and forth, but in the meantime i learned a very nice trick: if i use two password databases passdb { driver = passwd-file mechanisms = external args = /etc/dovecot/pass-external.db override_fields = nopassword } passdb { driver = passwd-file args = /etc/dovecot/pass.db } userdb { driver = passwd } which are effectively the same except that one does not have passwords while the other has, i can use EXTERNAL (with and without additional user-via-protocol in combination with auth_ssl_username_from_cert=yes and it just works! Whereas EXTERNAL works just fine for IMAP and POP3 it does not for SMTP. Last year when i did it i saw a postfix ML thread in action, so i have not looked further into that. Looking again with things unchanged in the postfix 3.5 that they mentioned by then i think, i now posted to the postfix list myself yesterday [1], and it turned out that postfix seems incapable to do something about it, because the dovecot auth protocol does not offer the possibility to specify a valid-user-certificate-seen flag as well as pass the username from the certificate. (Or even pass the entire certificate as a base64 string, less postfix CA, .. or whatever.) [1] https://marc.info/?l=postfix-users&m=159785887710910&w=2 What is really terrible with the current situation is that postfix announces the EXTERNAL, with Wietse Venema saying Short summary: Postfix does not implement a single iota of SASL AUTH support. Postfix simply propagates the names of mechanisms that the backend (Cyrus or Dovecot) claims to support, and Postfix proxies requests and responses between the remote SMTP client and the SASL backend. Postfix has no idea what SASL mechanisms are, including EXTERNAL. It just proxies stuff. If Dovecot claims to support SASL EXTERNAL but does not handle it, that that is a bit of a WTF. It would be tremendous to have true EXTERNAL support all through, i personally really like EXTERNAL, i would rather have some password-protected crytographically secured certificates in my local store, and have client certificates in all the IoT devices, than have to mess around with the OAUTH that the major players press forward, for example. Thanks, and Ciao from Germany, --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)

3 9

zlib errors after upgrading from 2.3.10.1 to 2.3.11.3
by Robert Nowotny 21 Aug '20

21 Aug '20

I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 Thunderbird reports some error when try to save/open a bigger attachment. Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870><jZk...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]) Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63871><9A0...>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]) Aug 21 15:30:11 lxc-imap dovecot: imap(cpotzinger)<63889><Ig6...>: Error: Mailbox Sent: UID=29495: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Aug 21 15:30:17 lxc-imap dovecot: imap(cpotzinger)<64169><GXe...>: Error: Mailbox Sent: UID=29495: read(zlib(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703)) failed: read(/home/vmail/virtualmailboxes/cpotzinger/storage/m.4703) failed: Broken pipe (FETCH BODY[]) Aug anything I can tweak or do ? Robert

1 0

Adjusting logging with the "remote" syntax
by Jason Young 21 Aug '20

21 Aug '20

According to the docs, we can use ‘local’ and ‘remote’ blocks to change configuration directives. In my current setup (Mail-in-a-box using Nextcloud, which is configured for IMAP authentication), my mail logs are spammed with local logins. I really don't need these reports, but still want to retain login logs for remote IPs. So I set the following in my configuration: remote 127.0.0.1 { info_log_path = /dev/null } When I run "doveadm -n -f remote=127.0.0.1”, it does seem to understand it: --- # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) ... info_log_path = /dev/null ... remote 127.0.0.1 { info_log_path = /dev/null } --- However, I’m still getting spammed with local login reports: Aug 12 12:17:13 imap-login: Info: Login: user=<user(a)domain.tld>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=29798, TLS, session=<FGVJhbCsstt/AAAB> Aug 12 12:17:13 imap(user(a)domain.tld): Info: Logged out in=305 out=2277 I've also tried logging to a specific file, instead of /dev/null, but no file was created. So there must be an issue with my understanding. How can I prevent logins from localhost from being logged without sacrificing logs for all logins? -Jason Young

1 1

OT: SASL questions
by Richard Hector 21 Aug '20

21 Aug '20

Hi all, Apologies for the somewhat off-topic questions - I'm trying to get my head around SASL, and what it is/does. I can see that a (SMTP, IMAP etc) server can offer various authentication methods, which are pre-defined and which the client can choose from. SASL then seems to define how those work. But dovecot and cyrus-sasl both seem to offer a client-server interface, usable by eg postfix, which I don't see any reference to in SASL summaries online. Is that a standard interface? ie can a client like postfix talk to either dovecot or cyrus without knowing the difference? Are there others? Is there a good reference to this somewhere, short of reading the RFCs? And is there any option (current or proposed) to let dovecot act as a client, rather than a server? Thanks, Richard

2 2

Rootless wiki page is not up to date?
by Marc Roos 20 Aug '20

20 Aug '20

If I run a docker image with the mesos containerizer and altering the dovecot config mentioned here[1] I think the root detection is incorrect because it looks like dovecot is still thinking it is root. I still get errors like: >> log(829825): Fatal: We couldn't drop root group privileges (wanted=10053(dovecot), gid=0(root), egid=0(root)) Why does it want to drop to root, if we are not even running as root? >> Error: service(ipc): chown(/var/dovecot/login/ipc-proxy, 91, 4294967295) failed: Operation not permitted Why does it want to chown, when it is not root? pop3-login: Fatal: setgid(101(dovenull)) failed with euid=10053(dovecot), gid=10053(dovecot), egid=10053(dovecot): Operation not permitted (This binary should probably be called with process group set to 101(dovenull) instead of 10053(dovecot)) [1] https://wiki.dovecot.org/HowTo/Rootless?action=edit&editor=text

2 2