Issued resolved...
Someone had actually copied the cert from the PF server to the DV cert location as well but renamed it to the same name that we had before. So when looking at the config, everything appeared proper but after Christian’s message, I decided to go and actually check the cert contents…it had been changed…
Thanks to Christian and darkc0de and sorry for the false alarm...and now need to go have a discussion with someone…
On Jul 25, 2020, at 2:43 PM, Antonio Leding <tech@leding.net> wrote:
Because the file containes the wrong certificate.
We must be miscommunicating…
The file that is configured in Postfix is being sent to the client..NOT the file cfg’d in Dovecot…
Prior to enabling TLS in Postfix, this exact same config worked fine...
On Jul 25, 2020, at 2:35 PM, Christian Kivalo <ml+dovecot@valo.at> wrote:
On 2020-07-25 23:31, Antonio Leding wrote:
CORRECTION: Just discovered that actually the Postfix cert is being sent to the client regardless of the configuration…so now the remaining question is why would is the PF cert sent rather than the cert I have configured in the dovecot.conf file? Because the file containes the wrong certificate.
-- Christian Kivalo