Author Topic: dovecot SNI  (Read 3218 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
dovecot SNI
« on: August 11, 2021, 04:41:29 PM »
If you want to add SNI to your dovecot configuration:
(this was made on a proxmox lxc container with centos 8 )

my dovecot configuration didn't include the files in /etc/dovecot/conf.d but there are about 30 files which I didn't want to include to avoid breaking other things. so I created a new directory:
mkdir /etc/dovecot/myconf.d
then added a line to the end of  /etc/dovecot/dovecot.conf:
!include myconf.d/*.conf

in /etc/dovecot/myconf.d you create a file which will reference the certs for one of your domains:
I did:
cd /etc/dovecot/myconf.d
vi 14-domain2.conf

and the file looks like this:
local_name domain2.eu {
  ssl_cert = </etc/pki/tls/certs/domain2.eu.pem
  ssl_key = </etc/pki/tls/certs/domain2.eu.pem
}


the file /etc/pki/tls/certs/domain2.eu.pem doesnt exist yet, you can create it like this:
cat /etc/pki/tls/private/domain2.eu.key /etc/pki/tls/certs/domain2.eu.cert /etc/pki/tls/certs/domain2.eu.bundle > /etc/pki/tls/certs/domain2.eu.pem

thats probably not the most elegant way, but it works ;)
also when the lets encrypt certs are renewed, you have to renew the *.pem files manually
will check if there is a more automatic way...
any suggestions welcome.

Offline
*
Re: dovecot SNI
« Reply #1 on: August 23, 2021, 02:54:02 PM »