On Thu, Oct 22, 2026 at 06:25:41PM +0200, H.-Dirk Schmitt wrote:
> > Is it not sufficient for your configuration to list the ssl_server_*
> > settings and omit the ssl_server block? The docs don't indicate a need
> > to define an ssl_server block in a normal configuration:
> >
> [1]https://doc.dovecot.org/2.4.5/core/config/ssl.html#configuration-overview
>
> I'm not sure. I migrated my old 2.3 configuration with the help
> of [2]https://dovecot.org/upgrader
> Wasn't the `ssl = true` the triggering point?
No, I had that in my config all along. What I posted earlier was only
what I suspected as the relevant part of the doveconf -n output; I
figured actually enabling ssl was assumed.
Try updating your config to drop the ssl_server {} block and see if that
resolves the issue for you. Based on what I've seen, I suspect it will.
Note that you can move the nested dh_file setting to a top-level
ssl_server_dh_file setting to go along with the rest of the top-level
settings.
If this works, that doesn't change the fact that this is a bug that
should be fixed, but it may reduce the urgency of it and let you move
back to the trixie packages.
noah
