Emails to Outlook.com and Hotmail bounced in November 2026: what happened, and what senders and recipients should do

For several days in early November 2026, emails to Outlook.com, Hotmail and Live addresses came back with SPF errors, even from senders whose settings were correct. Microsoft says a faulty update to its spam rules caused it and that it has been rolled back. How to tell if your mail was hit, why it will not arrive by itself, and how this differs from Microsoft's permanent rules for bulk senders.

Published Facts checked 6 min read
Two different Outlook.com rejections. The November 2026 incident: errors 550 5.7.23 or 550 5.7.1 Message lacks SPF/DKIM/DMARC Auth Records, from about 5 November, hit senders of any size, caused by a faulty spam rule update that Microsoft rolled back, so resend the message. The bulk sender rule: error 550 5.7.515, applies to domains sending 5,000 or more emails a day to Outlook.com, is permanent since May 2025, and is fixed by passing SPF and DKIM with an aligned DMARC record.
The error code tells you which problem you have.

From about 5 November 2026, some emails sent to Outlook.com, Hotmail.com and Live.com addresses were rejected with SPF errors, including mail from senders whose SPF, DKIM and DMARC records were correct. Microsoft says the cause was its own mistake. A Microsoft support moderator, citing service incident EX1545193, wrote on 10 November that “the issue was caused by a recent update to spam enforcement rules, which incorrectly identified some legitimate emails as SPF violations” and that Microsoft “has since rolled back the change and confirmed that mail flow has been restored.”

In short:

  • It was a bug, not a new rule. Microsoft calls it a faulty update that it reversed. A Microsoft spokesperson told The Register it had fixed “an issue that may have prevented some email messages from reaching Outlook.com, Hotmail and Live addresses.”
  • Bounced mail will not arrive by itself. The same moderator wrote: “If any emails failed to deliver during the affected period, users may need to resend those messages.”
  • The error codes were 550 5.7.23 and 550 5.7.1, not 5.7.515. If you see 5.7.515, that is Microsoft’s separate, permanent rule for senders of 5,000 or more emails a day.
  • Worth doing anyway: check that your domain has SPF, DKIM and a DMARC record.

What happened

Reports started on Microsoft’s own Q&A forum on 6 November (“we suddenly received this error today”), and Windows Latest reported that “emails have been rejected since at least November 5”. On 9 November, a Microsoft staff moderator on the forum described “an ongoing Exchange service issue” affecting messages “to Outlook.com, Hotmail.com, or Live.com addresses”, with senders receiving “Non-Delivery Reports (NDRs) citing 550 5.7.1 or 550 5.7.23 errors related to SPF validation failures.”

The rejections were not limited to one email provider or to badly configured domains. One forum user wrote that “about 50% of my clients that have emailed me since yesterday are getting the message”, and another saw a message from a Zoho user rejected and then accepted when it was sent again 19 minutes later. According to The Register, Microsoft’s incident report said: “A recent update to the spam enforcement rules caused email messages to be incorrectly marked and blocked, which led to impact.”

By 10 November, Microsoft listed the incident as Service Restored, and on 11 November a spokesperson said Microsoft was “continuing to monitor”. Administrators can read the incident, EX1545193, in the Microsoft 365 admin center.

The error messages

Senders who were hit received a bounce (a non-delivery report) with text like this, quoted from reports on Microsoft’s forum:

  • hotmail.com couldn't confirm that your message was sent from a trusted location. with SPF validation error and Status code: 550 5.7.23
  • 550 5.7.23 The message was rejected because of Sender Policy Framework violation
  • 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)

If your bounce has one of these, dated in early November 2026, it was very likely this incident.

How to tell if you were affected

If you send email:

  1. Search your inbox for bounces from about 5 to 10 November 2026 that mention 5.7.23, 5.7.1 or SPF validation error, sent to addresses ending in outlook.com, hotmail.com or live.com.
  2. If you find any, send those messages again. Microsoft did not say that rejected mail would be redelivered, and a bounce means the message was never accepted.
  3. If you sent nothing important to those addresses in that period, there is nothing to do.

