One of my customers is setting up a send connetor on their Exchange 2010 edge server to allow all e-mail sent to my organization to be encrypted using TLS. He would like to enable mutual TLS on his end but it is failing because the 2 edge appliances on my end (Not Exchange) have the certifiactes with the names of mail1.mydomain.com and mail2.mydomain.com. The mutual auth is failing because it is looking for a cert with mydomain.com name. Is there a way to configure the send connector on his end to use mutual auth TLS and accept the names of mail1.mydomain.com and mail2.mydomain.com?

Is the send connector configured to use MX records (DNS) or is it sending to a smarthost?lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

So it sounds like your partner needs to configure the settings on his send connectors so they work with the domain names you have on your certificates? Wouldn't this cmdlet allow him to configure that: Set-TransportConfig -TLSSendDomainSecureList woodgrovebank.comFrom:http://technet.microsoft.com/en-us/library/bb123543.aspx

You obviously add your domain name(s) instead of Woodgrove bank.

So it sounds like your partner needs to configure the settings on his send connectors so they work with the domain names you have on your certificates? Wouldn't this cmdlet allow him to configure that: Set-TransportConfig -TLSSendDomainSecureList woodgrovebank.comFrom:http://technet.microsoft.com/en-us/library/bb123543.aspx