Critical ErrorSMTP Error · Permanent (5.x.x)
550 5.7.606

Access denied, banned sending IP (Office 365)

A 550 5.7.606 from Microsoft 365 means your sending IP is on Microsoft's block list — Exchange Online Protection is refusing all mail from that address until it's delisted.

Updated June 13, 2026

SMTP Exchange / Mail Log
> MAIL FROM:<you@yourdomain.com>> RCPT TO:<recipient@example.com>✕ 550 5.7.606 Access denied, banned sending IP (Office 365)
All guides

Is your domain affected?

Run a free check — we'll show you exactly what's misconfigured.

550 5.7.606 is a permanent SMTP reply meaning access denied, banned sending ip (office 365). The 5.7.606–5.7.614 range is "Access denied, banned sender [IP]." Microsoft has flagged your sending IP for spam-like behaviour and blocks it at the edge.

What 550 5.7.606 means

The 5.7.606–5.7.614 range is "Access denied, banned sender [IP]." Microsoft has flagged your sending IP for spam-like behaviour and blocks it at the edge.

⚠️
This is a 5.x.x permanent failure — the message will keep bouncing until you fix the cause. Retrying the same message unchanged won't help.

Common causes

📨
#1

Your sending IP built a poor reputation with Microsoft

Most common

Spam complaints, spam-trap hits, or a compromised account sending through your IP got it onto Microsoft's block list.

🔁
#2

A compromised account or relay on your infrastructure

Common

A breached mailbox or open relay sent spam, and Microsoft banned the originating IP.

⚙️
#3

Shared-IP neighbour abuse

Less common

On a shared sending IP, another sender's spam can get the whole IP banned.

How to fix 550 5.7.606

  1. 1

    Stop the source of abuse first

    Find and shut down whatever caused the bad reputation — secure compromised accounts, close any open relay, fix the spam source. Delisting without this is pointless.

  2. 2

    Submit the Microsoft delisting request

    Use the Microsoft 365 Anti-Spam IP Delist Portal (sender.office.com) to request removal of your IP. It's usually processed within 24–48 hours.

  3. 3

    Lock down authentication and monitoring

    Ensure SPF, DKIM, and DMARC pass and monitor your domain so you catch a repeat before Microsoft re-bans you.

Confirm your domain is set up correctly

Most delivery failures — permanent or temporary — trace back to authentication or reputation. Run a free EmailHealth check to confirm SPF, DKIM, DMARC, blacklist status, and TLS are all healthy for your sending domain. If you send in volume, free daily monitoring will alert you before a small issue becomes a flood of bounces.

Stop this error from coming back

Most delivery problems start when a DNS record changes, a key is removed or a domain lands on a blocklist. EmailHealth checks your sending domains every day and sends one alert, by email, Slack or webhook, with the exact fix.

1 domain free. Sending from many domains (cold email, agencies, MSPs)? Early access covers 10.

Frequently asked questions

Check your domain for free

SPF, DKIM, DMARC, MX, blocklists and TLS in about 2 seconds. No account needed.

Run the check