On Fri, 14 Aug 2020 at 13:57:32 +0200, Jonas Smedegaard wrote: > and shouting out to you on irc,
Oh, if that was recently I'm afraid I missed it. > Now it works, after aplying this patch: > > --- /etc/dovecot/conf.d/10-ssl.conf.orig > +++ /etc/dovecot/conf.d/10-ssl.conf > @@ -9,8 +9,8 @@ > # dropping root privileges, so keep the key file unreadable by anyone but > # root. Included doc/mkcert.sh can be used to easily generate self-signed > # certificate, just make sure to update the domains in dovecot-openssl.cnf > -ssl_cert = </etc/dovecot/private/dovecot.pem > -ssl_key = </etc/dovecot/private/dovecot.key > +#ssl_cert = </etc/dovecot/private/dovecot.pem > +#ssl_key = </etc/dovecot/private/dovecot.key > . > # If key file is password protected, give the password here. Alternatively > # give it when starting dovecot with -p parameter. Since this file is often I see, thanks. Seems a regression from Dovecot upstream, which was also reported at https://dovecot.org/pipermail/dovecot/2020-August/119642.html . The test suite didn't catch this since we don't run the IMAPd with the stock configuration (intentionally — don't want to depend too much on a specific server), and instead run `doveadm -c /path/to/dovecot.conf exec imap` as tunnel command. That's also the workflow advertised at /usr/share/doc/interimap/getting-started.md.gz. I'll see if upstream fixes the regression, and add a note to the aforementioned document otherwise. (Explicitly setting ‘ssl=no’ doesn't seem to have an effect anymore, so that document should probably be revisited anyway.) -- Guilhem.
signature.asc
Description: PGP signature