Outlook and Microsoft

Why Is Outlook Blocking or Junking My Cold Emails?

Outreach2dayPublished 2 min read
On this page

Short answer

Outlook junks or rejects cold email for three main reasons: authentication that fails Microsoft's rules (bounce 550 5.7.515), a sending IP on Microsoft's blocklist (5.7.1, 5.7.511 or 5.7.606 to 649), or content and volume its filters distrust. Read the bounce code first. Fix SPF, DKIM and DMARC, request delisting if the IP is banned, then test the copy against a neutral email.

What changed in May 2025

On April 2, 2025 Microsoft announced new requirements for high-volume senders to Outlook.com, its consumer service for hotmail.com, live.com and outlook.com addresses. They cover domains that send more than 5,000 emails a day:

  • SPF must pass for the sending domain.

  • DKIM must pass.

  • DMARC must be at least p=none and align with SPF or DKIM, preferably both.

Enforcement started on May 5, 2025. Microsoft's post first said non-compliant mail would go to Junk; its April 29 update says such messages are rejected with 550; 5.7.515 Access denied, sending domain [SendingDomain] does not meet the required authentication level. The post also recommends valid From: and Reply-To: addresses, a working unsubscribe link, list hygiene and bounce management.

If you see 5.7.515, the fix is DNS, not copy: see SPF, DKIM and DMARC for cold email.

Read the bounce code

Business recipients on Microsoft 365 return Exchange Online codes, and Outlook.com uses 5.7.515 for failed authentication. The most common ones for cold senders:

Code

What Microsoft says it means

What to do

550 5.7.515

Sending domain does not meet the required authentication level

Fix SPF, DKIM, DMARC and alignment

5.7.1 "Client host ... blocked using Blocklist 1"

The source IP is on Microsoft's blocklist

Forward the bounce to delist@microsoft.com or use the delist portal

5.7.511

"Access denied, banned sender"

Email delist@microsoft.com with the full bounce and the IP

5.7.606 to 5.7.649

"Access denied, banned sending IP"

Check IP reputation, then use the delist portal

5.7.23

Rejected because of an SPF violation

Fix the SPF record

Other 5.7.1 variants ("Delivery not authorized", "Unable to relay") are recipient-side settings. Microsoft notes that "Typically, you can't fix the problem yourself." See 550 5.7.1 by provider.

When there is no bounce

Outlook often fails quietly: the message lands in Junk, or never shows up in either folder. Check the text of the email and your recent volume changes, not only DNS: a sudden jump in volume and mass-mail wording are common reasons for Junk placement and throttling.

Check:

  1. Copy. Send a neutral, non-sales email and your campaign email from the same mailbox to Outlook seed inboxes in the same minute. If the neutral one lands and the campaign one doesn't, rewrite the offer into a genuinely different text. Financial and lending offers are the most sensitive.

  2. Volume. Temporary errors such as 4.7.500-699 "Access denied, please try again later" mean Microsoft has temporarily restricted your sending. Slow down, and don't raise total volume while they appear.

  3. Domain. With finance and lending copy, .info domains did 3.5× worse on Outlook than .co domains in our tests; with neutral copy we saw no difference. See .info vs .com.

  4. Separate campaigns. Put Outlook and Google recipients in separate campaigns so you can measure each on its own. A blended inbox rate hides a problem on one side.

What we recommend at Outreach2day

Keep to up to 25 cold emails per mailbox a day, not counting warm-up, and up to 5 mailboxes per domain. Keep warm-up running while you send. We don't guarantee inbox placement on Outlook or Gmail, so test placement on both before you scale.

Sources

See deliverability issues before they kill performance

Monitor mailbox health in real time, spot degradation early, and keep warmup, protection, and sending in one place.