Outlook.com Rejected Mail From Domains Without DMARC
From November 5 to 9, 2026, Outlook.com and Hotmail bounced part of the mail from domains with no DMARC record. Microsoft says a faulty spam rule caused it.
From November 5 to 9, 2026, Outlook.com and Hotmail bounced part of the mail from domains with no DMARC record. Microsoft says a faulty spam rule caused it.

From November 5, 2026, Microsoft's consumer mail service turned away some of the email from domains that don't publish a DMARC record. If your company emailed customers, vendors or applicants with outlook.com, hotmail.com, live.com or msn.com addresses, some of that mail may have bounced. Nobody announced it at the time. The fix was one DNS record.
Key takeaways
v=DMARC1; p=none, got mail through. It changes nothing about how other receivers treat your mail, and it's still worth keeping.The sender got a bounce like this one, followed by a bracketed server name and ID that differ per message:
550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)
On the first day, the same rejection came back without the (AS9031519) code:
550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records
Microsoft's notice says some senders got 550 5.7.23 instead.
The wording suggests something is badly broken. Usually it wasn't. The domains we saw bounced mostly had working SPF, and many had DKIM too. What they were missing was the DMARC record that ties the two to the From address.
Microsoft does have published sender rules. Since May 2025, domains that send more than 5,000 messages a day to Outlook.com have had to pass SPF, DKIM and DMARC, or get 550 5.7.515 Access denied. That rule is aimed at marketers and bulk senders, and most small businesses rightly assumed it didn't apply to them.
This rejection was different in the ways that matter:
We first saw these bounces in our own outbound logs on November 5. Public reports from other administrators started appearing the same day.
Microsoft refused only part of the mail from an affected domain, and its own notice calls the problem intermittent. One message to a Hotmail address went through, the next one bounced, and a resend might succeed. That inconsistency is what made this one dangerous: the person who sent the message saw a bounce full of acronyms, assumed a glitch, and moved on. The customer on the other end never knew a message was sent.
If your business depends on reaching people at personal addresses (patients, homeowners, applicants, parents, members), the cost was quiet. Invoices that didn't arrive, appointment confirmations that never landed, replies that looked like you ignored someone. Outlook.com doesn't retry a refused message, so anything important that bounced in those days needs sending again.
You can check in a few seconds from any terminal. Replace example.com with your domain:
dig +short TXT _dmarc.example.com
A line starting with "v=DMARC1 means you have a record. No output means you don't. That was the case this rejection targeted.
Add a TXT record at your DNS host:
_dmarcv=DMARC1; p=nonep=none is the safe starting point. It declares that your domain uses DMARC and asks receivers to send you reports, but it tells them to take no action on failures. Nothing about how Gmail, Yahoo or anyone else treats your mail changes.
There is one condition. DMARC passes only when SPF or DKIM passes for the domain in your From address. If neither lines up, a DMARC record alone won't help. We covered how alignment works, and why it's where most setups go wrong, in SPF, DKIM, and DMARC Are No Longer Optional.
Step-by-step instructions, including the checks for all three records, are in our guide to the Outlook.com 5.7.1 error.
Mail you send through the MailRoute outbound relay already passes both checks DMARC needs:
include:spf.mailroute.net authorizes.mr01, mr02 and mr03 CNAME records point to. Publish all three, so we can rotate keys without your signatures ever breaking.For MailRoute senders, the DMARC record was the whole fix. Once it was in place, Outlook.com saw a domain that authenticates, and DMARC passed on either check. Our guide to publishing DMARC for the MailRoute outbound relay takes you from p=none to enforcement when you're ready.
The DMARC record was still the fix, but the service that sends your mail has to pass SPF or DKIM for your domain. Microsoft 365, for example, signs with its own onmicrosoft.com domain until you turn on DKIM for your own domain, and that signature doesn't count toward DMARC. Our sister company mxio has a guide to this error for any sender, with a checker that tests your domain from the page.
When we published this, we read the rejections as Microsoft quietly making DMARC a requirement for every sender, the way bulk-sender rules have tended to spread. Microsoft says it was a mistake in a spam rule update. Small senders have no new DMARC requirement.
The record is still worth publishing. Microsoft, Google and Yahoo all require DMARC of bulk senders, and spoofing is how much of today's phishing and business email compromise starts. The p=none record that got your mail delivered to Outlook.com is also the first step to p=reject, which tells receivers to refuse mail that forges your domain.
If you'd like a relay that signs your outbound mail correctly from day one, our setup documentation walks through SPF, DKIM and DMARC, and you can start a trial whenever you're ready.
Texto de mailroute.net tal como lo publicó, leído de su página y mostrado aquí con el formato de El Autómata. El original, en mailroute.net · Volver a la noticia de El Autómata