1. Home
  2. SMTP codes
  3. 550 5.7.513
Permanent failure — do not retry
BlockAbout your sending, not the address

SMTP 550 5.7.513

Blocked by the recipient's own block list (Microsoft 365)

550 5.7.513 means the recipient's organisation added your sending IP to its own block list in Microsoft 365. It is not Microsoft's block but theirs. Only that organisation can remove it, so contact the recipient another way if you think it was a mistake, and stop sending there until then.

Should you remove the address?

Suppress the address if it keeps failing

Suppress the whole domain for now. Every address there will reject you until their admin lifts the block.

Block. Retrying changes nothing until the cause on your side is fixed.

How it appears

Service unavailable, Client host <IP> blocked by <recipient domain> using Customer Block list (AS16012607)

What causes it

  • The recipient's admin added your sending IP to their own block list.
  • Another sender on a shared IP caused the block.
  • Earlier mail from you was reported or judged unwanted by that organisation.

How to fix it

In order — try the first one first.

  1. Stop sending to that domain.
  2. If the mail was wanted, ask the recipient by phone or another channel to have their admin remove the block.
  3. If you share the IP with others, the block may have been triggered by another sender. A dedicated IP or a different sending service avoids that.

Who sends it

Microsoft 365 tenants.

Common questions

What does SMTP 550 5.7.513 mean?
550 5.7.513 means the recipient's organisation added your sending IP to its own block list in Microsoft 365. It is not Microsoft's block but theirs. Only that organisation can remove it, so contact the recipient another way if you think it was a mistake, and stop sending there until then.
Should I retry a 550 5.7.513 error?
No. 550 is a permanent failure, so the message will never be delivered no matter how many times you try. Remove the address — repeated sends to permanent failures are one of the main signals mailbox providers use to throttle a sender.
How do I fix SMTP 550 5.7.513?
Stop sending to that domain.
Is 550 5.7.513 a hard bounce or a soft bounce?
550 5.7.513 is a block rather than a classic hard or soft bounce. The rejection is about your sending (authentication, reputation, content or the recipient's policy), not about whether the address exists. Retrying changes nothing until the cause on your side is fixed.
Should I remove the address after a 550 5.7.513 bounce?
Suppress the whole domain for now. Every address there will reject you until their admin lifts the block.
Will verifying my list prevent 550 5.7.513?
Not directly. This code is about your authentication, IP or domain reputation, so verification will not lift it. A clean list still matters, because mailbox providers weigh how often a sender hits addresses that don't exist.

Clean the list before the next send.

A bounce report only tells you about the addresses you already mailed. The rest of the list has the same kinds of dead mailboxes in it, and each one becomes a hard bounce recorded against your domain the moment you send.

  • A real SMTP mailbox check on every row, before anything is sent
  • Dead and mistyped addresses split out, so they never reach your sending tool
  • Catch-all, disposable and role addresses flagged alongside

One plan, cancel anytime, no contract. Sign in with Google and your first 100 email checks are free, no card. The free tools stay free either way.

Other 550 replies

Sources

Provider wording is quoted only where the provider publishes it.

Last reviewed 2026-10-22

Clean your next list before it bounces

100 free email checks when you sign in with Google, no card. Then monthly plans from $9, or one flat price with fair use, never cut off.

100 free checks, no card Cancel anytime Secure payment by Stripe