A validation error has stopped Outlook.com from accepting legitimate emails.
The problem appears widespread and, according to reports from affected users, can result in non-delivery reports with error codes related to SPF (Sender Policy Framework) validation failures.
Other users have reported errors highlighting a lack of DMARC (Domain-based Message Authentication, Reporting, and Conformance) information.
The troubles began at the end of last week and appear to be the result of Microsoft tightening the rules (or at least attempting to do so) for accepting emails. The company's consumer email services are affected, and it appears that if a domain doesn't have working SPF or if it has a missing DMARC record, then Outlook.com and its ilk will treat it as suspicious and not accept emails.
The rules are designed to deal with spam, bulk senders, and the like. In 2025, Microsoft announced new rules designed to strengthen email authentication for domains sending more than 5,000 emails per day. In addition to DMARC and SPF compliance, DKIM (DomainKeys Identified Mail) was also required.
Although this seemed like a good idea to ward off spammers, small senders now appear to be affected. According to complainants in the Outlook forum, a single email with just one line might now be rejected. Furthermore, Microsoft has not issued any advisory to customers explaining how the rules have changed.
Although some customers insist their DMARC, SPF, and DKIM settings are compliant, many more have reported that once they set them to Microsoft's preferences, email began flowing once more.
SPF must pass for the sending domain (the domain's DNS record should accurately list authorized IP addresses/hosts). DKIM must pass to validate email integrity and authenticity. DMARC must have at least p=none and align with either SPF or DKIM (preferably both).
asked the Windows giant for more information, but we have yet to receive a response.
To make matters worse, the glitch also appears to be intermittent. A resend attempt might succeed following a rejection. To compound the situation, the rejection error message may also be vague about what caused the bounce in the first place.
A moderator in Microsoft's support forum acknowledged the bug and said it was "classified as a service degradation."
"Microsoft is actively investigating the underlying cause of this email delivery issue, and engineering teams are actively analyzing service telemetry and customer-provided data to identify the source of the issue."
Still. It could be worse. Earlier today, several users in Europe, the Middle East, and Africa were affected by another Microsoft whoopsie – a "recent service change" that caused some connections to be abruptly terminated. Outlook on the web, as well as the Purview and Defender portals were all affected.
Microsoft reverted the change in the Exchange Online front-end infrastructure, and all was well.
It has yet to say what else, if anything, might have changed in its email services to cause legitimate messages to bounce back. ®