Exchange Online 5.2.2 has two documented meanings: a sender over the submission quota (10,000 recipients a day) or a recipient mailbox that is full. How to tell them apart and fix quotas, archives, Recoverable Items and public folders.
Home › Guides › Exchange Online 5.2.2
Last updated 17 November 2026
Microsoft documents 5.2.2 for two different problems. Read the text after the code to know which side has to act:
| Side | Wording Microsoft documents | What's wrong |
|---|---|---|
| Sender | 5.2.2 Submission quota exceeded, or "The message can't be submitted because the sender's submission quota was exceeded." | The sender went over the recipient rate limit (10,000 recipients per day) or the message rate limit. It could mean the account is compromised. |
| Recipient | 554 5.2.2 mailbox full with STOREDRV.Deliver.Exception:QuotaExceededException.MapiExceptionQuotaExceeded | The receiving mailbox or public folder is over its quota and can't accept messages. |
The user-facing text Microsoft shows for the full-mailbox case is: "The recipient's mailbox is full and can't accept messages now. Please try resending this message later or contact the recipient directly."
Microsoft says you get this NDR when you exceed the recipient rate limit of 10,000 recipients per day. The NDR reference adds the message rate limit (30 messages per minute). Both are hard service limits and can't be increased.
If the user really sent that much, wait until the 24-hour count drops below the limit. For newsletters or other bulk mail, Microsoft recommends Azure Communication Services Email or a third-party bulk email provider instead of a mailbox.
If the user didn't send it, assume the account is compromised: reset the password, scan devices for malware, and follow the compromised-account steps, because the attacker might have added forwarding Inbox rules or delegates. The 5.1.8 guide lists them. A compromised account that keeps sending often ends up blocked with 5.1.8.
Related sender-side codes: 5.1.90 (you've reached your daily limit for message recipients) and 550 5.7.233 (the tenant exceeded its daily limit for external recipients, TERRL; trial tenants are capped at 5,000 external recipients per day). Lower limits you set in an outbound spam policy can block a user before the service limit does.
Each mailbox has three quotas (Set-Mailbox parameters):
| Quota | What happens when the mailbox reaches it |
|---|---|
IssueWarningQuota | The user gets a warning message. |
ProhibitSendQuota | The mailbox can't send new messages. |
ProhibitSendReceiveQuota | The mailbox can't send or receive. Messages sent to it are returned to the sender with an error. This is effectively the maximum mailbox size. |
Default user mailbox sizes from the Exchange Online limits page: 100 GB for Microsoft 365 Business Basic, Standard and Premium and for Microsoft 365 and Office 365 E3/E5, 50 GB for Office 365 E1 and 2 GB for F3. Shared mailboxes without a license are limited to 50 GB (100 GB with Exchange Online Plan 2), resource mailboxes to 50 GB, group mailboxes to 50 GB and public folder mailboxes to 100 GB. Admins can lower these but can't go past what the license allows.
Get-MailboxStatistics <user> | FL TotalItemSize Get-Mailbox <user> | FL *quota*
Compare TotalItemSize with ProhibitSendReceiveQuota. Add -Archive to Get-MailboxStatistics to see the archive.
Enable-Mailbox -Identity <username> -Archive. The default policy moves items to the archive two years after delivery or creation, and retention only moves items when the primary mailbox is larger than 10 MB. Set-OrganizationConfig -AutoEnableArchiveMailbox $true creates an archive automatically when a primary mailbox reaches 90% of its quota (cloud-only user or shared mailboxes whose license includes archiving).Enable-Mailbox <user mailbox> -AutoExpandingArchive for one user (main archive first) or Set-OrganizationConfig -AutoExpandingArchive for everyone. The archive starts at 100 GB and grows up to 1.5 TB, including Recoverable Items (Microsoft is raising this to 3 TB for eligible E5-level licenses). New space can take up to 30 days, and growth is supported up to 1 GB per day.Set-Mailbox -Identity <user> -ProhibitSendReceiveQuota 100GB -ProhibitSendQuota 99GB -IssueWarningQuota 98GBIf that doesn't take, also run
Set-Mailbox -Identity <user> -UseDatabaseQuotaDefaults:$false.Archive mailboxes are for one user or entity only. Microsoft doesn't permit journaling, transport rules or auto-forwarding to copy other people's mail into one for archiving.
Deleted items go to the Recoverable Items folder, which has its own quota: 30 GB in the primary mailbox when not on hold and 100 GB on hold (RecoverableItemsQuota). Microsoft documents this case for mailboxes on litigation or retention hold with an archive: a new or changed retention policy deletes many items, they land in Recoverable Items, and the default tag Recoverable Items 14 days Move to Archive leaves them there for 14 days. The user can't delete or archive items (so the mailbox fills up) and can't accept calendar invitations.
Get-MailboxFolderStatistics -Identity <user> -FolderScope RecoverableItems Get-RetentionPolicyTag | ft Name,Type,RetentionAction,AgeLimitForRetention Set-RetentionPolicyTag "<Retention_policy_tag>" -AgeLimitForRetention 1 Start-ManagedFolderAssistant <user>
Setting the age limit of the RecoverableItems tag to 1 day and running the Managed Folder Assistant moves the items to the archive. Enabling auto-expanding archiving for one user on hold also adds 10 GB to the Recoverable Items quota (100 GB to 110 GB).
Mail-enabled public folder. 554 5.2.2 means one of these is reached: the organization default post quota (DefaultPublicFolderProhibitPostQuota), the folder's own post quota, or the quota of the content public folder mailbox. Check and raise:
Get-PublicFolderStatistics \pfname | FL TotalItemSize Get-PublicFolder \pfname | FL *quota* Get-OrganizationConfig | FL *quota* Set-PublicFolder \pfname -ProhibitPostQuota 5GB -IssueWarningQuota 4GB Set-OrganizationConfig -DefaultPublicFolderProhibitPostQuota 5GB -DefaultPublicFolderIssueWarningQuota 4GB
Avoid very large per-folder quotas: the default individual public folder limit is 2 GB and Microsoft recommends no more than 25 GB, because bigger folders cause auto-split problems. If the content mailbox is full and auto-split didn't create a new one, open a support request.
AggregateGroupMailbox is full. An NDR naming an AggregateGroupMailbox.A.…@contoso.onmicrosoft.com address when you mail a Microsoft 365 group comes from a deprecated arbitration mailbox. Microsoft says it doesn't affect delivery to the group. The workaround is a transport rule that deletes messages sent to that address (New-TransportRule -SentTo … -DeleteMessage:$true).
A mailbox can also refuse mail because of the number of messages, not their size. The receiving limit is 3,600 messages per hour from all sources, and one sender can use 33% of it. Those NDRs are 5.2.121 (per-hour limit from a specific sender) and 5.2.122 (per-hour limit from all senders). The fix is for the sender to slow down. The Mailboxes exceeding receiving limits report in the Exchange admin center shows which mailboxes hit them.
Need SPF, DMARC and MX checks across a whole client list? Run the Bulk SPF / DMARC / MX Auditor on Apify ($2 per 1,000 domains).
Read the NDR in the Email Header Analyzer, keep cmdlets in the PowerShell Cheat Sheet, confirm the tenant with the M365 Tenant Lookup, look up the recipient domain with the MX Record Lookup, and check the sending domain with the Email Deliverability Checker and SPF Record Checker. Related guides: Exchange Online 550 5.1.8, Exchange Online 5.7.501 to 5.7.503, Exchange Online 5.7.57 (SMTP AUTH), Exchange Online 4.4.7 message expired and bulk sender requirements.
Microsoft documents two meanings. 5.2.2 Submission quota exceeded means the sender went over the recipient rate limit (10,000 recipients per day) or the message rate limit. 554 5.2.2 mailbox full means the recipient mailbox or public folder is over its quota.
The 10,000-recipient limit uses a 24-hour sliding window. The mailbox can send again when the number of recipients sent to in the past 24 hours drops below the limit. If you sent to 10,000 recipients, Microsoft says to wait a day.
No. Microsoft lists the recipient rate limit and the message rate limit as hard limits that can't be increased. Outbound spam policies can only set lower limits. Use Azure Communication Services Email or a bulk email provider for large mailings.
Check TotalItemSize against ProhibitSendReceiveQuota, free space, turn on the archive mailbox and auto-expanding archiving if the license includes it, and fix quotas that weren't raised after a license change with Set-Mailbox. On hold, check the Recoverable Items folder too.
Microsoft documents that a new or changed retention policy can fill the Recoverable Items folder (30 GB, or 100 GB on hold) while the default 14-day tag keeps items there. Set the RecoverableItems tag age limit to 1 day and run Start-ManagedFolderAssistant.
Runbooks, checklists and helpdesk templates: IT Admin Packs on Gumroad.