Topic · Troubleshooting
MTA-STS MX mismatch
An MTA-STS MX mismatch occurs when the actual recipient MX hostname is not allowed by the domain's policy patterns.
Email Security Glossary·Practical guidance
01 / How it works
How it works
A sending MTA compares discovered MX names to the published HTTPS policy under applicable enforcement rules.
02 / What can go wrong
What can go wrong
A mail provider migration can cause blocked deliveries if policy MX entries lag behind DNS updates.
03 / What to check or do
What to check or do
Compare every live MX host with policy patterns and coordinate staged policy updates before cutover.
Practical diagnosis
How to investigate MTA-STS MX mismatch
- Signal to investigate
- A strict sender rejects a secondary MX not named by MTA-STS policy.
- Evidence to collect
- Compare actual MX hostnames against every mx pattern in the fetched policy.
- Common wrong conclusion
- A working STARTTLS handshake does not override the policy hostname constraint.
NEXT STEP
Put this into practice
Run a focused check, then explore protection if your domain needs it.