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

5.1.90: daily 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.

Microsoft
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
5.1.90
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
5.1.90 Your message can't be sent because you've reached your daily limit for message recipients

What it means

Exchange Online caps how many recipients one mailbox can send to in 24 hours, to discourage unsolicited bulk mail. When the cap is reached, further messages bounce with 5.1.90 until earlier sends fall outside the window. Microsoft warns that reaching the limit can mean the account was compromised and is being used to send spam. For legitimate bulk commercial email, it recommends third-party providers that specialize in it, or Azure Communication Services for high-volume mail to external recipients.

Common causes

  • The user sent to more recipients in 24 hours than the recipient rate limit allows.
  • The account is compromised and sending spam.
  • An application uses a user mailbox for bulk sending.

How to fix it

  1. 01Check Sent Items for messages you did not send; if you find any, report a possible compromise to your admin.
  2. 02Wait for the 24-hour window to move on before sending more.
  3. 03Move newsletters and bulk sends to a service built for them.
  4. 04Admins: if the volume was not legitimate, follow Microsoft's steps for responding to a compromised account.

Sources

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

  1. 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
  2. 550 5.1.8Account 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.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