2016-04-07 12:20:51 +00:00
|
|
|
##
|
|
|
|
## SSL settings
|
|
|
|
##
|
|
|
|
|
|
|
|
# SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt>
|
|
|
|
#ssl = yes
|
|
|
|
|
|
|
|
# PEM encoded X.509 SSL/TLS certificate and private key. They're opened before
|
|
|
|
# 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
|
2018-02-04 20:27:47 +00:00
|
|
|
ssl_cert = </etc/dovecot/ssl/dovecot.pem
|
|
|
|
ssl_key = </etc/dovecot/ssl/dovecot.key
|
2016-04-07 12:20:51 +00:00
|
|
|
|
|
|
|
# If key file is password protected, give the password here. Alternatively
|
|
|
|
# give it when starting dovecot with -p parameter. Since this file is often
|
|
|
|
# world-readable, you may want to place this setting instead to a different
|
|
|
|
# root owned 0600 file by using ssl_key_password = <path.
|
|
|
|
#ssl_key_password =
|
|
|
|
|
|
|
|
# PEM encoded trusted certificate authority. Set this only if you intend to use
|
|
|
|
# ssl_verify_client_cert=yes. The file should contain the CA certificate(s)
|
|
|
|
# followed by the matching CRL(s). (e.g. ssl_ca = </etc/ssl/certs/ca.pem)
|
2017-01-25 13:10:40 +00:00
|
|
|
#ssl_ca =
|
2016-04-07 12:20:51 +00:00
|
|
|
|
|
|
|
# Require that CRL check succeeds for client certificates.
|
|
|
|
#ssl_require_crl = yes
|
|
|
|
|
|
|
|
# Directory and/or file for trusted SSL CA certificates. These are used only
|
|
|
|
# when Dovecot needs to act as an SSL client (e.g. imapc backend). The
|
|
|
|
# directory is usually /etc/ssl/certs in Debian-based systems and the file is
|
|
|
|
# /etc/pki/tls/cert.pem in RedHat-based systems.
|
|
|
|
#ssl_client_ca_dir =
|
|
|
|
#ssl_client_ca_file =
|
|
|
|
|
|
|
|
# Request client to send a certificate. If you also want to require it, set
|
|
|
|
# auth_ssl_require_client_cert=yes in auth section.
|
|
|
|
#ssl_verify_client_cert = no
|
|
|
|
|
|
|
|
# Which field from certificate to use for username. commonName and
|
|
|
|
# x500UniqueIdentifier are the usual choices. You'll also need to set
|
|
|
|
# auth_ssl_username_from_cert=yes.
|
|
|
|
#ssl_cert_username_field = commonName
|
|
|
|
|
|
|
|
# DH parameters length to use.
|
2017-01-25 13:10:40 +00:00
|
|
|
ssl_dh_parameters_length = 2048
|
2016-04-07 12:20:51 +00:00
|
|
|
|
|
|
|
# SSL protocols to use
|
2017-12-31 11:33:48 +00:00
|
|
|
ssl_protocols = !SSLv3
|
2016-04-07 12:20:51 +00:00
|
|
|
|
|
|
|
# SSL ciphers to use
|
2017-01-25 13:10:40 +00:00
|
|
|
ssl_cipher_list = ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:!DSS
|
2016-04-07 12:20:51 +00:00
|
|
|
|
|
|
|
# Prefer the server's order of ciphers over client's.
|
2016-12-17 09:59:04 +00:00
|
|
|
ssl_prefer_server_ciphers = yes
|
2016-04-07 12:20:51 +00:00
|
|
|
|
|
|
|
# SSL crypto device to use, for valid values run "openssl engine"
|
|
|
|
#ssl_crypto_device =
|