Subscribe
0%
Illustration for: Outlook.com has started bouncing some mail from domains with no DMARC record. How to check yours and fix it in minutes

Outlook.com has started bouncing some mail from domains with no DMARC record. How to check yours and fix it in minutes

Since November 5, senders report "550 5.7.1 … lacks SPF/DKIM/DMARC Auth Records" bounces when mailing Outlook.com, Hotmail, Live and MSN addresses, even at low volume. Microsoft hasn't announced anything. Adding one DNS record usually fixes it.

Listen to this article0:00 / 5:01

Microsoft's consumer email service has started rejecting some messages from sending domains that have no DMARC record. Email security vendor MailRoute says the bounces started on November 5 for mail sent to outlook.com, hotmail.com, live.com and msn.com addresses. The bounces carry this error:

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

This matters because it hits ordinary senders, not just bulk mailers. Small businesses, side projects and SaaS apps sending signup emails, password resets and receipts can find mail to a big share of personal inboxes failing. And because only some messages bounce, a test email that arrives doesn't prove your domain is fine, MailRoute warns.

What's confirmed and what isn't

  • No announcement. MailRoute (November 6) and byteiota (November 9) both say Microsoft has published nothing about the change. Affected senders are comparing notes in a Microsoft Q&A thread.
  • Not the old bulk-sender rule. Microsoft's published requirement, in force since May 2025, covers domains sending more than 5,000 messages a day to Outlook.com. Those fail with a different code, 550 5.7.515 Access denied. The new AS9031519 bounce also hits low-volume domains, and unlike the old error, it doesn't say which check failed.
  • The pattern is intermittent. Suped gathered reports from November 5–6 and is more cautious. It calls the rejections intermittent and says they don't yet prove a new policy across all Exchange Online recipients. One Zoho-sent message it cites was rejected, then delivered when resent.
  • Adding DMARC appears to stop it. In the Hacker News discussion, several senders say mail with valid SPF and DKIM but no DMARC record was fine until the past few days. They say bounces stopped once they published a record. One affected sender was on Google Workspace. Gmail delivery wasn't affected.

DMARC's standard (RFC 7489) lets receiving servers choose how to treat mail from domains with no DMARC record. So rejecting it is within the rules, even if it happened without notice.

How to check your domain

Run this from any terminal, replacing the domain:

dig +short TXT _dmarc.example.com

If the output starts with v=DMARC1, you have a record. If nothing comes back, you don't. Web tools such as MXToolbox's DMARC lookup do the same check.

How to fix it

  1. Make sure SPF or DKIM passes for your From domain. DMARC only passes when one of them passes and aligns with the domain in the From address. A DMARC record on its own isn't enough.
  2. Add one DNS TXT record at your DNS host:

    • Name/host: _dmarc
    • Value: v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com

    p=none only asks receivers to send you reports. It doesn't tell them to block anything, so it's the safe starting point. Publish only one DMARC record: byteiota notes that with duplicates, receivers ignore both.

  3. Wait for DNS to update. byteiota says this usually takes 15 minutes to an hour. Then resend anything that bounced.
  4. Check the platform-specific gaps:
    • Microsoft 365: The setup wizard doesn't create a DMARC record. Until you turn on DKIM for your own domain, mail is signed with the onmicrosoft.com domain, and that signature doesn't count toward your domain's DMARC, according to MailRoute. Turn on DKIM in the Defender portal and publish the two CNAME records it gives you.
    • Google Workspace, SendGrid, Postmark, Amazon SES: None of these add DMARC for you, per byteiota. Add the _dmarc record yourself.
  5. Tighten later. After a few weeks of reports show your real senders passing, move to p=quarantine and then p=reject to block spoofing. Suped advises against the reverse: don't weaken a working stricter policy to p=none just to chase these bounces.

If bounces continue after you add DMARC

Suped suggests grouping bounces by exact code, timestamp, sending service and receiving host. Check SPF for the envelope sender and sending IP, and confirm DKIM signing and alignment. If the problem keeps coming back, send redacted bounce messages and logs to Outlook.com's sender support.

Who should act today: anyone who runs a custom-domain mailbox, a newsletter, or an app that sends transactional email. Personal domains on hosted email are included. If dig returns nothing for your domain, the fix takes five minutes.

Sources

  1. MailRoute — Outlook.com Is Quietly Rejecting Email From Domains Without DMARC mailroute.net
  2. Suped — Senders report Outlook.com email authentication bounces suped.com
  3. byteiota — Outlook Is Rejecting Your Emails Since Nov 5 — Fix It Now byteiota.com
  4. Hacker News — Outlook.com is rejecting email from domains without DMARC (discussion) news.ycombinator.com

#Microsoft#Outlook.com#DMARC#email deliverability#DNS#SPF#DKIM