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

SMTP 550 5.7.12

Sender not authenticated by organization (Microsoft 365)

550 5.7.12 means the recipient's Microsoft 365 address only accepts mail from inside its own organisation, so mail from outside is rejected. Related codes 5.7.133, 5.7.134 and 5.7.136 say the same for groups, mailboxes and mail users. Only the recipient's admin can change it.

Should you remove the address?

Remove the address from your list

Remove it from external sends. It will reject anything from outside the organisation for as long as the setting stays.

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

What causes it

  • The recipient mailbox or group only accepts mail from inside its organisation.
  • It is a shared or departmental address not meant for outside mail.
  • An admin restricted external senders after spam or phishing.

How to fix it

In order — try the first one first.

  1. Contact the person through another channel or a different address.
  2. If you have a relationship with the organisation, ask their admin to allow external senders for that address.

Who sends it

Microsoft 365 and Exchange Online.

Common questions

What does SMTP 550 5.7.12 mean?
550 5.7.12 means the recipient's Microsoft 365 address only accepts mail from inside its own organisation, so mail from outside is rejected. Related codes 5.7.133, 5.7.134 and 5.7.136 say the same for groups, mailboxes and mail users. Only the recipient's admin can change it.
Should I retry a 550 5.7.12 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.12?
Contact the person through another channel or a different address.
Is 550 5.7.12 a hard bounce or a soft bounce?
550 5.7.12 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.12 bounce?
Remove it from external sends. It will reject anything from outside the organisation for as long as the setting stays.
Will verifying my list prevent 550 5.7.12?
Not reliably. The address exists, so a mailbox check may accept it; the restriction only shows at delivery.

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