Re: Problems connecting to imap after upgrade of openssl to v3

Sam Varshavchik <[email protected]>
Newsgroups gmane.mail.imap.courier.general
Message-ID <CAMO9iftWJMoJUctEt18R19MNKN8af7VHnz=WU3St3GSETxBzew@mail.gmail.com>
On Wed, Oct 18, 2023 at 5:21 PM Kristian Duus Østergaard <
[email protected]> wrote:

> 1) pop3 have always been disabled. TLS_PROTOCOL, TLS_CIPHER_LIST, and
> TLS_STARTTLS are default for imapd-ssl. For esmtpd I reduced the
> TLS_CIPHER_LIST years ago to make it more secure. And for esmtpd-ssl the
> TLS_PROTOCOL="TLSv1".
>

It's a near certainty that this TLS_PROTOCOL setting will be problematic,
these days TLS 1.3 is the expected minimum, but your issue is with imap.


> 2) True - but I was hoping some of the bright minds in here had an I
> idea :-) . The only thing I can come up with is that openssl have changed
> something in the way that it parses ipv6 adressses.
>

I  can't think of a reason why openssl needs to do that. It has a socket.
That's enough to do its job. I don't recall reading about any certificate
properties that bind certificates to specific IP addresses.

Without anything else to go on, the only possible course of action is to
start with a clean slate, instead of some existing complicated
configuration. Set Courier up with a single certificate, and all default
settings. Once that's working, and only then, start working on converting
the existing, complicated setup.

_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.