Most common causes
- The published MTA-STS policy does not include the active MX hostname
- MX records changed but the MTA-STS policy was not updated
- A backup MX or failover host is missing from policy
- Cached policy and current DNS describe different transport paths
What to verify next
- Run Mail Transport Security for the destination domain
- Compare every active MX hostname with the published MTA-STS mx patterns
- Review recent MX, gateway or failover changes
- Publish a consistent policy and allow normal policy/DNS cache propagation before retesting
Best diagnostic path
Live analysis
Mail Failure Doctor
Classify the complete rejection and preserve provider-specific diagnostic context.
Open analysis → Live analysisMail Transport Security
Inspect MX, TLS, MTA-STS and transport-policy evidence for the destination.
Open analysis → Live analysisEmail Infrastructure Digital Twin
Map the domain’s public mail infrastructure and provider relationships before remediation.
Open analysis →Why the exact message matters
The same status family can be triggered by different conditions, and providers frequently add diagnostic text that narrows the issue. Use the complete rejection text rather than treating the numeric code as a complete diagnosis.
Provider reference
For the provider-defined meaning and current requirements, review Microsoft Exchange Online NDR reference.