All articles

Outlook.com is bouncing mail from domains without DMARC

Since November 5, senders report Outlook.com and Hotmail rejecting mail from domains with no DMARC record, at any volume. Microsoft hasn't confirmed it, but the fix is quick.

Since around November 5, 2026, senders have been reporting bounces from Microsoft's consumer mailboxes (Outlook.com, Hotmail, Live and MSN) with a new error. Windows Latest covered it on November 8, and EasyDMARC published a write-up on November 9 after reproducing it. The common thread in those reports: the sending domain has no DMARC record.

Microsoft hasn't announced anything. As of November 8, EasyDMARC said it found no blog post, no postmaster notice and nothing on the known-issues list. So treat the cause as unconfirmed. But the bounces are real, and the likely fix takes five minutes.

What the bounce looks like

The new rejection reads:

550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)

Some senders, including some with SPF, DKIM and DMARC all set up, have also reported 550 5.7.23 SPF errors. EasyDMARC treats those as a separate problem, and Windows Latest says there's no confirmed fix that covers every report.

Why this is different from the 2025 rules

Microsoft already requires DMARC from high-volume senders. Since May 2025, domains sending more than 5,000 messages a day to Microsoft consumer addresses have needed SPF, DKIM and a DMARC record of at least p=none.

What's new, according to these reports, is that there doesn't seem to be a volume threshold. Small senders well below 5,000 a day are seeing rejections. That includes the domains most likely to have skipped DMARC: a brand's secondary sending domain, a microsite, a regional store, or an agency's own domain.

It's intermittent, so a passing test isn't proof

This is the part that catches people out. Both sources say the rejections come and go. Windows Latest describes a Zoho message rejected at 3:50 p.m. that then arrived at 4:09 p.m. on retry. So a single test send to your Hotmail seed address isn't proof that you're fine. Check your DNS records instead of relying on a test.

What to do

  1. List every domain that sends email. Include ESP sending domains, transactional senders, support desks and any old subdomains still in use.
  2. Check each one for a DMARC record at _dmarc.yourdomain.com. Any DMARC lookup tool will do.
  3. If there isn't one, publish a starter record. In the reports so far, adding one, even at p=none, stopped the rejections:
_dmarc.yourdomain.com  TXT  "v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com"
  1. Make sure SPF and DKIM align with your From domain. DMARC passes only when one of them aligns.
  2. Read your reports, then move towards p=quarantine and p=reject once you know every legitimate sender is covered. On its own, p=none doesn't protect you from spoofing.
  3. Watch bounce logs for AS9031519 over the next couple of weeks, and keep the full bounce text if you need to raise it with your ESP or Microsoft.

For agencies and brand teams

If you send on behalf of clients, this is worth a quick sweep across your accounts this week, especially with holiday campaigns about to go out. Outlook.com and Hotmail addresses make up a large share of many consumer lists, and a silent bounce looks like a quiet campaign rather than an error.

It's also a good reminder that deliverability and email development overlap. A beautifully coded email that never reaches the inbox doesn't do anyone much good.

I'll update this post if Microsoft confirms the change or publishes guidance.

Related on the Journal

If you'd like help checking your sending setup as part of a pre-send QA, get in touch.

Sources

Work with me

Need this handled in your templates?

Send me your design file or the HTML that's misbehaving. You'll get a clear scope, timeline and quote within 1 business day.