9 Nov 2026 · @Chris
Since 5 November, we’ve been seeing a growing number of reports that Microsoft’s free consumer mailboxes (Outlook.com, Hotmail, Live and MSN) are rejecting some email sent from domains that don’t publish a DMARC record. It hasn’t been 100% confirmed yet, but the pattern is consistent enough that we think it’s worth acting on now. At the time of writing (9 November), Microsoft hasn’t announced the change or given any advance warning. If your organisation emails donors, customers or volunteers who use those addresses, some of your messages may already be bouncing.
The immediate fix takes minutes. Fixing it properly takes a few weeks, and this is a good week to start.
What’s being reported
Email operators first reported the rejections on 6 November, and EasyDMARC reproduced the problem on 8 November using a domain with correctly configured SPF and DKIM but no DMARC record. The message to a Live.com address was refused with this bounce:
550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)
What the reports show so far:
- Who’s affected as a recipient: Microsoft’s consumer mailboxes (Outlook.com, Hotmail, Live, MSN). Business Microsoft 365 mailboxes on your own domain don’t appear to be affected.
- Who’s affected as a sender: any domain with no DMARC record, whatever its size. That includes many Microsoft 365 customers, because Microsoft 365 doesn’t create a DMARC record for you.
- It’s intermittent. Some messages get through and others bounce, so one successful test doesn’t mean you’re safe.
- It hasn’t been announced. As of 9 November, Microsoft hasn’t published anything about it, and its documentation doesn’t mention the AS9031519 code. Its published requirements, from May 2025, only applied to senders of more than 5,000 messages a day. This new behaviour appears to apply to everyone.
Some specialists caution that it isn’t yet confirmed as a deliberate policy. Even so, several email experts have reproduced it independently, so it’s sensible to plan as if it’s here to stay. Google, Yahoo and Microsoft have all been moving steadily in this direction since 2024.
Why charities should pay particular attention
Charities rely on email to reach supporters, and many donors and volunteers use personal Hotmail and Outlook addresses. A thank-you email, a Gift Aid confirmation or an event reminder that silently bounces is a real cost.
Our colleagues at Nebula Design measured the DNS records of 73,687 UK charity domains. Here’s where they sit on the DMARC “ladder”:
| DMARC position | Share of UK charity domains |
| No DMARC record at all | 55.7% |
| Monitoring only (p=none) | 31.5% |
| Quarantine (p=quarantine) | 7.6% |
| Reject (p=reject) | 5.1% |
That means more than half of UK charity domains are exactly the kind these reports say Microsoft is bouncing, and 87.2% publish no policy that actually stops someone forging their address. The full findings are in Can you trust email from the UK’s charities?
The same applies to small businesses. If the reports are right, this isn’t aimed only at bulk marketers: a five-person firm emailing a client at a Hotmail address can be caught by it.
Fixing the bounce isn’t the same as fixing the problem
The quick advice doing the rounds is to publish a basic DMARC record set to p=none. Senders who’ve done that report their mail flowing again, so it does stop the bounce.
But p=none simply tells receiving servers “I use DMARC, take no action if a message fails”. On its own it:
- Doesn’t stop anyone sending phishing emails as you. Only p=quarantine or p=reject does that.
- Tells you nothing unless it includes a reporting address, so you still won’t know which services send email as you, or who is impersonating you.
- Leaves you exposed to the next change. Every major mailbox provider is moving towards enforcement. A domain parked at p=none forever will hit the next wall too.
There’s also a common hidden gap: many organisations believe they have DKIM set up, but Microsoft 365 signs your email with its own onmicrosoft.com domain until you switch DKIM on for your own domain. That passes DKIM, but doesn’t count towards DMARC.
What to do this week
- Check whether you have a DMARC record. Your IT provider can tell you in minutes, or you can use any free online DMARC checker.
- If you don’t, publish one at p=none with a reporting address. Senders report this stops the Outlook and Hotmail bounces once it’s live, and starts telling you what’s happening to your email.
- Resend anything important that bounced. A 550 rejection is permanent, so Microsoft won’t retry it.
- Switch on DKIM for your own domain in Microsoft 365 or Google Workspace, and check your other sending services (newsletter tools, CRMs, donation platforms, helpdesks) are set up to send as you properly.
- Read the reports for a few weeks. They show every service sending email as your domain, and which ones fail.
- Move to enforcement. Once your legitimate email passes consistently, step up to p=quarantine and then p=reject. That’s the point where DMARC actually protects your name.
If you own domains you don’t send email from, they can go straight to p=reject, which stops them being used for impersonation.
How we can help
If you’re a Nebula client, we’re already checking your domains and will be in touch if anything needs attention.
If you’re not, and you’d like a quick answer to “are we affected?”, get in touch and we’ll check your email set-up for you, explain what we find in plain English, and help you get from a basic record to proper protection. Our free Cyber Resilience Self-Assessment is also a good place to see where else your organisation stands.
Sources
- Microsoft Is Now Rejecting Mail From Domains Without DMARC (EasyDMARC, via Security Boulevard, 9 November 2026)
- Can you trust email from the UK’s charities? (Nebula Design research, 73,687 domains, November 2026)
- Microsoft newly rejecting mail lacking DMARC? (Al Iverson, Spam Resource, 7 November 2026)
- Senders report Outlook.com email authentication bounces (Suped, November 2026)


