Email

Outlook 550 5.7.1: Why Email Is Rejected and How to Fix It

November 12, 20268 min readBy David Collins

Getting an Outlook 550 5.7.1 email rejection? Before changing your DNS settings, find out whether the problem is SPF, DKIM, DMARC or Microsoft's mail filtering. Here's how to diagnose the error and fix the right thing.

You've sent an email, perhaps an invoice or a response to a customer, and a few moments later it comes straight back.

Instead of arriving in the recipient's inbox, you get a delivery failure that looks something like this:

550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)

If you've managed email systems for any length of time, you'll know the temptation: head straight into DNS, find the SPF record and start looking for something to change.

But hold on.

An Outlook 550 5.7.1 rejection doesn't automatically mean your email authentication is broken.

It might be an SPF, DKIM or DMARC configuration issue. Equally, the receiving server might be blocking your messages because of a security policy or a temporary filtering problem.

In November 2026, Microsoft experienced exactly that kind of filtering problem, causing legitimate emails to bounce even when their senders had working authentication.

The important thing is to find out what's actually wrong before making changes.

Here's how.

What does Outlook error 550 5.7.1 mean?

The first part of the error tells us that a receiving mail server has rejected the message.

The SMTP code 550 indicates a permanent delivery failure. The enhanced status code 5.7.1 generally points to a security, permission or policy restriction.

Unfortunately, that still leaves several possible causes.

An Outlook 550 5.7.1 error can be triggered by:

  • Email authentication failures involving SPF, DKIM or DMARC.
  • Recipient-side security policies or delivery restrictions.
  • A sending IP address or domain being blocked.
  • Problems with email routing or connector configuration.
  • Temporary problems with a receiving provider's filtering systems.

The code alone doesn't identify which one you're dealing with.

The full error message matters more than the first few numbers.

If the bounce mentions SPF, DKIM or DMARC, authentication is a sensible place to investigate. If it mentions a blocked IP address or a restricted recipient, that points you somewhere else entirely.

Microsoft also documents several different causes for Exchange Online 550 5.7.1 rejections.

The November 2026 Outlook email rejection incident

This is a useful example of why administrators shouldn't automatically trust an error message's suggested cause.

Between 6 and 9 November 2026, some senders experienced unexpected email rejections when contacting Outlook.com, Hotmail.com and Live.com recipients.

The error frequently referenced missing SPF, DKIM or DMARC authentication records.

For some organisations, that explanation didn't make sense. Their authentication settings hadn't changed, and the same systems had previously been sending email without difficulty.

Microsoft subsequently confirmed incident EX1545193.

The cause was a change to Microsoft's spam enforcement rules that incorrectly identified some legitimate messages as failing authentication.

The update was rolled back, and Microsoft reported that service had been restored on 9 November 2026 at 11:02 UTC.

Affected senders did not need to change their SPF, DKIM or DMARC records simply because of that incident.

The practical consequence was more frustrating: messages that had already been permanently rejected needed to be sent again.

Microsoft's support discussion about the incident confirms the rollback and advises contacting support if the issue continues.

What should you do if you still see this error?

First, check the date and exact wording of your rejection.

If it occurred during the November incident, the provider's filtering issue may explain it.

If you're receiving fresh errors, don't assume they're related to the resolved outage. Check your authentication, review the sending logs and investigate any current Microsoft service advisories.

A past incident is useful context, not a diagnosis for every future bounce.

Step 1: Read the complete bounce message

Before changing any DNS records, open the original non-delivery report (NDR).

Look for five things:

  1. The complete SMTP error: Not just 550 5.7.1, but everything following it.
  2. The receiving domain: Is it Outlook.com, Hotmail, Microsoft 365 or another service?
  3. The rejecting server: The diagnostic message may identify the server responsible.
  4. The time of the failure: This helps correlate errors with configuration changes or service incidents.
  5. The affected recipients: Does it happen with every destination or only one provider?

Imagine that mail is being delivered to Gmail and other providers, but messages to several Hotmail recipients suddenly start bouncing.

That doesn't prove Microsoft is at fault. But it gives you a good reason to investigate the Microsoft-specific rejection before modifying your sending domain.

Conversely, if messages are being rejected across several unrelated providers, an issue with your sending infrastructure becomes more likely.

If you administer Microsoft 365, the Exchange admin centre's message-tracing tools can help establish where delivery failed.

Save the complete bounce message. It could prove invaluable if you need to contact your email provider.

Step 2: Check for a known Microsoft service issue

This takes very little time and can save a lot of unnecessary work.

If you have access to a Microsoft 365 administrative account, navigate to:

Microsoft 365 Admin Centre → Health → Service health

Look for Exchange Online incidents or advisories relevant to the affected recipients.

You can also check Microsoft's support documentation and recent technical discussions for matching error codes.

Three things are particularly useful:

  • A confirmed incident affecting the same email service.
  • Multiple unrelated organisations reporting an identical error.
  • A provider acknowledgement that legitimate mail has been incorrectly blocked.

If a provider incident is confirmed, follow its guidance rather than making speculative DNS changes.

If no relevant incident exists, continue with authentication checks.

Step 3: Check your SPF record

SPF, or Sender Policy Framework, tells receiving mail servers which systems are authorised to send email for a domain.

A typical Microsoft 365-only SPF record might look like this:

v=spf1 include:spf.protection.outlook.com -all

This isn't a record you should automatically copy. Your domain may use several sending services, each requiring its own configuration.

For example, you might send messages through Microsoft 365, a helpdesk system and a marketing platform.

All legitimate sending sources need to be accounted for.

Check SPF using NetworkUtils

Open the free NetworkUtils SPF Checker and enter the domain you want to investigate.

