What does “550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level.” mean?
Outlook.com refused the message because your domain does not meet its sender requirements: SPF must pass, DKIM must pass, and DMARC must be at least p=none and aligned.
Last read from the sources at the foot of this page.
- Type
- TXT
- Name
_dmarc- Value
v=DMARC1; p=none; rua=mailto:[email protected]
What does it mean?
Microsoft set these requirements for domains that send more than 5,000 messages a day to Outlook.com, Hotmail and Live addresses. A message that does not meet them is refused with this code.
What exactly does the source say?
"550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level."
Why would a small firm see it?
A domain with no DMARC record, or a service sending in volume that is not in SPF or not signing with DKIM for your domain.
How do I fix it?
- Start herep=nonereports only
- p=quarantinesuspicious mail to spam
- Where to aimp=rejectforged mail refused
v=DMARC1; p=none; rua=mailto:[email protected]v=DMARC1; p=quarantine; rua=mailto:[email protected]v=DMARC1; p=reject; rua=mailto:[email protected]- Turn on DKIM signing for your domain at your mail provider, and at each other service that sends as your domain.Each one gives you a record to publish.
- Publish one TXT record named _dmarc with the p=none value shown here.Use a mailbox someone reads for the reports.
Keep one SPF record. Add the service inside the one record you have, before its last word, and keep every service already in it. A second SPF record makes the check fail for every message.
An SPF record may make at most 10 DNS lookups. Each include counts, and so do the includes inside it. Past 10 the check fails, so take out services you no longer use before adding a new one.
Use your own domain and a mailbox someone reads where the record shows yourfirm.example.
What else do the sources say?
we're announcing new requirements and best practices designed to strengthen email authentication for domains sending more than 5,000 emails per day.
At least p=none and align with either SPF or DKIM (preferably both).
If you exceed 10 DNS lookups, your SPF check might fail.
Where does this come from?
- Microsoft: Outlook's new requirements for high-volume senderstechcommunity.microsoft.comRead 14 October 2026
See what is open before anyone else does.
We read from outside, find each way in first, and show it with a check anyone can re-run. No access, nothing tested, no obligation.
- We read your firm from outside.
- You see what is open, with the proof for the lead finding.
- If it is worth it, you order.
What happens if you go ahead. More at getleaktrace.com/see-it-first/.
Read the transcript
- 72 hours. One domain. Nothing to install.
- Discover. Every way in, found from outside.
- Validate. Every finding, proven. Dated and checkable by anyone.
- Close. Forged email: one click per step, where we reach your DNS host and you approve it.
- You get the fix for the rest, step by step, and we re-check until it is closed.
- Monitor. On monitoring: email settings, look-alikes and new host names re-checked every hour. Alerts within the hour.
- Every paid assessment is human-verified before release.
- The AI defense layer for businesses. getleaktrace.com/see-it-first/