About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
The code 5.1.90 with the text "Your message can't be sent because you've reached your daily limit for message recipients" means one mailbox has used up its recipient rate limit. Microsoft's pages set that limit at 10,000 recipients per day, counted over a sliding 24 hours, and state that it is a hard limit enforced by the service that cannot be increased.
The practical steps are to find what is sending, rule out a compromised account, let the window clear and move any bulk sending off the mailbox. This code is about one mailbox; a tenant-wide limit gives a different code.
What the error means
Microsoft's NDR reference lists the code: "5.1.90 Your message can't be sent because you've reached your daily limit for message recipients. The sender exceeded the recipient rate limit, as described in Sending limits. This error could indicate that the account was compromised and is being used to send spam."
Microsoft's page on outbound sending limits sets out the per-user numbers:
- Recipient rate limit: 10,000 recipients per day, on a 24-hour sliding window. "The mailbox can't send until the number of recipients sent to in the past 24 hours drops below the limit."
- Message rate limit: 30 messages per minute. Excess submissions are throttled and carried over to following minutes, with no NDR.
- Recipient limit per message: 500 recipients by default, customisable from 1 to 1000.
The page says the recipient rate limit and the message rate limit "are hard limits enforced at the service level and can't be increased."
Counting matters. For the recipient rate limit, "distribution groups in the organization's address book count as one recipient. Distribution groups in a mailbox's Contacts folder are counted individually by member." The limits page adds that the limit is applied per user to all outbound and internal messages, and that sending from another mailbox through permissions is counted for the delegate with the rights, not for the mailbox being sent from.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| One person or process sending to very many recipients | 5.1.90 from one mailbox; others unaffected | Message trace for that sender; the Email sending limit exceeded alert |
| An application or device sending through one mailbox | A service account hits the limit daily | Microsoft says client SMTP submission and SMTP relay are both subject to the per-user limits |
| Large personal distribution lists | A message to one list uses hundreds of recipients | Lists in the Contacts folder count each member |
| Delegate sending | The person with Send As or Send on behalf rights hits it | The limits page says delegate sending is counted for the delegate |
| A compromised account sending spam | Sudden volume, unknown rules, restricted user | Sign-in logs, inbox and forwarding rules, recent sent items |
| A different limit | 550 5.7.233, not 5.1.90 | Microsoft says 5.7.233 is the tenant external recipient rate limit |
Microsoft's pages give no figures for how many cases fall under each cause, so the table is not in order of likelihood.
Prove the cause before changing anything
All of these only read.
- Copy the exact code and text from the bounce, and the time the mailbox first received it.
- Check which mailbox. A delegate sending as another mailbox counts against the delegate, per the limits page.
- In the Exchange admin center, open the Mail flow reports page at
https://admin.exchange.microsoft.com/#/reports/mailflowreportsmain. Microsoft's page lists the Tenant Outbound External Recipients report, which shows tenant external recipient usage. A tenant at its external limit shows 5.7.233, not 5.1.90. - In the Microsoft Defender portal, open the Alert policy page at
https://security.microsoft.com/alertpoliciesv2and search for the Email sending limit exceeded policy. Microsoft says it is enabled by default and notifies the TenantAdmins group when a user exceeds the outbound limits. - Open the Restricted entities page at
https://security.microsoft.com/restrictedusersand see whether the user is listed. Microsoft says in some cases a user over the limit also appears there. - Use message trace in the Microsoft Defender portal to follow individual outbound messages from that sender and identify the large sends.
- Before deciding it is a bulk job, check for compromise. Microsoft's page says to check sign-in logs for suspicious activity, look for unknown inbox rules or forwarding rules, and check recent sent items.
Example (illustrative): at contoso.com.au the shared mailbox invoices@contoso.com.au is used by a billing application on app01. It sends 4,000 recipients at 09:00, 3,500 at 10:00 and 2,500 at 11:00. That is 4,000 plus 3,500 plus 2,500, which equals 10,000, so the 11:00 send reaches the limit and the next send is refused with 5.1.90. The mailbox can send again once the past-24-hour count is below 10,000, which starts when the 09:00 batch ages out at 09:00 the next day, as in the worked example on Microsoft's limits page. Other mailboxes in the tenant are not affected, because the limit is per user.
Fix
Microsoft's page gives no step that raises the recipient rate limit. The workable steps are these.
Wait for the window to clear
The mailbox can send again once the number of recipients sent to in the past 24 hours drops below 10,000. Microsoft's page says in some cases the user also appears on the Restricted entities page. In that case Microsoft says to determine why the restriction was applied before unblocking the user, and points to its page on removing blocked users from the Restricted entities page.
Rule out a compromise first
Microsoft's NDR page says the error could indicate that the account was compromised, and its sending-limits page says to check sign-in logs, unknown inbox or forwarding rules and recent sent items. If the account is compromised, follow Microsoft's compromised account guidance before you clear anything. Microsoft also lists enabling MFA among its ways to prevent future blocks.
Move bulk sending off the mailbox
Microsoft says Exchange Online "isn't designed for bulk mailing scenarios" and recommends a dedicated bulk email service provider. The alternatives it names are Azure Communication Services Email, non-Microsoft bulk email providers and on-premises email servers. For applications and devices, it names SMTP relay through a connector or a non-Microsoft bulk service. Microsoft notes SMTP relay is still subject to Exchange Online sending limits, at 10,000 recipients per day for each mailbox used for relay, while Direct Send sends to internal recipients only.
Spread the sends, then resend
If a bulk send has to run through Exchange Online, Microsoft's page says to spread bulk sends over time, to keep to no more than 30 messages per minute per mailbox, and to use a custom subdomain for bulk email.
Before you resend, use message trace in the Microsoft Defender portal to list who received the original send, and keep that list with the ticket.
Risk: The next step, sending the blocked message again, can deliver a duplicate to anyone who already received it. The earlier send may have reached part of the list before the limit was hit.
Resend to the missing recipients in batches that keep the 24-hour total under 10,000.
There is no way back from a message that has been delivered twice, which is why the list from the message trace comes first.
Control future sending
Microsoft says admins can add limits in outbound spam policies: an external message limit and an internal message limit, each per hour, and a daily message limit for the maximum total number of recipients per day, each from 0 to 10,000 with 0 meaning the service default. It suggests custom alert policies that warn before limits are reached. The sending-limits page gives no portal steps for these.
Confirm the fix
- After the window clears, a new test message to one or two recipients is delivered with no 5.1.90.
- The user is no longer on the Restricted entities page, if they were listed.
- The Email sending limit exceeded alert stops firing for that user.
- A message trace for the sender shows the new volumes inside the limit.
What to watch afterwards
- Daily recipient totals for any service mailbox. Microsoft's mail flow reports show outbound sending.
- Mailing lists kept in a Contacts folder, which count member by member.
- Any new application that sends through a mailbox, since SMTP relay is counted against the mailbox used.
Read next
Related articles you may want next.
- TroubleshootingExchange Online '550 5.1.8 Access denied, bad outbound sender': a user is restricted from sending in Microsoft 365550 5.1.8 bad outbound sender: a user is on the Restricted entities page. Check for compromise first, then unblock in the portal or PowerShell.Read article
- TroubleshootingExchange Online 550 5.7.708 'Access denied, traffic not accepted from this IP': what it means and how to clear itExchange Online 550 5.7.708 blocks mail from a low-reputation IP, more likely on trial tenants. How to confirm it, and what 5.7.703, 705, 750 mean.Read article
- Troubleshooting550 5.7.64 TenantAttribution; Relay Access Denied: an application server can't relay through Microsoft 365550 5.7.64 TenantAttribution; Relay Access Denied: find why Microsoft 365 no longer recognises your server and fix the connector or certificate.Read article
Risks and limits
Microsoft's pages describe Exchange Online only and give figures as of their dates. They say these limits are hard limits and cannot be increased, so no request to Microsoft is described as a way to raise them. Microsoft's pages do not say how many recipients a message has counted when a group is nested, other than that group members are counted after expansion for the tenant external limit. Check the current pages before you quote a figure to a customer.
Sources
- Email nondelivery reports (NDRs) and SMTP errors in Exchange Online — Microsoft Learn, page dated 2026-08-24, accessed 22 November 2026
- Troubleshoot outbound sending limits and blocked users in Exchange Online — Microsoft Learn, page dated 2026-05-27, accessed 22 November 2026
- Exchange Online limits — Microsoft Learn, page dated 2026-11-11, accessed 22 November 2026
This article was originally published on .