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.
Mail sent to a shared address bounces with "The recipient's mailbox is full and can't accept messages now", and the diagnostic text ends "554 5.2.2 mailbox full" with a quota exception. If the address belongs to a mail-enabled public folder, Microsoft lists three possible causes: the organisation's default public folder post quota was reached, the folder's own post quota was reached, or the public folder mailbox that hosts the folder reached its quota. You find out which by reading each value in order, and you change only the one that is reached.
These steps apply to mail-enabled public folders, the case Microsoft's page describes. A person's own mailbox is a different case and these steps do not apply to it.
What the error means
The NDR (non-delivery report, or bounce) that Microsoft shows reads:
The recipient's mailbox is full and can't accept messages now. Please try resending this message later or contact the recipient directly.
Diagnostic information for administrators
Remote Server returned '554 5.2.2 mailbox full;
STOREDRV.Deliver.Exception:QuotaExceededException.MapiExceptionQuotaExceeded'
Three quotas can produce it. The organisation default is DefaultPublicFolderProhibitPostQuota. The folder's own value is ProhibitPostQuota, set per folder. And the hosting mailbox has its own quota, checked through ProhibitSendReceiveQuota.
How they interact matters. Microsoft's note says that if the folder's value is left at its default of Unlimited, the organisation-level DefaultPublicFolderProhibitPostQuota applies, and that a value configured on the folder takes precedence over the organisation value. Microsoft's reference for the parameter says users cannot post to a folder whose size is larger than the quota, and that the folder owners get a warning at the IssueWarningQuota size, which is meant to come earlier.
The bounce tells the sender to try again later or to contact the recipient. For a folder that has reached its quota, a resend cannot succeed until an admin raises the quota or the folder is cleared, so the sender is better off forwarding the bounce to whoever administers Exchange Online. Ask them for the full bounce text, including the diagnostic lines, because the exception name is what separates this fault from other delivery problems. A message trace in the Exchange admin center, under Mail flow, then Message trace, shows what happened to the message. Trace data can take from 10 minutes to an hour to appear.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Organisation default post quota reached | Several folders bounce | TotalItemSize is larger than DefaultPublicFolderProhibitPostQuota |
| One folder's own post quota reached | Only that folder bounces | TotalItemSize reaches or exceeds the folder's ProhibitPostQuota |
| Content public folder mailbox reached its quota | Folders hosted in that mailbox bounce; Microsoft says auto-split "should create" a new mailbox when a quota is reached, so check whether one was added | Mailbox TotalItemSize exceeds its ProhibitSendReceiveQuota |
Prove the cause before changing anything
All of these are read-only. Connect to Exchange Online PowerShell first. The folder name below is an example in the same \name form Microsoft uses.
Check the folder's size and its own quota:
Get-PublicFolderStatistics \Sales | Format-List TotalItemSize
Get-PublicFolder \Sales | Format-List *quota*
Microsoft writes Format-List as FL. Compare TotalItemSize with ProhibitPostQuota. If the size reaches or exceeds the quota, the folder's own quota is the cause.
Then the organisation values:
Get-OrganizationConfig | Format-List *quota*
A TotalItemSize larger than DefaultPublicFolderProhibitPostQuota stops mail-enabled public folders from accepting new email.
Microsoft's Step 2 follows its folder and organisation checks: "If the public folder exceeds the individual or organizational quota as shown in Step 1, check if the public folder mailbox hosting the public folder content exceeds its quota." So if either folder value above was reached, read the hosting mailbox next. Microsoft's cause list also names the hosting mailbox reaching its quota as a cause of its own. If both folder values are within their quotas and mail still bounces with this exception, reading the hosting mailbox values costs nothing. Find its name, then its size and quota:
Get-PublicFolder \Sales | Format-List name, *content*
Get-MailboxStatistics PFMBX01 | Format-List TotalItemSize
Get-Mailbox -PublicFolder PFMBX01 | Format-List *quota*
Compare TotalItemSize with ProhibitSendReceiveQuota.
Read all three results before you change anything. More than one quota can be reached at once.
- Folder size at or above the folder's own
ProhibitPostQuota: the folder quota is reached. Go to the folder fix, and also read the hosting mailbox. - Folder size above
DefaultPublicFolderProhibitPostQuotaand the folder has no value of its own: the organisation default is reached. Also read the hosting mailbox. - Both folder values are fine but the hosting mailbox is at or over its quota: the mailbox quota is the cause, and the auto-split check below decides the next step.
Microsoft's reference for the organisation setting adds two details. DefaultPublicFolderProhibitPostQuota applies to all folders and its default is unlimited. DefaultPublicFolderIssueWarningQuota applies to folders that do not have their own warning quota set, and its default is also unlimited. If the folder shows Unlimited, the organisation value is the one that counts.
When a quota is reached, Microsoft says the auto-split process should create a new public folder mailbox and move some of the content to it. Check that with:
Get-PublicFolder \Sales | Format-Table name, *content*
Example (illustrative): the folder \Sales on contoso.com.au has a ProhibitPostQuota of 2 GB and a TotalItemSize of 2.1 GB, so it is 0.1 GB over. The organisation default is Unlimited and the hosting mailbox is well under its quota. The folder's own quota is the cause. Raising it to 3 GB, with a warning at 2.5 GB, gives 3 - 2.1 = 0.9 GB of headroom and warns owners only once the folder grows past 2.5 GB. That is a 50 per cent increase on the old value.
Fix
Raise only the quota you proved was reached. Save the current values first, as files, because the back-outs below depend on them:
Get-PublicFolder \Sales | Format-List *quota* | Out-File -FilePath .\sales-folder-quota-before.txt
Get-OrganizationConfig | Format-List *quota* | Out-File -FilePath .\org-quota-before.txt
Microsoft's reference says to qualify a quota value with a unit, such as B, KB, MB, GB or TB. The saved file may show a value such as "5 GB (5,368,709,120 bytes)"; when you restore it, type only the value with its unit, for example 5GB, not the bytes in brackets. Keep the warning quota below the prohibit quota, as Microsoft's own example does with 5GB and 4GB, so owners are warned before senders are blocked.
Folder quota. It raises the post quota and the warning quota of one folder together.
Disruptive step: the command below changes how much a public folder can hold. Microsoft warns to avoid a large increase of an individual folder's ProhibitPostQuota, because setting it too high affects the auto-split process negatively. Save-first: sales-folder-quota-before.txt from above. Back-out: run the same command with the values in sales-folder-quota-before.txt, each written with its unit. If the old value was Unlimited, use Unlimited, which the parameter accepts.
The form is Microsoft's; the values are examples:
Set-PublicFolder \Sales -ProhibitPostQuota 3GB -IssueWarningQuota 2.5GB
Organisation default. Use this when many folders are affected.
Disruptive step: the command below changes the limit for every public folder that has no value of its own, so it affects far more folders than the one that bounced. Save-first: org-quota-before.txt from above. Back-out: run the command again with the values in org-quota-before.txt, each written with its unit.
Microsoft's example sets both values:
Set-OrganizationConfig -DefaultPublicFolderProhibitPostQuota 5GB -DefaultPublicFolderIssueWarningQuota 4GB
Hosting mailbox. If the hosting mailbox has reached its quota, the auto-split process should have created a new mailbox. If it did not, Microsoft's instruction is to submit a support request to Microsoft Support. Microsoft gives no command to change this quota yourself.
Confirm the fix
Ask the sender to send a new message to the folder address. Check that the folder receives it, and look for the item in the folder itself rather than assuming delivery from the absence of a bounce. Run the read-only commands again and confirm TotalItemSize is now below the quota you raised, with room to spare. Confirm the warning quota is lower than the prohibit quota, so owners are warned before senders are blocked. Write the old and new values in the change record together with the date, so a later admin can see what was changed and why.
What to watch afterwards
- Folder growth against its quota. Reading
TotalItemSizemonthly shows whether a raise bought months or days. - The warning quota. Folder owners are warned at that size, and a warning that nobody reads gives no protection.
- Whether the auto-split process creates new public folder mailboxes when a mailbox fills.
- Old items. Raising a quota only delays the next bounce, so decide with the folder owner what can be removed or archived.
- Who owns each mail-enabled public folder. A folder with no owner has nobody to receive the warning message, so assign one when you raise its quota and write down the name next to the new values.
Read next
Related articles you may want next.
- TroubleshootingMicrosoft 365 mailbox almost full: archive, auto-expanding archiving and quota optionsMailbox nearly full in Microsoft 365? Compare clean-up, archive, licence change and auto-expanding archiving, with limits and what cannot be undone.Read article
- Troubleshooting550 5.1.10 RESOLVER.ADR.RecipientNotFound: a Microsoft 365 user can't email a hybrid user whose address existsMicrosoft 365 user gets 550 5.1.10 RESOLVER.ADR.RecipientNotFound sending to a hybrid user? Check the on-premises object and ExchangeGuid, then fix.Read article
- Backup & RecoveryMicrosoft 365 Data: What Native Retention Restores, What It Does Not, and Graph API ThrottlingWhat Exchange Online, SharePoint, OneDrive and Teams can put back, for how long and by whom, and the Graph API limits on backup and restore time.Read article
Risks and limits
These commands have not been run or lab-tested. The values 3GB, 2.5GB, 5GB and 4GB are examples, and Microsoft's page does not say what size is right for your folders. The Set-PublicFolder reference says the default of Unlimited equals 2 terabytes, while the NDR page says an Unlimited folder value defers to the organisation default, so read your own values before assuming either. An ordinary user mailbox that is full, or a shared mailbox, is a different case, so use this only when the recipient address is a mail-enabled public folder. The PowerShell reference pages show no date. Increasing quotas does not free space, and Microsoft warns that setting an individual folder's ProhibitPostQuota too high affects the auto-split process negatively.
Sources
- "554 5.2.2 mailbox full" when sending emails to a mail-enabled public folder — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- Find and fix email delivery issues as a Microsoft 365 for business admin — Microsoft Learn, page dated 2025-06-25, accessed 20 November 2026
- Out-File — Microsoft Learn, date not shown, accessed 20 November 2026
- Set-PublicFolder — Microsoft Learn, date not shown, accessed 20 November 2026
- Get-PublicFolder — Microsoft Learn, date not shown, accessed 20 November 2026
- Set-OrganizationConfig — Microsoft Learn, date not shown, accessed 20 November 2026
This article was originally published on .