Microsoft requiring DMARC now or just us?
speckx
15 points
8 comments
November 07, 2026
Related Discussions
Found 5 related stories in 127.4ms across 12,324 title embeddings via pgvector HNSW
- DMARC has been public since 2012 but most company domains still don't enforce it adulion · 182 pts · July 28, 2026 · 59% similar
- Microsoft are rejecting your mail birdculture · 11 pts · November 10, 2026 · 58% similar
- Outlook.com is rejecting email from domains without DMARC xmddmx · 333 pts · November 08, 2026 · 57% similar
- PCI DSS DMARC Requirement: What Section 5.4.1 Requires meysamazad · 12 pts · July 24, 2026 · 55% similar
- How to set up SPF, DKIM, and DMARC for your sending domain spy888 · 75 pts · October 01, 2026 · 50% similar
Discussion Highlights (7 comments)
jared_stewart
No, this seems like a big thing that silently happened in the last 24 hours without announcement. Since roughly November 5, Outlook Hotmail, Live and MSN are rejecting some mail from domains without DMARC records. This includes low volume domains with passing SPF and DKIM results. The specific bounce we are seeing is "550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records". This is a different outcome from the high volume sender rule (5.7.515) which is part of why this looks like an unannounced extension. I haven't seen anything from Microsoft confirming any change. The current fix is minimal - just add a DMARC record of something like `v=DMARC1; p=none;` if a domain already has a record though, leave it alone.
simonklitj
Same for us, yes. Error messages started popping up November 5th.
proactivesvcs
There's some discussion of this on Mastodon, started by Mythic Beasts, who spotted it yesterday: https://social.mythic-beasts.com/@beasts/117569497236204746
Avamander
About time.
coolestguy
With how easy spam is now with AI, I welcome the change fully. I’m surprised anyone who reads/posts here wouldn’t have spf and dmarc set up already
soahc
There is another issue that we hit a few months ago which might be related/unrelated. But the total time for Microsoft to lookup your DKIM record and get an answer can't be longer than 500ms or your DKIM fails, their answer is to use faster DNS servers. You'd think 500ms is heaps of time, but if you it include the time to do the NS lookups to see what server to talk to, etc. We were having issue where sending to hotmail/msn from the same account to the same hotmail account would bounce 50% of the time.. It depended on which MS server accepted the incoming SMTP.
throwaway81523
I got a notification email about this from mxroute.com (email host) yesterday.