Mail Is Down
On Friday Contoso switched its email to a new domain, contoso.co.uk, and moved its mailboxes to Microsoft 365. Since then, emails to customers bounce, and customers say their replies bounce back too. Completion day for three house sales is today.
Three locks to open
- 1Find the cause. Why are customers' mail servers rejecting Contoso's email?
- 2Fix the records. Get mail authenticated and flowing both ways, without weakening anything.
- 3Prove it. Send a test both ways.
Every email I send to buyers comes back undelivered. Three completions today and the solicitors can't reach us.
Customers are ringing to say their replies to us bounce as well. The domain move was Friday. Tom did the DNS before he went on leave.
You escaped Mail Is Down
What happened
When contoso.co.uk was added to Microsoft 365, the Exchange DNS records were skipped. The MX record still pointed at the old mail host, so customers' replies went nowhere. The SPF record still listed only the old host, so Microsoft 365's servers failed SPF, and nothing was DKIM signed. The domain's DMARC policy was p=reject, so receivers did exactly what it asked and bounced every message.
How you'd fix it for real
- Read the bounce and the Authentication-Results header: which of SPF, DKIM and DMARC failed?
- Compare the domain's DNS with the records Microsoft 365 expects in the admin center.
- Point MX at Microsoft 365 and edit the single SPF record to include spf.protection.outlook.com.
- Create DKIM keys, publish both selector CNAMEs and enable DKIM signing.
- Test both directions, and allow for DNS caching (the record's TTL) in real life.
Stop it happening again
- Don't skip the Exchange DNS records when adding a domain. Add them before switching the default domain.
- Only ever have one SPF record per domain, and never end it in +all.
- Keep DMARC at reject, but read the aggregate reports (rua) so you see failures before customers do.