Replicating to an older version

Hi everyone, I have two servers running dovecot, both at version 2.2.33.2. One is a an mx-backup and they replicate to each other. I am moving the main server to a new VPS instance, and I'm planning the move carefully, including running dovecot on a container (Docker). I am basing my

Re: Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK

On Thu, 30 Apr 2020, hanas...@gmail.com wrote: Apr 8 18:10:18 hh dovecot: imap-login: Debug: SSL error: SSL_accept() failed: error:14094412:SSL routines:ssl3_read_bytes:sslv3 alert bad certificate: SSL alert number 42 According to this

Replicating to an older version

Hi everyone, I have two servers running dovecot, both at version 2.2.33.2. One is a an mx-backup and they replicate to each other. I am moving the main server to a new VPS instance, and I'm planning the move carefully, including running dovecot on a container (Docker). I am basing my

Re: Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK

I would expect the public cert to be imported as a "server" not an "auth" The attached image shows that TBird wants an httpS url for a webserver, for the source. Ages ago, I think it prompted for "do you want to trust this new cert" and YES added it (assuming that is the public key) to the

Re: Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK

For internal use I've installed the private CA cert on whatever clients I'm using (Thunderbird, browsers). That way you don't need to make exceptions every time a certificate changes. Good luck, Reio On 30.04.2020 21:36, hanas...@gmail.com wrote: Hello, This is a selfsigned cert.  Both of

Re: Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK

I see. You need to import the cert into thundebird's trusted ca certs.AkiOn 30/04/2020 21:36 hanas...@gmail.com wrote:Hello,This is a selfsigned cert. Both of the below methods were used.May I ask for 1. pointer to info setting up "intermediate certs" andwhere the certfile

Re: Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK

Hello, This is a selfsigned cert. Both of the below methods were used. May I ask for 1. pointer to info setting up "intermediate certs" and where the certfile goes? The objective is to generate a self-signed cert and use it for just internal use with IMAPS dovecot. Separately, what are

sender rewriting scheme

Hello, I would like to know if dovecot/pigeonhole provide a way to do sieve redirection with sender rewriting scheme (srs)? I apologize in advance if that e-mail address isn't meant for assistance, but I've asked on the official irc channel on freenode and was told to direct my query to

Re: Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK

On 30/04/2020 14:49 hanas...@gmail.com wrote:Recently thunderbird and Dovecot IMAPS cannot agree on SSL howeverEvolution, on the exact same system, is working fine with the sameaccounts. Tried recreating the Dovecot cert and also the thunderbirdaccounts from scratch. The

Dovecot IMAPS : Thunderbird SSL cert issue / Evolution OK

Recently thunderbird and Dovecot IMAPS cannot agree on SSL however Evolution, on the exact same system, is working fine with the same accounts. Tried recreating the Dovecot cert and also the thunderbird accounts from scratch. The OpenSSL raw client works fine as well. Would someone also