The tool retrieves the published SPF record and checks its structure, including DNS lookup limits and potentially invalid mechanisms.

Pay particular attention to these problems.

No SPF record

Your sending domain doesn't publish an SPF policy that receivers can use.

Multiple SPF records

Two separate SPF records at the same DNS name can cause an SPF permanent error. They should be consolidated into one valid record.

Missing sending services

A new email platform may not be authorised by your existing SPF policy.

Too many DNS lookups

SPF permits a maximum of 10 DNS-query-triggering mechanisms and modifiers during an evaluation. Exceeding the limit produces PermError.

You can also retrieve TXT records manually.

On Windows PowerShell:

Resolve-DnsName example.com -Type TXT

On Linux or macOS:

dig +short TXT example.com

Replace example.com with the domain you're checking.

One detail catches people out: SPF normally checks the envelope-sender domain, not necessarily the visible address in the From field.

If your email platform uses a third-party return-path domain, make sure you're investigating the correct domain.

And remember, finding a valid SPF record doesn't prove that a particular email passed SPF. It only tells you that the published configuration appears valid.

Step 4: Check whether DKIM is configured correctly

DKIM, or DomainKeys Identified Mail, provides cryptographic verification that a message was signed by a system authorised to use a particular domain.

The sending system signs the message with a private key. The recipient retrieves the corresponding public key from DNS to verify the signature.

A DKIM key is located using a selector.

For example:

selector1._domainkey.example.com

The exact selector depends on your email provider.

Check DKIM using NetworkUtils

Open the NetworkUtils DKIM Checker.

You can enter a domain to probe common selectors, or specify a selector directly:

selector1:example.com

The tool can retrieve the published DKIM key and identify issues with its format or availability.

If the record is missing, check which selector your sending platform actually uses.

Don't assume that a missing result for selector1 means DKIM is broken. Your provider could be using s1, google or another selector entirely.

If you're using Microsoft 365, check that DKIM signing is enabled for the relevant custom domain and that the provider's required DNS records are published.

There's another important distinction here.

The NetworkUtils checker verifies a published DKIM public key. It doesn't inspect an actual outgoing message or verify that message's signature.

You'll need message headers or sending-platform logs for that.

Step 5: Check your DMARC record and domain alignment

This is where email authentication becomes a little more interesting.

DMARC builds on SPF and DKIM, but it doesn't simply check whether those mechanisms exist.

It checks whether authentication succeeds and whether an authenticated domain aligns with the domain your recipient sees in the From address.

Let's say your business sends an email from:

accounts@example.com

The message goes through a third-party platform using its own sending domain.

SPF passes for that platform.

DKIM also passes using the platform's signing domain.

But neither authenticated domain aligns with example.com.

The message can therefore fail DMARC even though both individual authentication checks passed.

That's a common source of confusion.

Check DMARC using NetworkUtils

Visit the NetworkUtils DMARC Checker.

Enter your domain and review the published policy, alignment configuration and reporting addresses.

A basic monitoring record looks like this:

v=DMARC1; p=none

It is published as a TXT record at:

_dmarc.example.com

A monitoring policy that also requests aggregate reports might look like this:

v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com

Key takeaways

  • Outlook 550 5.7.1 can indicate authentication failures, recipient security policies or provider-side filtering issues.
  • Microsoft's November 2026 incident caused legitimate email rejections and was resolved on 9 November.
  • Verify SPF, DKIM and DMARC records before making changes to your sending configuration.
  • DMARC requires successful authentication and domain alignment; passing SPF alone may not be enough.
  • Use NetworkUtils email diagnostic tools to investigate your DNS records, then confirm actual authentication results from message headers.
  • Always resend and verify delivery of messages that were permanently rejected.

FAQ

FAQ 1 — What does Outlook error 550 5.7.1 mean?

It means the receiving mail server rejected your message because of a security, permission or policy-related restriction. Possible causes include SPF, DKIM or DMARC failures, recipient-side restrictions and sender blocking. The complete bounce message is needed to identify the specific cause.

FAQ 2 — Will adding a DMARC record fix Outlook 550 5.7.1?

Not necessarily. A missing DMARC record may contribute to delivery failures, especially where authentication requirements apply. However, publishing a DMARC policy doesn't automatically fix SPF or DKIM problems or resolve provider-side filtering issues. Check the actual authentication results before changing your configuration.

FAQ 3 — Why does DMARC fail when SPF passes?

SPF can pass for the envelope-sender domain while that domain doesn't align with the address shown in the visible From field. DMARC requires at least one aligned authentication method to pass: SPF or DKIM. Correcting domain alignment can resolve the failure.

FAQ 4 — Why does email work with Gmail but fail with Outlook?

Different providers use different filtering policies, reputation checks and authentication requirements. Successful delivery to Gmail doesn't guarantee acceptance by Outlook. Compare the full rejection message, sender logs and authentication results to establish why Microsoft rejected the message.

FAQ 5 — Was the November 2026 Microsoft Outlook email rejection issue resolved?

Yes. Microsoft confirmed that an update to its spam enforcement rules incorrectly blocked some legitimate email sent to Outlook.com, Hotmail.com and Live.com. The update was rolled back and service was restored on 9 November 2026. Permanently rejected messages may need to be resent. Microsoft Q&A

outlook 550 5.7.1email authenticationSPFDKIMDMARCemail deliverabilityMicrosoft 365

Reviews & Recommendations

Community feedback on this article. All submissions are moderated before publication.

Loading feedback…

Related articles

Continue reading with these guides from the networkutils.org blog.

Try the related tools

Put the concepts in this guide into practice with these live diagnostic tools.