How To Fix Outlook.com Bounce Error 550 5.7.1 Message Lacks SPF/DKIM/DMARC Auth Records (2026)
Updated November 21, 2026: Since November 5, people on Microsoft’s Q&A forum have reported that emails sent to Outlook.com and Hotmail addresses bounced, and one thread posted November 6 shows more than 80 people with the same problem.
The bounce message reads 550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519), even for senders whose records look correct.
This guide explains what the error means, what Microsoft has said about it, and what to do whether you are the person receiving the mail or the person sending it.
Quick answer: what you see and what to do
| What you see | Likely cause | What to do |
|---|---|---|
| You are the recipient and expected mail never arrived | The sender’s message was rejected before it reached your mailbox | Ask the sender for the bounce message and ask them to resend |
| You are the sender and got the 550 5.7.1 bounce | A Microsoft spam-rule update wrongly rejected mail around November 5 to 9 | Send the message again now |
| The bounce keeps happening after November 9 | Your domain may truly lack a DMARC record or have a broken SPF or DKIM record | Check your three DNS records |
| The bounce says 550 5.7.515 | You send 5,000 or more messages a day to Microsoft consumer addresses | Follow Microsoft’s high-volume sender steps |
What users reported
The table below lists the dated reports behind this guide.
| Date | Source | What was reported |
|---|---|---|
| November 5, 2026 | Windows Latest testing | Failures seen from at least this date, with some reports earlier |
| November 6, 2026 | Microsoft Q&A thread | About half of senders bounced, and the thread was marked as 80+ same question |
| November 9, 2026 | Microsoft Q&A thread | A user reported only the code AS9031519 in a bounce |
| November 9, 2026 | Windows Latest | Mail flow reported restored at 12:02 CET |
| November 12, 2026 | Windows Latest | Microsoft said a spam-rule update caused the problem and was rolled back |
What the error means
The message was refused during delivery, so it never reached any folder in your mailbox.
SPF, DKIM and DMARC are three DNS-based checks that let a receiving server confirm an email really comes from the domain it claims.
The bounce said these records were missing, but many senders with valid records were bounced too.
Has Microsoft acknowledged it?
Yes, according to Windows Latest, which reported Microsoft’s statement that it resolved an issue that may have stopped some mail reaching Outlook.com, Hotmail and Live addresses.
Microsoft reportedly blamed an update to its spam rules, rolled it back, and referenced the item EX1545193.
The same report says senders did not need to change their SPF, DKIM or DMARC records, although I could not find that statement on a Microsoft page myself.
Step 1: check whether the mail was lost
For recipients: A rejected message is not hiding in Junk, so searching your folders will not find it.
- Open Outlook on the web at outlook.com and look in Inbox, Junk Email and Deleted Items for the missing message.
- If it is not there, assume it bounced.
- Ask the sender whether they received a delivery failure message.
Step 2: ask the sender to resend
The simplest fix: Since mail flow was restored on November 9, a fresh copy should now go through.
- Ask each sender who emailed you between November 5 and November 9 to send the message again.
- Ask for a copy of the bounce text if the resend fails.
- Keep the full error, including the code AS9031519 and the time, for support.
Step 3: if you send mail, check your DMARC record
Only if the bounce continues: Several forum users said adding a missing DMARC record let mail through, though Microsoft has not said this was needed.
- Sign in to wherever your domain’s DNS is managed.
- Look for a TXT record named _dmarc.
- If none exists, Microsoft’s own example for the value is v=DMARC1; p=none.
- Make sure there is only one DMARC record, because duplicates break the check.
Step 4: verify SPF and DKIM
What to confirm: Microsoft’s support page says a message should pass SPF or DKIM in a way that lines up with the visible From domain.
- SPF should be one TXT record that lists every service allowed to send for your domain.
- DKIM should sign outgoing mail with a key published under your domain.
- Open the message headers of a sent email and look for the pass or fail result of each check.
Step 5: check services that send for you
If a newsletter tool, web form or invoicing app sends mail in your name, it must sign with your domain.
Ask that service for its authentication setup guide and confirm your SPF record includes it.
The 550 5.7.515 variant
This is a different, documented error that applies to senders reaching 5,000 or more messages to Microsoft consumer addresses with the same From domain.
If your bounce shows this code, the steps in Microsoft’s article are the right ones to follow.
Mistakes to avoid
Warning: Do not edit working DNS records in a hurry, because a mistake there can stop all of your domain’s email.
- Adding your own email address to a safe senders list does not help, since the rejection happens before delivery.
- Do not delete an existing SPF record to add a new one, because a domain should have only one.
- Write down the old DNS values before you change anything.
When to contact Microsoft or your IT help desk
Contact support if bounces continue after November 9 even though your headers show SPF, DKIM and DMARC all passing.
Send the full bounce text, the time in UTC, the sending domain and the message headers, and ask your IT help desk to run a message trace if you use a work account.
Sources: Windows Latest report, Microsoft: fix NDR error 550 5.7.515, user threads 550 5.7.1 on Microsoft Q&A and incoming emails bouncing back.