Hotmail and Outlook.com bounced some business email for nearly three days: Microsoft has fixed it
11 November 2026Microsoft says a faulty spam rule update made Outlook.com, Hotmail and Live wrongly block some email from 06/11 to 09/11/2026. It has rolled the update back. If your mail to those addresses still bounces, tell your IT person.

What happened
Microsoft says that from Friday evening, 06/11/2026, to late morning on Monday 09/11/2026, some email sent to Outlook.com, Hotmail.com and Live.com addresses bounced back. It was on and off: Microsoft says some senders were "intermittently" unable to get mail through. Microsoft now says the cause was its own mistake: "A recent update to the spam enforcement rules caused email messages to be incorrectly marked and blocked, which led to impact." It says it has "fully rolled back this update and confirmed that mail flow has been restored and impact is resolved."
On 11/11/2026 a Microsoft spokesperson told The Register it had fixed the bug and was "continuing to monitor" the problem.
Does this affect you
Only if you or your team email customers on Outlook.com, Hotmail or Live addresses and got bounce messages over that weekend. A bounce is the automatic email that tells you a message wasn't delivered; Microsoft calls it a non-delivery report. Microsoft says these ones showed the code 550 5.7.1 or 550 5.7.23 and mentioned SPF.
What to do
- Nothing, if your email to those addresses is going through again.
- If anything important bounced between 06/11 and 09/11, send it again.
- If you get a 550 5.7.23 bounce from now on, the fault is most likely at your end. Microsoft's help for that code says it "most likely indicates a Sender policy framework (SPF) configuration issue" in the sender's own setup, and that "Only an email admin" can fix it. Give the whole bounce message to your IT person and keep it: while the fault was live, Microsoft asked for examples saved as .eml files with their message IDs.
- Worth doing anyway: ask your IT person or web host whether your domain has SPF, DKIM and DMARC records. In the NCSC's words, SPF lets you "publish the email systems that you trust to send emails from your domain", DKIM lets you "cryptographically sign an email to show it has come from your organisation", and DMARC "tells other computers online how to handle malicious emails that use your domain name". The NCSC's free Check your cyber security service checks all three: you type in your domain, and it "looks at publicly available information only" and needs no software.
Is it being attacked?
No. Microsoft says the cause was its own spam rule update, not an attack.
Found by
Not applicable. This was an outage, not a flaw anyone found. Tag: not stated.
For developers
- Microsoft 365 incident EX1545193, service Exchange Online, feature group "E-Mail timely delivery", classification incident, status serviceRestored. Start 06/11/2026 18:00 UTC, end 09/11/2026 11:02 UTC (Microsoft's figures). Final update posted 10/11/2026 05:36 UTC ("This is the final update for the event"); the record's last-updated time is 05:38 UTC.
- A Microsoft Q&A thread reporting 550 5.7.23 bounces was opened at about 09:05 UTC on 06/11/2026, so some senders saw bounces before Microsoft's stated start.
- NDRs: Microsoft lists 550 5.7.1 or 550 5.7.23 "due to" an SPF violation (its incident text expands SPF as "Service Provider Foundation"; it is Sender Policy Framework). Microsoft Learn's NDR table: "5.7.23 The message was rejected because of Sender Policy Framework violation".
- Microsoft's next steps: "We're reviewing our update procedures and improving our mail detection logic to lower the false positive rate and ensure that legitimate email messages aren't inaccurately blocked."
- Microsoft's final update does not mention DMARC. Some users reported that setting SPF, DKIM and DMARC to Microsoft's requirements got their mail flowing again while the fault lasted (The Register); others reported rejections with all three already correct (Microsoft Q&A). Microsoft doesn't say why either happened.
- Microsoft's Outlook.com sender requirements of 02/04/2025 apply to "domains sending more than 5,000 emails per day"; its FAQ adds "all senders benefit from these best practices".
- The Register (updated 09:48 UTC, 11/11/2026): a Microsoft spokesperson described it as "an issue that may have prevented some email messages from reaching Outlook.com, Hotmail and Live addresses", said Microsoft is "continuing to monitor", and added "Customers can learn more via EX1545193 in the Microsoft 365 admin center."
- The incident sits in the Microsoft 365 admin centre behind a login. The University of Pennsylvania publishes an extract of Microsoft's incident reports from its own admin console, refreshed every 15 minutes and covering the last 30 days.
Sources
- Microsoft 365 incident EX1545193, via the University of Pennsylvania's extract of Microsoft's incident reports
- The Register, 09/11/2026, updated 11/11/2026
- Microsoft Learn, Fix NDR error 5.7.23 in Exchange Online
- Microsoft Learn, Email nondelivery reports (NDRs) and SMTP errors in Exchange Online
- Microsoft Q&A, SPF Validation Error, opened 06/11/2026
- Microsoft, Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders, 02/04/2025
- NCSC, Check your cyber security, email security check
Read next
More from The Patch Wave
- Act today

iPhones, iPads and Macs: update today, Apple has patched a compression flaw already on the US exploited list
Apple's 09/11/2026 updates fix the Brotli flaw CVE-2026-111497, which CISA added to its exploited list on 27/10/2026, and an iMessage group chat flaw. Update iPhones, iPads and Macs today.
- Act today

Microsoft Outlook: November's updates fix a flaw attackers are already using
Microsoft says attackers are already using an Outlook flaw (CVE-2026-124194) fixed in this month's updates. Update Office and run Windows Update today.
- Act today

Google Chrome: update today, attackers are already using a new flaw
Google says an exploit for a new Chrome flaw, CVE-2026-125350, exists in the wild. It is fixed in Chrome 157.0.8103.50: relaunch Chrome today and check the version. Microsoft has not released the Edge fix yet.