Email Security / ARTICLE

Outlook.com Begins Rejecting Some Email from Domains Without DMARC

Starting November 5, 2026, Outlook.com, Hotmail, Live, and MSN addresses have bounced some messages from domains without a DMARC record. A single TXT record with v=DMARC1; p=none is the fix.

Starting November 5, 2026, Microsoft’s consumer mail service has been turning away some messages from domains that publish no DMARC record. Outlook.com, Hotmail, Live, and MSN addresses can all bounce affected mail. There was no announcement. The fix is a single DNS TXT record.

What the bounce looks like

Senders receive a rejection like the following, with the bracketed server name and ID changing per message:

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

On the first day, the same rejection appeared without the (AS9031519) code. The wording can make authentication look completely broken. Most of the time it isn’t. Affected domains seen in these bounces usually had working SPF, and many had DKIM too. What they lacked was the DMARC record that ties those checks to the From address.

What changed

Microsoft published sender rules earlier. Since May 2025, domains sending more than 5,000 messages per day to Outlook.com must pass SPF, DKIM, and DMARC or receive 550 5.7.515 Access denied. That rule targets bulk senders and marketers; small senders largely assumed it didn’t apply to them.

The new rejection differs in three ways. It reaches low-volume senders, including one-line replies from a small office. It was not announced, and as of November 6 Microsoft had published no postmaster notice, blog post, or service-health entry. It also doesn’t state what failed. A 5.7.515 bounce lists SPF, DKIM, and DMARC results; this one only says records are missing.

Why the problem is easy to miss

Microsoft refuses only part of the mail from an affected domain. One message to a Hotmail address goes through, the next bounces, and a resend may succeed. That inconsistency lets the problem hide. The sender sees a bounce full of acronyms, assumes a glitch, and moves on. The person on the receiving end never knows a message was sent. Businesses that depend on reaching personal addresses—patients, homeowners, applicants, parents, members—can lose invoices, appointment confirmations, and replies without seeing a hard failure.

Checking and fixing

Use dig to check whether a domain has a DMARC record:

dig +short TXT _dmarc.example.com

Replace example.com with the real domain. Output starting with v=DMARC1 means a record exists. No output means it doesn’t, which is what this rejection targets.

Add a TXT record at the DNS host:

Name: _dmarc Value: v=DMARC1; p=none

p=none is a safe starting point. It declares that the domain uses DMARC and asks receivers to send reports, but it instructs them to take no action on failures. It doesn’t change how Gmail, Yahoo, or other providers treat the domain’s mail.

DMARC passes only when SPF or DKIM passes for the domain in the From address. If neither aligns, a DMARC record alone won’t help. For mail sent through an outbound relay that already passes SPF and DKIM as the domain, the DMARC record is the whole fix.

END
Feedback