Home › Exchange Online › 550 5.7.357

Exchange Online · 550 5.7.357 · Exchange Online / Microsoft 365

Exchange Online Error 550 5.7.357 Daily Outbound Message Limit Exceeded

Root cause: Sending mailbox or tenant exceeds daily outbound message limit; Fix: Upgrade subscription, secure compromised account, configure dedicated SMTP relay.

Error Details

FactValueSourceNote
Exact error string550 5.7.357 AggregatedMailbox; Recipient limit exceeded for the sending mailbox or tenant.Exchange Online NDR->
Affected build rangeExchange Online / Microsoft 365Product documentation
Registry key involved
Relevant service/endpoint URLhttps://admin.exchange.microsoft.comExchange Admin Center (EAC)->
Log line signatureMicrosoft-Windows-Security-Auditing Event ID 4625 or 4648Event Viewer

Log Files to Check

What This Error Actually Means

The error code "550 5.7.357 AggregatedMailbox; Recipient limit exceeded for the sending mailbox or tenant." is raised by Exchange Online when a user attempts to send an email that exceeds their daily outbound message limit. This restriction applies to both standard and high-volume licenses, with limits of 10,000 recipients per day for standard tenants and 100,000 recipients for high-volume license holders. The error is generated by the Microsoft.Exchange.Transport.AggregatedMailbox component within Exchange Online, which monitors and enforces these daily recipient caps to prevent abuse and ensure service stability.

Affected Versions and Scope

This issue affects all versions of Exchange Online as part of the Microsoft 365 suite. The restriction is enforced across all tenants regardless of their geographical location or language settings. However, it does not apply to users who have been granted a higher daily send limit through specific licensing agreements or those using dedicated transactional email services like Azure Communication Services or SendGrid.

Where To Look First: Logs and Event IDs

To diagnose this issue effectively, start by examining the logs generated by Exchange Online. The relevant log files include: The Security.evtx file contains Event IDs 4625 and 4648, which can indicate login failures or logon attempts with explicit credentials. These events may suggest a compromised account being used for unauthorized bulk email sending.

Root Causes

Bulk Email Campaigns from Single Mailbox

This scenario occurs when a user sends large volumes of emails to multiple recipients, often as part of marketing or newsletter campaigns. You can identify this by checking the Message Trace in Exchange Admin Center (EAC) and observing high recipient counts per trace row.

Compromised Account Used for Spam

If an account has been compromised, it may be used to send out large volumes of spam emails. This can often be detected through Event IDs 4625 or 4648 in the Security logs, indicating unauthorized access attempts.

Automated Scripts Exceeding Daily Caps

Automated scripts running via SMTP relay or PowerShell may inadvertently exceed daily send limits due to high-frequency operations. This can be identified by reviewing script execution logs and checking for patterns of excessive outbound mail volume.

Fix Procedure

To resolve the issue, follow these steps:
  1. Confirm Active Mailbox: Use Exchange Online PowerShell to verify the mailbox is active.
    Get-MailboxStatistics -Identity  | Select DisplayName,TotalItemSize
    
  2. Check Message Trace: Navigate to Exchange Admin Center > Mail flow > Message trace and run a trace on the sender for the past 24 hours. Look for high recipient counts (>500/trace row).
  3. Review Outbound Spam Filter Policy: Go to Microsoft 365 Defender > Email & collaboration > Policies & rules > Threat policies > Anti-spam policies > Outbound and review the outbound spam filter policy.
  4. Analyze Recipient Limits: Use PowerShell to check recipient limits.
    Get-HostedOutboundSpamFilterPolicy | Select RecipientLimitExternalPerHour,RecipientLimitInternalPerHour,RecipientLimitPerDay
    
  5. Check Restricted Senders List:
    Get-BlockedSenderAddress
    
    If the sender is listed as a restricted sender, remove them.
    Remove-BlockedSenderAddress -SenderAddress 
    
  6. Upgrade Subscription or Use Transactional Email Service: If legitimate high-volume mail is being sent, consider upgrading to Microsoft 365 E3/E5 or using Azure Communication Services/SendGrid.
  7. Secure Compromised Account: Reset the password immediately and revoke all active sessions.
    Revoke-AzureADUserAllRefreshToken -ObjectId 
    
  8. Remove Inbox Rules: Use PowerShell to remove any inbox rules that might be contributing to high volume sending.
    Get-InboxRule -Mailbox 
    
  9. Apply Conditional Access Policy: Entra admin center > Protection > Conditional Access > New policy and require MFA.
  10. Configure SMTP Relay: Exchange Admin Center > Settings > Mail flow > Connectors — use an IP-restricted inbound connector tied to your relay IP.
Be cautious when configuring SMTP relays as incorrect settings can break enrolled devices or disrupt email delivery.
A quick diagnostic shortcut is to check the Message Trace for high recipient counts immediately after receiving the 550 5.7.357 error.

Error Code Variants

CodeDescription
550 5.1.6User not found; indicates the recipient's email address is invalid or does not exist.
550 5.7.348Recipient limit exceeded for the sending mailbox or tenant, but specific to internal recipients only.
550 5.1.29Mailbox is full; indicates the recipient's mailbox has reached its storage quota.

Verification

To verify that the fix was successful, check the following:

Prevention

To prevent recurrence of this error: By following these guidelines, you can effectively diagnose and resolve issues related to the "550 5.7.357 AggregatedMailbox" error in Exchange Online environments.

Sources & References

Related Guides

Get new error code fixes by email

Product-specific solutions for Intune, Autopilot, SCCM and Entra ID — straight to your inbox. No spam.