Opens in a new tab

Outlook.com 550 SC-001: mail rejected by Outlook.com for policy reasons

Outlook.com refused the message “for policy reasons”, and the code after 550 says which: spam-like content or a poor IP or domain reputation (SC-001, OU-002), dictionary attacks (SC-002), an open relay (SC-003), complaints (SC-004) or a compromised machine (DY-002).

550 SC-001 Mail rejected by Outlook.com for policy reasons. Reasons for rejection may be related to content with spam-like characteristics or IP/domain reputation.
5 other wordings of the same rejection

Namespace mining (SC-002):

550 SC-002 Mail rejected by Outlook.com for policy reasons. The mail server IP connecting to Outlook.com has exhibited namespace mining behavior.

Open proxy or relay (SC-003):

550 SC-003 Mail rejected by Outlook.com for policy reasons. Your IP address appears to be an open proxy/relay.

Complaints (SC-004):

550 SC-004 Mail rejected by Outlook.com for policy reasons. A block has been placed against your IP address because we have received complaints concerning mail coming from that IP address. We recommend enrolling in our Junk Email Reporting Program (JMRP)

Compromised or infected server (DY-002):

550 DY-002 Mail rejected by Outlook.com for policy reasons. The likely cause is a compromised or virus infected server/personal computer.

Content or reputation (OU-002):

550 OU-002 Mail rejected by Outlook.com for policy reasons. Reasons for rejection may be related to content with spam-like characteristics or IP/domain reputation.
Code550 SC-001
Sent byOutlook.com
TypePermanent — not retried
CauseReputation

Is your mail server on a blocklist?

Enter the sending IP address from the bounce, or your domain to check its mail servers.

What it means

These are about the sending IP’s behaviour, not your DNS records. Microsoft’s advice for all of them is to contact your email provider if you are not the administrator, and — if you run the server and follow Microsoft’s policies — to open a support request.

Why it happens

  • Spam from a compromised account or server behind the address.
  • Mailing lists with many addresses that do not exist (namespace mining).
  • A server that relays mail for anyone.
  • Complaints from Outlook.com users.

How to fix it

  1. Check the sending address on the blocklists below and fix the cause first.
  2. Close any open relay, and clean or rebuild a compromised server.
  3. Enrol the address in Microsoft’s SNDS and JMRP to see its reputation and the complaints.
  4. Then request a review through the Outlook.com postmaster support form.

Outlook.com postmaster troubleshooting →

Read Outlook.com complaints about your domain →

Sources

Message text and meaning checked on 25 September 2026 against these official sources:

Catch it before the bounces start

Add your domain and we monitor what these bounces are about — SPF, DKIM, DMARC, your sending servers on the blocklists, Gmail’s spam rate — every day, and email you the day something changes. Free for your first domain.

Create a free account