I confirm it was a SNI issue. Some people were using custom MX names
pointing to our IPs, and some senders didn't like the default certificate.
Thank you all!
Camille
Le 12/09/2023 à 15:04, Taavi Eomäe via mailop a écrit :
On 12/09/2023 15:33, Bill Cole via mailop wrote:
Your CA (LetsEncrypt) says that is breakage and they offer a fix.
Take it or leave it, but saying that it isn't broken is wrong.
It is not wrong.
There's a valid and trusted path, that is sufficient. If your TLS
client does not build certification paths properly then that's a flaw
in the software. There is a lot of discussion on this subject so
there's no point in continuing that here.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
