Re: Dovecot and SNI

2024-03-13 Thread Peter
On 13/03/24 22:30, Stuart Henderson wrote: I test with this: openssl s_client -connect mail.domain.com:993 -crlf -quie= t That's not a valid test. openssl >=1.1.1 s_client uses SNI by default, with libressl or older openssl you need to use -servername. Indeed, you want: openssl s_client

Re: Dovecot and SNI

2024-03-13 Thread Stuart Henderson
On 2024-03-12, steffan--- via dovecot wrote: > I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips= > that=92s been fine for quite some time. Recently I started getting complai= > nts related to SNI. > > I test with this: openssl s_client -connect mail.domain.com:993

Re: Dovecot and SNI

2024-03-13 Thread Aki Tuomi via dovecot
> On 12/03/2024 22:54 EET steffan--- via dovecot wrote: > > > I have an old CentOS 7 server using dovecot 2.2.36 and OpenSSL 1.0.2k-fips > that’s been fine for quite some time. Recently I started getting complaints > related to SNI. > > I test with this: openssl s_client -connect

Dovecot and SNI

2024-03-12 Thread steffan--- via dovecot
I have an old CentOS 7 server using dovecot 2.2.36  and OpenSSL 1.0.2k-fips that’s been fine for quite some time. Recently I started getting complaints related to SNI.   I test with this: openssl s_client -connect mail.domain.com:993 -crlf -quiet   On macOS using OpenSSL LibreSSL 3.3.6 I test and

Re: local_name in dovecot for SNI and wildcard

2021-10-20 Thread Aki Tuomi
Wildcard and multiple name support was added in 2.2.27. Aki On 20 October 2021 8.40.49 UTC, Alessio Cecchi wrote: >Hi, > >in dovecot configuration the options "local_name" can support wildcard >domain name (es. *.mailserver.com)? > >This because we have a wildcard SSL certificate and I prefer

local_name in dovecot for SNI and wildcard

2021-10-20 Thread Alessio Cecchi
Hi, in dovecot configuration the options "local_name" can support wildcard domain name (es. *.mailserver.com)? This because we have a wildcard SSL certificate and I prefer to specifica a wildcard name instead of single. Is fine this? local_name *.mailserver.com {  ssl_cert =

[Dovecot] TLS SNI with Dovecot

2013-12-22 Thread Michael Neurohr
Hi! I've been using Dovecot for one single Domain with SSL certificates. Now I would like to use Dovecot with several Domains and proper SSL certificates. I tried to setup TLS SNI but it does not work. What I basically did was just adding local_name imap.samsoft.at { ssl_cert =

Re: [Dovecot] TLS SNI with Dovecot

2013-12-22 Thread Reindl Harald
Am 22.12.2013 22:07, schrieb Michael Neurohr: I've been using Dovecot for one single Domain with SSL certificates. Now I would like to use Dovecot with several Domains and proper SSL certificates. I tried to setup TLS SNI but it does not work. What I basically did was just adding forget it -

Re: [Dovecot] TLS SNI with Dovecot

2013-12-22 Thread Gedalya
On 12/22/2013 04:26 PM, Reindl Harald wrote: forget it - SNI is relevant for webservers because different vhosts with different contents, typically not for mailservers why do you start the burden of different certs instead mail.your-company.tld and give that hostname to any user? While it's

Re: [Dovecot] TLS SNI with Dovecot

2013-12-22 Thread Reindl Harald
Am 22.12.2013 23:09, schrieb Gedalya: On 12/22/2013 04:26 PM, Reindl Harald wrote: forget it - SNI is relevant for webservers because different vhosts with different contents, typically not for mailservers why do you start the burden of different certs instead mail.your-company.tld and