On November 7, 2026, reports surfaced regarding Sender Policy Framework (SPF) validation errors blocking Outlook email deliveries, even when senders verified that their Domain Name System (DNS) records were correct. According to Microsoft Q&A threads, the resulting email bounces primarily affect messages sent to Outlook.com and Hotmail addresses. These rejected messages often return with the specific SMTP code “550 5.7.23” and sometimes include additional “550 5.7.1” text, as reported by affected senders and Microsoft 365 administrators.
Understanding Outlook SPF Validation Errors
Reports detailing these intermittent rejections describe varying scenarios involving both outgoing mail and incoming mail. Microsoft Q&A threads confirm that cases are heavily tied to Microsoft 365 domains, while additional reports mention Google Workspace and Zoho, although those external reports have not been independently verified. Many affected senders noted that their SPF, DKIM, and DMARC records appeared entirely valid upon initial inspection.
Despite widespread community discussion and troubleshooting efforts across user forums, Microsoft has not publicly confirmed a service-wide defect as of this writing. The available evidence consists primarily of community reports, a Neowin write-up, and a handful of anecdotal fixes. This data does not establish a verified service-wide event, its scale or geographic regions, or any underlying change to how Outlook.com evaluates SPF records. Suggestions that Microsoft altered an enforcement rule remain speculation from Q&A participants rather than confirmed findings.
Furthermore, personal Outlook.com users cannot edit Outlook.com’s SPF, DKIM, or DMARC records, nor can they edit the sender’s individual records. For small businesses operating on custom domains, any necessary DNS changes must be handled by whoever manages the domain DNS—whether that is the owner, a registrar, a hosting company, or a managed service provider (MSP). Crucially, the domain that matters in these evaluations is the envelope-sender (Return-Path) domain shown in the non-delivery report (NDR), which does not always match the visible From address.
Decoding the Bounce Notice (NDR) and Error Codes
If an email message bounces, saving the full non-delivery report (NDR) first is vital. Its diagnostic text identifies which domain and which validation check failed. Although 550 5.7.23 and 550 5.7.1 are both SMTP rejection codes, they do not mean the same thing:
- 550 5.7.23: Specifically identifies an SPF validation failure. The recipient system checked the sender’s SPF record and rejected the message before final delivery.
- 550 5.7.1: Represents a broader policy rejection that can point to missing SPF, DKIM, or DMARC authentication, or another policy violation.
Because the exact diagnostic text in the NDR determines which check actually failed, administrators should never assume both codes mean “SPF failed.” Safe Senders lists and junk-mail settings will not resolve these blocks because Microsoft Q&A guidance notes that those settings only apply after a message is successfully accepted. An SMTP rejection occurs prior to that point.
Evaluating Common Causes and Community Theories
Microsoft’s official SPF setup documentation outlines several common, self-inflicted causes that lead to validation errors:
- Maintaining more than one
v=spf1TXT record on the same domain. - Omitting the required
include:spf.protection.outlook.comentry for Microsoft 365 custom domains. - Configuring an SPF record that requires more than 10 DNS lookups, causing a permanent failure.
- Failing to implement or properly align DKIM or DMARC records.
While missing or misaligned DKIM or DMARC records do not cause a valid SPF record to fail on their own, stricter enforcement settings can trigger rejections. For example, if DMARC enforcement is set to p=reject or p=quarantine and a message fails DMARC alignment, Microsoft’s mail servers can reject it even when SPF itself passes.
Additionally, community posts on social media platforms like X—summarized from data sources such as @NeowinFeed and @windowsforum—suggest that Microsoft may be rejecting mail from domains completely lacking a DMARC record. The most common community advice involves adding a basic DMARC TXT record set to p=none. While one public post shared a case where adding a missing DMARC record fixed Outlook delivery immediately, this theory remains unconfirmed by Microsoft and is supported only by anecdotal success stories.
Step-by-Step Troubleshooting for Domain Administrators
Domain administrators investigating outbound delivery issues to Outlook and Hotmail addresses should work through a structured diagnostic workflow:
- Save the complete NDR: Preserve the entire non-delivery report, including the full “Diagnostic information for administrators” section, which details the envelope-sender domain, timestamp, sending IP, and exact SMTP error text.
- Identify the envelope-sender domain: Determine the exact Return-Path domain and sending IP evaluated by the recipient system.
- Audit DNS records: Run an
nslookup -type=txtquery against that domain to confirm there is exactly one validv=spf1record. Ensure the sending IP or service is included and keep total DNS lookups under 10. - Trace outbound messages: If troubleshooting a Microsoft 365 tenant, open the Exchange admin center, navigate to Mail flow, and use Message trace to search by sender, recipient, and date. Note that message trace shows tenant processing but may not display the recipient system’s full authentication failure reason.
- Allow for TTL expiration: After making any DNS updates, wait for the old record’s Time-To-Live (TTL) to expire before testing delivery to an Outlook.com address.
Public SPF checkers may not accurately replicate a recipient system’s evaluation because results depend on the envelope-sender domain, sending IP, DNS responses, and any intervening message forwarding. However, if an NDR shows SPF failing for a domain and IP clearly authorized by your records, that documentation provides a solid foundation for a support escalation. If clean records do not resolve intermittent bounces, treat the issue as a potential Microsoft-side concern and escalate with your NDR and trace results.


































