On 24/08/25, louis.villedieu@yahoo.com (louis.villedieu@yahoo.com) wrote:

I tried yesterday all the options you proposed in terms of configuration.

I don't think the configuration has an issue since the settings are loaded successfully but not kept.

I presume this can be due to an incompatibility of 2.4.1 with my system.

That seems a bit odd. Are you sure you have cut out the "<" symbols relating to ssl certificate/key paths, and that the certificates are the full-chain certs?

Anyhow, with reference to https://github.com/rorycl/dovecot-config, you can easily debug your issue with Dovecot 2.4.1's official docker image. Simply edit the provided dovecot.conf to include your ssl settings and the debugging log to stderr should quickly show you where your issue is in a safe environment.

Be aware that if you run docker from the local directory with your dovecot.conf etc to load into docker you need to use the --volume/v or --mount options to put that directory at /etc/dovecot in the container:

docker run -p 1143:143 -p 1993:993 \
-v ./:/etc/dovecot \
dovecot/dovecot:latest

If you have specified ssl files at, for example, /etc/dovecot/ssl, you need to put your ssl certificates and keys in an ssl directory of the current directory, or make another -v / --mount mount.