I cannot stop Outlook blocking emails, as the help steps do not exist

This message is being rejected by Microsoft’s mail servers before it reaches Classic Outlook, so changing Outlook’s blocked-sender or Mail settings will not resolve it.

The wording “couldn't confirm that your message was sent from a trusted location” together with “SPF Validation error” matches the November 2026 delivery issue affecting messages sent to Outlook.com, Hotmail.com, and Live.com addresses. Microsoft identified it as an Exchange service degradation involving 550 5.7.1 and 550 5.7.23 failures.^1^

What to do now

1. Open the complete failure notice, normally found in the sender’s Inbox, and locate:
   • Status code
   • Error
   • Original Message Details
   • Message rejected by
2. If it contains 550 5.7.23, 550 5.7.1, or “SPF validation error”:
   • If you are receiving the mail, send the complete failure notice to the sender. The sender or their email provider must investigate it.
   • If you sent the mail from a personal/ISP address, contact that email provider and give them the complete notice.
   • If you administer the sending domain, validate its SPF, DKIM, and DMARC records as described below.
3. Retest with a new message. Resending may work intermittently during the reported service degradation, but that does not establish that the underlying authentication configuration is correct.

If you manage the sending domain

Check the Authentication-Results section of the failed message and address the reported result:

• spf=none: no SPF TXT record was found.
• spf=permerror: there may be multiple SPF records or more than ten DNS lookups.
• spf=softfail or spf=fail: the actual sending server/IP is not authorized by SPF.
• dkim=none or dkim=fail: DKIM signing is absent or invalid.
• dmarc=fail: SPF or DKIM does not align with the domain shown in the message’s From address.

Microsoft documents that only one SPF TXT record is permitted for each domain or subdomain. Services such as website mailers, CRM systems, forwarding services, and marketing platforms must also be authorized correctly; SPF alone may not be sufficient without DKIM and DMARC.^2^

Do not create or replace DNS records unless you administer the domain. An incorrect SPF replacement can disrupt mail from other authorized services.

Escalation for the November 2026 incident

If SPF, DKIM, and DMARC already pass but Microsoft consumer addresses still reject messages intermittently:

• Submit a report through Microsoft’s Sender Support form: https://go.microsoft.com/fwlink/?LinkID=614866
• Include a recent full non-delivery report, the Network Message ID, timestamp, sending domain, recipient domain, and an affected message saved as .eml.
• For Microsoft 365 business mail, the tenant administrator should open a Microsoft 365 support request. If the subscription came from a reseller, contact that reseller.

The missing Mail or Home options are therefore not the blocker: those help instructions concern Outlook client settings, while this rejection occurs at the mail-server authentication stage.

References

1. SPF Validation Error - Microsoft Q&A
2. Troubleshoot email authentication in Microsoft 365