All articles

NewsNovember 9, 20265 min read

Outlook.com rejects legitimate email without DMARC: spam rule bug

From 5 November Outlook.com, Hotmail and Live rejected legitimate email over SPF, DKIM or DMARC: cause, error codes and what to check on your domains.

Metallic icon with an envelope, a padlock and the word Security

For several days starting on 5 November 2026, Microsoft’s consumer mailboxes (Outlook.com, Hotmail, Live and MSN) rejected legitimate email sent from domains without a DMARC record or failing an SPF check. The problem mostly hit small, ordinary senders, not the bulk senders targeted by the authentication rules Microsoft introduced in 2025. Between 10 and 11 November Microsoft acknowledged the error, blamed it on an update to its own spam rules and declared mail flow restored.

What happened

According to The Register and CSO Online, from the end of last week many users reported non-delivery reports (NDRs) on Microsoft’s forum for perfectly normal messages, even single-line ones. The errors cited a failed SPF check or missing DMARC information. CSO Online reports the codes 550 5.7.1 and 550 5.7.23 and a text along the lines of «hotmail.com couldn’t confirm that your message was sent from a trusted location».

Three factors made the problem hard to diagnose:

  • it was intermittent: from the same sender some messages went through and others did not, and resending after a rejection could succeed;
  • the error message was vague and, according to analyst Frank Dickson (Dickson Research) quoted by CSO Online, pointed to the wrong cause;
  • even correctly configured domains were rejected: both outlets report this, based on user reports.

Microsoft had not announced any policy change: CSO Online stresses that there was no postmaster notice, service health entry or blog post. A moderator on the support forum classified the case as a «service degradation» under investigation.

The cause, according to Microsoft

In incident report EX1545193, quoted by The Register, Microsoft writes that a recent update to its spam enforcement rules caused messages to be incorrectly marked and blocked, and that it will review its update procedures. A spokesperson then confirmed to both outlets that the issue is resolved and that delivery to Outlook.com, Hotmail and Live has been restored, pointing to EX1545193 in the Microsoft 365 admin center. According to CSO Online, Microsoft said users do not need to change any settings.

On the same day, 9 November, and reported only by The Register, a separate incident hit users in Europe, the Middle East and Africa: a change to the Exchange Online front-end infrastructure terminated connections to Outlook on the web and to the Purview and Defender portals. Microsoft rolled it back.

Technical background

Since May 2025 Microsoft has required domains sending more than 5,000 messages a day to consumer mailboxes to have:

  • SPF passing for the sending domain, with the DNS record correctly listing authorised IPs and hosts;
  • DKIM passing, to guarantee message integrity and origin;
  • DMARC published with at least p=none and aligned with SPF or DKIM (preferably both).

Google and Yahoo have asked the same of bulk senders since February 2024. DMARC ties the SPF and DKIM checks to the domain the recipient sees in the «From» field and tells receiving servers what to do with messages that fail: it is the main defence against domain spoofing used in phishing and business email compromise fraud.

The bug effectively applied those requirements to everyone. According to Dickson, both a bug and a policy change may be at play, and the direction is clear anyway: DMARC will become a requirement for every sender.

Impact for European and Italian companies

Those left without DMARC are often those who assumed the rule did not apply to them: small businesses, professional practices, schools, associations, clinics, with domains set up years ago and never touched again. In larger companies the records are often missing on secondary domains, regional domains and the subdomains used by CRM, billing and marketing platforms.

The damage is silent: the sender sees a bounce full of acronyms and ignores it, the recipient never knows the message existed. Invoices, password resets, appointment confirmations and patient communications to Hotmail or Outlook.com addresses may have been lost between 5 and 10 November. For healthcare organisations and NIS2 entities, which must ensure continuity of communications with customers and users, it is worth checking what did not arrive. And a domain without DMARC remains easy to impersonate, regardless of this incident.

What to do now

  1. Look for bounces since 5 November in mail server logs, sending platform reports and help desk tickets: codes 550 5.7.1 and 550 5.7.23 and texts such as «Message lacks SPF/DKIM/DMARC».
  2. Resend important messages, starting with time-sensitive transactional ones.
  3. Check whether your domain has DMARC: dig +short TXT _dmarc.yourdomain.com. A reply starting with v=DMARC1 means the record exists; no reply means it is missing.
  4. If it is missing, publish it: the minimum is v=DMARC1; p=none, with a rua address to receive aggregate reports. It only works if SPF or DKIM is aligned with the «From» domain.
  5. Enable DKIM on custom domains in Microsoft 365, if you never have.
  6. Do not rewrite SPF just because the bounce mentions it, Dickson advises: if your records are correct and messages are still rejected, send the full bounce to Microsoft.
  7. Take an inventory of every service that sends on behalf of your domains (CRM, billing, HR, marketing) and move step by step towards p=quarantine and p=reject: p=none is only the first step.

How ARXDOME helps

ARX Expose checks every day, using passive sources, the domains your company has declared, including mail configuration (SPF and DMARC), and reports findings with the actions to take. The portal also reads the DMARC reports for your domains: it shows who sends in your name and how much, day by day, and helps you build the inventory of senders before moving to a stricter policy.

Last updated:

Any questions?

Let’s talk about your company’s needs, with no obligation.

Contact us

Related articles