When Messaging Gateway (SMG) is configured to require TLS delivery from a specific domain and to verify the certificate, SMG is not accepting delivery from the sender even when they have a valid TLS certificate.
2010 Aug 17 19:01:11 GMT (debug) ecelerity: [6390] Host Name: mx1.example.com 2010 Aug 17 19:01:11 GMT (debug) ecelerity: [6390] Host SSL certificate Subject: /C=US/ST=State/L=Locality/O=Company Co/CN=server1.example.com 2010 Aug 17 19:01:11 GMT (debug) ecelerity: [6390] Subject Common Name: server1.example.com 2010 Aug 17 19:01:11 GMT (info) ecelerity: [6390] Subject Common Name does not match host name 2010 Aug 17 19:01:11 GMT (info) ecelerity: [6390] DNS Subject Alternative Name does not match host name
The SMG TLS certificate validation operates in this order:
If the DNS hostname referred to by the domain's MX records do not match the common name (CN) attribute of the certificate Subject or Subject Alternative Name then certificate validation will fail and a secure connection cannot be established.
This may be resolved if you modify the TLS policy for the domain to "Require TLS and don't verify certificate".