Shadow Inbox/blog
Subscribe
← back to indexblog / cold email / outlook-cold-email-rejected
● Cold Email

Outlook 550 5.7.515: why your cold email is rejected and how to fix it

Outlook's 550 5.7.515 means your sending domain failed SPF, DKIM or DMARC. The 5,000-a-day rule counts the domain, not you. The fix is DNS.

A
ArthurFounder, Shadow Inbox
publishedSep 17, 2026
updatedOct 30, 2026
read6 min
Outlook 550 5.7.515: why your cold email is rejected and how to fix it

You sent eighteen emails this morning, each one referencing something a specific person had posted. Four bounced with the same line: 550 5.7.515 Access denied, sending domain doesn't meet the required authentication level. You have never se

You sent eighteen emails this morning, each one referencing something a specific person had posted. Four bounced with the same line: 550 5.7.515 Access denied, sending domain doesn't meet the required authentication level. You have never sent more than forty emails in a day. So why is Outlook treating you like a bulk sender?

Here is the short answer. The code means Outlook.com refused the message because your sending domain failed one of three checks: SPF did not pass, DKIM did not pass, or there is no DMARC record of at least p=none aligned with one of them. Microsoft's policy applies to domains sending more than 5,000 emails a day to Outlook.com, Hotmail and Live addresses, and that count belongs to the domain, not to you. Fix the three DNS records and the rejection stops.

The 5,000 a day belongs to the domain, not to you

Microsoft announced the requirements on 2 April 2025 for "domains sending more than 5,000 emails per day." The first plan was to route failing mail to Junk. An update on 29 April changed that: from 5 May 2025, failing messages are rejected with 550 5.7.515. Microsoft says it applies to Outlook.com, its consumer service, which covers hotmail.com, live.com and outlook.com addresses. Business mailboxes on Microsoft 365 are not named in the policy.

5,000/dayPer-domain threshold in Microsoft's high-volume sender policy
5 May 2025Outlook.com began rejecting, not junking, non-compliant mail
p=noneMinimum DMARC policy, aligned with SPF or DKIM
10DNS lookups an SPF record can make before the check fails, per Microsoft's FAQ

The requirements are short. SPF must pass for the sending domain. DKIM must pass. DMARC must exist, at least at p=none, and align with SPF or DKIM, preferably both. Microsoft also lists hygiene it expects from large senders: a From or Reply-To address that can receive replies, a working unsubscribe link, regular removal of bad addresses, and accurate subject lines.

The policy names a volume. The check itself only asks whether your domain can prove the mail came from you.

The forum case shows DMARC passing is not enough

A thread on Microsoft's support forum from June 2025 is useful precisely because the sender is so ordinary. They wrote that they used their address for personal mail only and were not a high-volume sender. Their messages to Hotmail addresses bounced with 550 5.7.515. The rejection reported SPF pass, DMARC pass and DKIM fail, and Microsoft's support reply put the cause on DKIM for the sending domain.

Two lessons come out of it. First, the address was on an internet provider's shared domain, so whatever volume Microsoft counted was the whole domain's, and the fix sat with the provider, not the user. If you send outbound from an address on someone else's domain, you inherit both their volume and their DNS. Second, DMARC passed and the mail was still refused. Microsoft wants SPF and DKIM to pass on their own, not just one of them through DMARC alignment.

Four things break the check on a small domain

No DMARC record. Plenty of domains registered years ago never published one. A missing record fails the requirement exactly like a broken one.

DKIM signed by the wrong domain. Many sending tools sign with their own DKIM key on their own domain until you set up yours. The signature passes, but it does not match your From: address, so it does not count for alignment. Microsoft's FAQ is explicit that outsourcing sending does not move authentication off your domain.

SPF over its lookup limit. Every include: in your SPF record costs DNS lookups. Microsoft's FAQ notes that more than 10 lookups can make SPF fail, which is easy to hit once a workspace, a CRM, a support desk and a sending tool all send as you.

