Outlook.com, Hotmail, and Live addresses started bouncing clean email on November 5, 2026, and the cause was DMARC email rejections, not spam. Microsoft’s rule was only supposed to catch senders blasting out 5,000 or more messages a day. For five days, it caught small businesses, schools, and law firms too, before Microsoft quietly rolled it back.
Key takeaways
- Outlook.com, Hotmail, and Live started rejecting legitimate email from domains without a DMARC record on November 5, 2026, even when SPF and DKIM passed.
- The rejections hit small businesses, nonprofits, schools, and MSP clients, senders Microsoft’s 2025 bulk-sender policy wasn’t supposed to touch.
- Bounces weren’t consistent: the same domain could see messages flip between delivered and rejected within minutes.
- Microsoft restored normal mail flow by November 10, and it still hasn’t published a detailed postmortem.
What Caused the DMARC Email Rejections at Outlook.com?
Microsoft’s spam filters started enforcing DMARC on messages they weren’t supposed to touch. DMARC tells a receiving server whether to trust a message from your domain, built on SPF (confirms the sending server is authorized) and DKIM (confirms the message wasn’t altered). According to CSO Online, Microsoft has required DMARC only from bulk senders since May 2025. Once November 5 hit, that line disappeared, and senders with no DMARC record got rejected outright, some even with valid SPF and DKIM.
The error itself wasn’t helpful. Recipients saw non-delivery reports citing codes 550 5.7.1 or 550 5.7.23, and one, reported by CSO Online, read simply: “hotmail.com couldn’t confirm that your message was sent from a trusted location.” That tells an admin nothing useful.
Why Did Small Senders Get Hit Instead of Big Ones?
The whole point of the 5,000-message threshold was to leave small senders alone. This bug hit small businesses, nonprofits, and schools instead, per Expert Insights.
Frank Dickson of Dickson Research summed it up well, as quoted by CSO Online: “Requiring every sending domain to prove it is who it says it is makes email safer. Doing it without notice, with an error message that points at the wrong problem, makes a mess.” The policy goal wasn’t wrong. The rollout was.
How Long Did It Last, and Is It Actually Fixed?
About five days, and yes, Microsoft says it’s fixed. Sources disagree on the exact start: Expert Insights says November 4, while CSO Online and The Register say November 5. Either way, the pattern held: intermittent, not constant. One organization’s mail logs, cited by Expert Insights, showed messages “switching between delivered and bounced within minutes” on November 6. The Register says Microsoft tracked it internally as a service degradation, incident EX1545193, tied to “a recent update to the spam enforcement rules.”
Microsoft restored normal mail flow by November 10, per both CSO Online and Expert Insights. No one published a percentage of affected mail, so there’s no clean number for how big this really was.
How Does This Compare to Google’s Bulk Sender Rules?
Not well for Microsoft: this arrived as a bug, not an announced policy. Google went through its own authentication tightening in 2024, which mGrowTech covered in Gmail Began Rejecting Noncompliant Mail Outright. The two share a cause but not a character.
| Point | Google, 2024 bulk sender rules | Microsoft, November 2026 incident |
|---|---|---|
| Announced in advance | Yes, months ahead | No |
| Who it targeted | Senders over 5,000 messages a day, by design | Meant for the same group, leaked to small senders |
| Error clarity | Specific rejection reasons | Vague, generic bounce text |
| Duration | Permanent policy | Rolled back after about five days |
Here’s what I’d take from that table: a planned requirement is survivable because you can prepare for it. A bug that misapplies the rule is different, and no amount of compliance protects you from your provider’s own code.
What the DMARC Email Rejections Mean for Your List
If your domain already has valid SPF, DKIM, and DMARC, you still weren’t fully safe during this window. Authentication records lower your risk; they don’t erase it when the enforcement logic is buggy. A clean reputation and list matter more, not less, when rules can shift without notice.
Isn’t that the real lesson here?
Deliverability was never just a checklist you pass once. It’s how much damage a bad week does to your program when a provider changes behavior underneath you.
What to Do Before the Next Silent Enforcement Change
- Publish a DMARC record at p=none, even if you’re nowhere near 5,000 messages a day. It costs nothing and closes off one failure mode.
- Track bounce codes by category, not just by volume, so a spike in 550 5.7.x errors doesn’t blend into normal noise.
- Keep a backup delivery channel, like a transactional provider, for anything time sensitive that can’t wait out a provider-side bug.
- Re-verify your list before a big send. A clean, current list means fewer messages exposed when a provider’s filters get aggressive.
List accuracy is the part marketers can control. EmailAddress.ai, a company related to mGrowTech, builds catch-all verification that resolves accept-all domains other tools skip, using active inbox signals and SMTP analysis instead of guessing. It won’t stop a buggy filter update, but a verified list is one less variable to debug when bounces spike for reasons you don’t control.
Frequently Asked Questions
Did Microsoft announce the DMARC enforcement change before it happened? No. Both CSO Online and Expert Insights report Microsoft gave no advance notice through its postmaster channels. It only acknowledged the issue after senders started reporting bounces, and it described the fix after the fact rather than the change beforehand.
Does having SPF and DKIM protect you from this kind of bounce? Mostly, but not completely. CSO Online reported some domains with valid SPF and DKIM were still rejected during the window, because the bug reached beyond a single missing record. A full DMARC record is still the safer baseline to have in place.
Who was most affected by the bounces? Small businesses, nonprofits, schools, law firms, doctors’ offices, and managed service providers sending for clients, according to Expert Insights. These are exactly the senders Microsoft’s 5,000-message bulk-sender threshold was designed to exempt from this kind of rule, not catch by accident.
Is the issue fully resolved now? Microsoft says mail flow was restored by November 10, 2026, and that it would review its update process. No outlet has reported a recurrence since the fix, but Microsoft still hasn’t published a detailed postmortem explaining exactly what broke in its enforcement logic.
Sources: CSO Online (Taryn Plumb, November 9 to 10, 2026), Expert Insights (November 11, 2026), and The Register (November 9, 2026). See also mGrowTech’s coverage of Gmail’s bulk sender rules and email response rate trends.