my hotmail email account respond with error 550 5.7.1 to incoming mails, what can I do?

Question

my hotmail email account respond with error 550 5.7.1 to incoming mails, what can I do?

MARX73 0

My hotmail email account cannot receive mails i respond to error 550 5.7.1 to everyone, what can I do?

0 comments

2 answers

Your answer

Answer 1

The sender’s email administrator or provider must correct its SPF, DKIM, and DMARC authentication; there is no SPF/DKIM/DMARC setting to change on your personal Hotmail mailbox.

The rejection from eur.olc.protection.outlook.com occurs before the message reaches your mailbox. Microsoft’s guidance requires the sending domain to publish valid SPF, DKIM, and DMARC records and properly align the authenticated domain with the address shown in the message’s From field.[^1^](https://support.microsoft.com/en-us/outlook/fix-ndr-error-550-5-7-515-in-outlook-com "Fix NDR error "550 5.7.515" in Outlook.com | Microsoft Support")

What to do

Send the complete bounce message to each affected sender by another method.
- Ask the sender to forward it to their email administrator or email provider.
- Include this relevant text:
  
  550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)
Ask the sender’s administrator to verify:
- SPF authorizes the server or service that sent the message.
- The message has a valid DKIM signature.
- The sending domain publishes a valid DMARC record.
- SPF or DKIM aligns with the domain in the visible From address.
- Any third-party bulk-mail, website, CRM, forwarding, or security service is configured to authenticate using the sender’s domain.
Microsoft provides the detailed checks in its Outlook.com NDR remediation instructions.[^2^](https://support.microsoft.com/outlook/fix-ndr-error-550-5-7-515-in-outlook-com#how-do-i-fix-this "Fix NDR error "550 5.7.515" in Outlook.com | Microsoft Support")
For urgent messages, ask the sender to use an address with a different, correctly authenticated provider until their administrator fixes the domain.

Adding the sender to Safe senders, changing inbox rules, or checking Junk Email will not normally resolve this rejection because the message is refused at Microsoft’s inbound server before mailbox processing. Personal @hotmail.* and @outlook.com users also cannot create authentication records for Microsoft’s domain; Microsoft manages those records.^3^

If unrelated senders are all rejected

Because you report that this affects everyone, collect complete bounce reports from at least two or three unrelated email providers. If they all show AS9031519, contact Outlook.com Support while signed in:

Open Outlook.com.
Select Help on the menu bar.
Enter the receiving problem.
Scroll to Still need help?
Select Yes and provide the complete bounce reports, timestamps, and server response—after removing email addresses and other personal information.^4^

The sending administrator can also use Microsoft’s Outlook.com sender-support guidance if their authentication is correct but delivery remains rejected.^5^

References

Answer 2

Hello

I am seeing a sudden increase in similar reports from other users in this forum as well.

Unfortunately, I cannot find any official information from Microsoft acknowledging this issue. Microsoft's published requirements for SPF, DKIM, and DMARC apply to senders sending more than 5,000 emails per day. However, based on the sudden increase in reports from the last few days, I suspect these requirements may now be affecting low-volume senders as well. This is just my observation, not something Microsoft has officially confirmed.

I helped several users with this issue the last few days in this forum. One interesting thing we noticed is that email headers may show DMARC as passing, even when the sending domain does not have a published DMARC record. We were able to identify this by checking the domain using a free tool such as https://mxtoolbox.com/.

In some cases, once the missing DMARC record was properly configured and verified, emails started coming through again.

For this reason, I strongly recommend having your senders check their SPF, DKIM, and DMARC records for the affected sending domains. This is not an issue you can fix on your end. It has to be addressed on the sender's end.

If you need help checking these records, I am happy to do so. I would just need to know the sending domain name. You do not need to share the full email address.

Also, news article about this issue: https://www.neowin.net/news/microsoft-outlook-spf-validation-error-blocks-email-sending-and-receiving/

Note: This is a non-Microsoft website. The page appears to be providing accurate, safe information. Watch out for ads on the site that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the site before you decide to download and install it.