If you have an Outlook.com or Hotmail address:

  1. If you were waiting for an email in early November that never came (a reply, an invoice, a sign-in code), ask the sender to send it again. Their copy bounced back to them; it is not hidden in your mailbox.
  2. Check your Junk Email folder as well. Mail that was accepted but judged as spam goes there, and adding a sender to your safe senders list keeps future messages out of Junk. A safe senders entry would not have stopped this incident, because the mail was rejected before it reached you.
  3. To report a delivery problem to Microsoft, use Help > Feedback > Report a problem in Outlook.com, as a volunteer moderator on Microsoft’s forum advised.
Decision tree for an email to Outlook.com that bounced. Does the bounce say 550 5.7.515? If yes, the bulk sender rule applies: make SPF and DKIM pass and publish an aligned DMARC record, then resend. Does it say 550 5.7.23, or 550 5.7.1 lacks SPF/DKIM/DMARC Auth Records, between about 5 and 10 November 2026? If yes, it was Microsoft's faulty rule update, now rolled back: resend the message. Otherwise, check SPF, DKIM and DMARC for your domain and read the full bounce text.

Not the same as the 5,000-a-day rule

Microsoft has had a deliberate rule for bulk senders since 2025. Its announcement says that “for domains sending over 5,000 emails per day”, messages must pass SPF and DKIM and have a DMARC record of “at least p=none” that aligns with SPF or DKIM. Since May 2025, mail that fails is rejected with a different code, which Microsoft’s support page gives as:

550 5.7.515 Access denied, sending domain <domain> does not meet the required authentication level.

For that rule, Microsoft’s FAQ adds that adding a sender to safe senders does not help: “Safe Sender list won’t be honored.” Our article on the Gmail, Yahoo and Outlook.com sender requirements explains who it applies to and what to set up.

The November incident was different: it used other codes (5.7.23 and 5.7.1), hit senders of every size, and Microsoft reversed it.

Check your own domain

Many senders reported that adding a DMARC record made the rejections stop during the incident, though a volunteer moderator also noted “intermittent rejections from domains where SPF, DKIM and DMARC are already correctly configured”. Either way, a domain with a valid SPF record, DKIM signing and at least a v=DMARC1; p=none DMARC record is better placed with every large mailbox provider.

Mailtria’s free SPF, DKIM and DMARC checker shows all three for your domain in the browser. If you have a bounce in front of you, the email header analyzer reads the authentication results in a message’s headers.

Frequently asked

Was this a new Microsoft rule? No. Microsoft’s support moderator, citing the incident report, said it was “a recent update to spam enforcement rules, which incorrectly identified some legitimate emails as SPF violations”, and that Microsoft rolled it back.

Is it fixed? Microsoft marked incident EX1545193 as Service Restored by 10 November 2026 and said on 11 November that it was continuing to monitor.

Will the bounced emails arrive later? No. A bounce means Microsoft refused the message. Microsoft’s moderator said users “may need to resend those messages.”

What does AS9031519 mean? It appeared in many of the 5.7.1 bounces during the incident. Microsoft has not published a description of it.

Do I need DMARC if I send only a few emails a day? Microsoft’s strict rule applies at 5,000 or more emails a day to its consumer addresses. A basic DMARC record is still good practice for any domain, and many senders found it helped during this incident.

My bounce says 5.7.515. Is that this incident? No. 5.7.515 is the permanent rule for bulk senders: your domain’s mail did not meet Microsoft’s authentication requirements, and resending without fixing SPF, DKIM and DMARC will fail again.

Sources

This article is general information, not legal, security or professional advice. Services change their rules and screens; check the official pages linked above before you act, and keep a backup before changing your mail.

SPF, DKIM and DMARC CheckerCheck a domain's email records and what to fix. Free, no sign-up; it only reads the domain's public DNS records.
Open SPF, DKIM and DMARC Checker