Deliverability News

Outlook.com Started Bouncing Legitimate Mail. The Rule Was Written for High-Volume Senders.

In the first days of November 2026, senders to Outlook.com and Hotmail began getting 550 5.7.1 bounces over a missing DMARC record — including senders far below the 5,000-a-day threshold Microsoft's rule targets. Here is what the rule actually says, and the check to run today.

9 November 2026 — 7 min read — LMR Studio

In the first days of November 2026, senders trying to reach Outlook.com and Hotmail began receiving bounce messages that had nothing to do with their campaigns. The non-delivery reports carried 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records — with the reference AS9031519 — and a variant that named SPF instead, 550 5.7.23. By 9 November, when The Register reported that the error had stopped Outlook.com accepting legitimate mail, threads on Microsoft's own support forum had collected 70-plus "same question" votes. The senders complaining were not the ones the rule behind the error was written for.

That rule is documented, and it is narrow. The requirement Microsoft publishes for 550 5.7.515 Access denied, sending domain <domain> does not meet the required authentication level applies to a defined class of sender: one sending 5,000 or more messages to Microsoft's consumer email services — Outlook.com, Hotmail, Live.com, MSN — with every message using the same domain in the 5322.From address. Cross that line and the domain is expected to publish SPF and DKIM (both must pass), publish a DMARC record, and pass DMARC validation with the SPF or DKIM domain aligned to the visible From address. Microsoft's own example of the DMARC record is the minimum: v=DMARC1; p=none.

Below 5,000 a day, the page asks for nothing. The November bounces did not observe the threshold, and that gap — between the rule as written and the rule as it behaved — is the whole story.

What the bounces looked like

The reports on Microsoft's forum read like a switch being thrown. A sender whose "server was working fine all along" was suddenly blocked. Another wrote that codes which had "worked for years now have email failure." One described "about 50% of my clients that have emailed me since yesterday" getting the rejection. The Register saw the same thing from the outside: the trouble began at the end of the previous week, small senders now appeared affected, a single one-line email could be rejected, and Microsoft had issued no advisory to customers explaining what had changed.

For most of the affected senders, one record explained it. A poster on the Microsoft thread traced mail from a Microsoft 365 tenant to Hotmail that bounced with a "SPF validation error" while both SPF and DKIM were fine. The message headers said dmarc=pass, but there was no DMARC record at all — because Microsoft 365 does not create one. Adding a _dmarc TXT record, v=DMARC1; p=none; rua=mailto:…, got the mail accepted.

Microsoft called it a service degradation

A moderator in Microsoft's support forum acknowledged the problem and, as The Register reported it, gave it a name:

"...classified as a service degradation." "Microsoft is actively investigating the underlying cause of this email delivery issue, and engineering teams are actively analyzing service telemetry and customer-provided data to identify the source of the issue."

The Register, 9 November 2026, quoting a Microsoft support-forum moderator

Two things follow from the word "degradation." It is not an announced policy change: the documented rule still reads as a high-volume requirement, and Microsoft has published nothing that extends it to ordinary senders. And the symptom is intermittent — The Register notes that a resend might succeed after a rejection, which is the shape of a regression rather than a policy switch. What Microsoft has not said is whether the stricter behaviour is intended and merely under-described, or unintended and about to be reverted. Until it does, the practical move is the same either way.

Why to act on something Microsoft calls a bug

Because a bug can be reverted, and a bounced password reset is still a bounced password reset. The fix here is a one-line DNS change against a failure mode that arrives silently: mail that never lands, and a bounce that names an authentication record you believed you already had. For a low-volume sender this is defence in depth rather than a compliance deadline, and it is cheap.

There is also a diagnostic trap worth naming. The bounce headline said "SPF validation error," but the actual cause in the traced cases was a missing DMARC record. Read the detail line — the one that says the message lacks SPF, DKIM or DMARC auth records — rather than the subject line of your own bounce, because the two point at different fixes.

The check to run this week

The one-line version

The rule was written for senders over 5,000 messages a day. In November it started bouncing mail from senders far below that, over a record that takes one DNS line to add. Publish the DMARC record whether or not the rule says you must. The cost is a TXT record; the alternative is finding out from a customer that your mail stopped arriving — after Microsoft has decided whether this was a change or a mistake.

Sources

  1. Microsoft Support — Fix NDR error "550 5.7.515" in Outlook.com (high-volume sender definition and the SPF/DKIM/DMARC requirements)
  2. Microsoft Q&A — SPF Validation Error (published 6 November 2026; AS9031519, 550 5.7.23 and 550 5.7.1 reports)
  3. Microsoft Q&A — 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (6 November 2026; the missing-DMARC fix)
  4. The Register — Outlook.com bounces legit emails as Microsoft's authentication crackdown goes sideways (9 November 2026)
  5. Microsoft Tech Community — Strengthening Email Ecosystem: Outlook's New Requirements for High-Volume Senders (the announcement the support page links to)

Written by the team at LMR — a senior lifecycle marketing studio working in Iterable, Braze, Klaviyo and the tools you already run.

Start a project ↗