Skip to content
Microsoft (Outlook.com and Microsoft 365) · permanent error

5.7.507: sending IP blocked by the recipient organization

The recipient's organization has blocked the IP address you send from; only the recipient can lift the block.

Microsoft
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
5.7.507
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The recipient's side. Their mail admin has to change something; you can tell them.
What the server says
5.7.507 Access denied, rejected by recipient

What it means

5.7.507 means the block was set by the recipient's organization: it has blocked the IP address you are sending from. Microsoft's guidance is simply to contact the recipient, because the decision is theirs. Microsoft's own delisting routes, the delist portal and delist@microsoft.com, are for blocks Microsoft places, so they do not apply here. Reach the recipient by some other channel and ask them to have their admin remove the block.

Common causes

  • The recipient organization blocked your sending IP, perhaps after unwanted mail from it.
  • You share a sending IP with another sender the recipient chose to block.

How to fix it

  1. 01Contact the recipient by phone or another channel and ask them to have the block removed.
  2. 02Give them the IP address from the bounce and the time of the attempt.
  3. 03If you use a shared IP from an email provider, ask the provider about a different IP.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 5.7.513Sending IP on the recipient's custom block list.The recipient domain added your sending IP address to its own custom block list, so its Microsoft 365 tenant refuses your mail.MicrosoftPermanent

All 111 Microsoft codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer