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

5.7.513: sending 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.

Microsoft
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
5.7.513
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.513 Service unavailable, Client host [$ConnectingIP] blocked by $recipientDomain using Customer Block list…

What it means

With 5.7.513 the block comes from the recipient domain, which has put your sending IP on a custom block list of its own. The bounce names the recipient domain and carries the reference AS16012607. Microsoft's guidance is to contact the recipient directly if you believe the listing is a mistake and ask them to remove your IP, since the list belongs to them.

Common causes

  • The recipient's admin added your IP to their block list, often after receiving unwanted mail from it.
  • You send from a shared IP that the recipient blocked because of another sender.

How to fix it

  1. 01Contact the recipient through another channel and ask them to remove your IP from their block list.
  2. 02Give them the IP address and the exact bounce text.
  3. 03If the IP is shared, ask your email provider whether you can move to another one.

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.507Sending 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.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