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

550 5.1.8: account blocked for sending spam

Microsoft 365 has blocked this user from sending because the account sent spam or exceeded its sending limits, usually after a compromise.

Microsoft
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
550 5.1.8
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 sender. The fix is on the sending side: your domain, your server or your list.
What the server says
550 5.1.8 Access denied, bad outbound sender

What it means

Exchange Online adds an account to its Restricted entities list when it sends spam or exceeds the outbound sending limits, and from then on its messages bounce with 550 5.1.8. Most of the time the account was compromised through phishing or malware and used to send spam. The block is on the sender's own mailbox; recipients and other users are not affected. An admin has to secure the account and then release it in the Microsoft Defender portal, after which Microsoft says restrictions are usually removed within one hour.

Common causes

  • The account was compromised and used to send spam.
  • The user, or an application sending as the account, exceeded the Exchange Online sending limits.

How to fix it

  1. 01Tell your admin and stop retrying.
  2. 02Admins: secure the account first by resetting the password, checking sign-in activity, and removing inbox rules or forwarding added by an attacker.
  3. 03Unblock the user on the Restricted entities page in the Microsoft Defender portal (security.microsoft.com/restrictedusers).
  4. 04Turn on multifactor authentication for the account to prevent a repeat.

Sources

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

  1. 5.1.90Daily recipient limit reached.The sending mailbox has reached the Exchange Online recipient rate limit for a 24-hour period and cannot send to more recipients for now.MicrosoftPermanent
  2. 5.2.2Submission quota exceeded.The sender went over the Exchange Online recipient or message rate limit, so Microsoft 365 refused to accept more mail from the account.MicrosoftPermanent
  3. 5.7.501Sending account banned for spam abuse.Microsoft 365 banned the sending account after detecting spam from it; Microsoft support has to restore its ability to send.MicrosoftPermanent

Further reading

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