Update 11/13/2023: We added new information on how to know when this change is released to your organization.
Today, we are announcing an update to our requirements for SMTP relay through Exchange ...
Updated Feb 22, 2024
Version 19.0
Blog Post
thank you for the immediate response. I have few questions here -
- In our set up , multiple exchange online tenants can send their emails to our server. But there is no specific certificate for every Exchange tenant, there is only one certificate(with one subject name and an alternate name). So can all the exchange tenants add the certificate subject name as an accepted domain?
- If yes, what is the implication, will it cause the emails from one tenant to mix with another?
- Is only the certificate subject name checked with the accepted domains, or the alternate subject names also checked?
- How can we verify if this approach of adding the certificate domain as accepted domain will work after Nov 1st from extended message trace report?
- One more question- may be slightly out of topic, but when we tried to make the inbound connector as a Partner Org connector, (instead of Your Org connector) we get this error: "50 5.7.64 TenantAttribution; Relay Access Denied ' for external mails. Is it because the accepted domain of our server does not contain an MX record? We tried adding the ips to the SPF record, still it does not work.(This is for Partner Org type Inbound connector)
Thanks