Forwarding. A message that passes through a forwarding rule or mailing list can lose DMARC alignment on the way. Microsoft's FAQ recommends ARC for forwarders, which preserves the original authentication results. That is the forwarder's setting to change, not yours, but it explains bounces that only happen on one route.

DMARC.org's overview is worth reading once if alignment is new to you. SPF and DKIM can each pass and still fail DMARC if the domain they check is not the one in your visible From: address.

Gmail has asked every sender for this since 2024

Outlook is not the first. Google's sender guidelines have required every sender to Gmail to set up SPF or DKIM since 1 February 2024, at any volume. Senders of more than 5,000 messages a day to Gmail need SPF, DKIM and a DMARC record, which can be p=none, aligned with the From: domain. A domain that meets Microsoft's three requirements meets Google's too. Low volume was never an exemption from authentication. It only made the gap quieter.

The fix is a DNS afternoon, not a subscription

None of this needs a warmup tool or a deliverability platform.

  1. List every service that sends as your domain: workspace mail, your sequencing tool, CRM, billing, support desk. Make sure the SPF record covers each one and stays under 10 lookups.
  2. Turn on DKIM signing with your own domain in each of those services, not the vendor's default.
  3. Publish a DMARC record if you have none, starting at v=DMARC1; p=none; with your own address in the rua= tag so you receive the aggregate reports Microsoft sends.
  4. Move toward p=quarantine once the reports show your legitimate mail passing.
# check what is published today
dig +short TXT yourdomain.com | grep -i spf
dig +short TXT _dmarc.yourdomain.com

Then send a test to an Outlook.com address, open the message headers, and confirm spf=pass, dkim=pass and dmarc=pass, with the passing domain matching your From: address. If your email channel is down while DNS propagates, move the conversation to another channel rather than pausing it. A message built on a specific trigger works by LinkedIn DM too.

● FAQ

What does 550 5.7.515 mean?
Outlook.com refused the message because the sending domain did not meet its authentication requirements: SPF must pass, DKIM must pass, and the domain must publish a DMARC record of at least p=none that aligns with SPF or DKIM. Microsoft has rejected non-compliant mail with this code since 5 May 2025. The message is not junked. It is refused.
Does Outlook's 550 5.7.515 error only hit high-volume senders?
Microsoft's policy covers domains sending more than 5,000 emails a day to Outlook.com, Hotmail and Live addresses. The count is per domain, not per person, so a low-volume user on a busy shared domain can be rejected for the domain's setup. Microsoft has not said whether it applies the check to smaller domains. The fix is the same either way.
What's the minimum DMARC setup Outlook will accept?
A DMARC record at p=none that aligns with either SPF or DKIM, preferably both. DMARC passing is not enough on its own: Microsoft also requires SPF and DKIM to pass individually. In one case on Microsoft's own support forum, SPF and DMARC passed, DKIM failed, and the message was still rejected.
How do I check whether my domain passes right now?
Send a test email to an Outlook.com or Gmail address, open the message headers, and look for spf=pass, dkim=pass and dmarc=pass, with the passing domain matching your From: address. Any of the three showing fail or none is the one to fix first.
Will Outlook enforce this on every sender eventually?
Microsoft has not said. Its FAQ on the policy says enforcement first targets large senders and that all senders benefit from the same setup. The word first leaves the door open. Fixing your records costs an afternoon, so there is little reason to wait and find out.
Does Shadow Inbox fix email deliverability?
No. Shadow Inbox finds the public posts that give an email a reason to exist. It has nothing to do with your DNS records, and the fix in this post is yours to run.
— share
— keep reading

Three more from the log.

Cold Email in Canada: What CASL Requires for B2B
001 · Cold Email

Cold Email in Canada: What CASL Requires for B2B

CASL has no blanket B2B carve-out. What cold email to Canadian prospects needs: the three-part implied-consent test, a 10-day unsubscribe, and a $10M ceiling.

Oct 27, 2026 · 7 min