Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

License Error 552 5.2.2

552 5.2.2 mailbox full: recipient quota and hourly receive limits in Exchange

11 min read Updated October 5, 2026 Exchange Server

Fix it now

The recipient hit a limit. Which limit depends on where the mailbox lives: RFC 3463 defines the 5.2.2 class as a mailbox full because a quota or physical capacity was exceeded, while Microsoft publishes 5.2.2 in Exchange Online as Submission quota exceeded, which is a limit on the sender. Establish which before you raise anything.

Run these in the Exchange Management Shell, in order

Get-MailboxStatistics user@contoso.com | Format-List DisplayName,TotalItemSize,TotalDeletedItemSize,ItemCount,StorageLimitStatus

Get-Mailbox user@contoso.com | Format-List *Quota*,UseDatabaseQuotaDefaults

Get-MailboxDatabase DB01 | Format-List *Quota*
  1. Read StorageLimitStatus. It tells you directly whether the mailbox is below limit, at warning, or past the prohibit send or prohibit send and receive threshold.
  2. If UseDatabaseQuotaDefaults is True, the numbers that matter are on the database, not on the mailbox. Changing mailbox values while it is True does nothing.
  3. Check the hidden half too: TotalDeletedItemSize and RecoverableItemsQuota. A mailbox on hold can fill Recoverable Items while the visible mailbox looks small.
  4. Raise the limit for that one mailbox and turn inheritance off in the same command: Set-Mailbox user -UseDatabaseQuotaDefaults $false -IssueWarningQuota 45GB -ProhibitSendQuota 48GB -ProhibitSendReceiveQuota 50GB
  5. Confirm StorageLimitStatus reads BelowLimit before you ask the sender to try again.

In Exchange Online, 5.2.2 points at the sender rather than the recipient, and can indicate a compromised account sending in volume. Check the sender’s activity before assuming anyone’s mailbox is full.

If the mailbox is back below limit and mail flows, stop here. If you are looking at a 5.2.12x code, that is a rate limit, not a storage one, and the next section explains why raising a quota will not touch it.

Why it happens

A mailbox has three storage thresholds and they fire in order. The warning quota tells the user to tidy up. The prohibit send quota stops them sending while mail still arrives. The prohibit send and receive quota is the one that bounces the people writing to them, and Microsoft’s own description of it is exactly that: Exchange stops the user sending, does not deliver new messages, and returns anything sent to the mailbox to the sender in a non-delivery report.

Each mailbox either carries its own values or inherits them from its database, and the inheritance flag is where most of the confusion starts. Microsoft is explicit that UseDatabaseQuotaDefaults has to be $false for custom quotas to override the database defaults. Set the numbers and leave the flag alone and nothing changes, which is why people conclude the quota is not the problem and go looking somewhere else.

The second family of limits is a rate, not a size, and no amount of storage touches it. Microsoft publishes two codes here with distinct meanings that are easy to swap. 5.2.121 is the recipient’s per hour message receive limit from a specific sender – one sender flooding one mailbox. 5.2.122 is the recipient’s per hour message receive limit across all senders. Microsoft’s stated purpose is to protect users from errant automated notification systems and single-sender mail storms, and its stated remedy is that the sending system should try again later and send fewer messages per hour. There is a report – Mailboxes exceeding receiving limits – that shows which mailboxes are on the receiving end.

And then there is the one that catches people out. In Exchange Online, Microsoft publishes 5.2.2 as Submission quota exceeded, and describes it as the sender exceeding the recipient rate limit or the message rate limit – possibly because the account has been compromised and is being used to send spam. A reader who takes 5.2.2 to mean a full recipient mailbox in a cloud tenant measures the wrong mailbox entirely.

The mailbox is genuinely over its storage quota

You have this one if StorageLimitStatus reports ProhibitSendReceive and TotalItemSize is at or above the prohibit send and receive value.

  1. Have the user empty Deleted Items and Junk Email and clear the largest items; sorting by size in Outlook finds them fastest.
  2. If the mailbox legitimately needs more room, set explicit quotas on it rather than raising the database defaults for everyone.
  3. Turn inheritance off in the same command as the new values, or they are ignored.
  4. Enable an archive mailbox and a retention policy so old mail moves out of the primary mailbox automatically instead of being deleted.

Recoverable Items is full while the mailbox looks small

You have this one if TotalItemSize is well below the quota but the mailbox still refuses mail, and the mailbox is on hold.

  1. Compare TotalDeletedItemSize with RecoverableItemsQuota.
  2. A mailbox on hold retains deleted items, so a high-churn mailbox fills the Recoverable Items folder without the user seeing anything.
  3. Raise RecoverableItemsQuota and RecoverableItemsWarningQuota, or review whether the hold still needs to be in place.

A per-hour receive limit fired, not a storage limit

You have this one if A 5.2.121 or 5.2.122 code, an unchanged mailbox size, and a burst of automated mail arriving at one address.

  1. Establish which of the two it is: 5.2.121 is one specific sender, 5.2.122 is everything arriving at that recipient.
  2. Find what is generating the burst – a monitoring system, ticketing integration or backup alert pointed at a single mailbox is the usual source.
  3. Rate-limit or batch at the sending application: digest the alerts, or spread them over time.
  4. Deliver bulk automated mail to a shared mailbox or a distribution group rather than to a person, so one recipient is not the bottleneck.

These caps are enforced by the service. Microsoft’s documented remedy is for the sender to slow down, not for an administrator to raise a number.

The database volume is out of space

You have this one if Many mailboxes on the same database start bouncing at once and free space on the volume is low or zero.

  1. Check free space on the database and log volumes before touching any quota.
  2. Clear transaction logs by taking a successful Exchange-aware backup, which truncates them. Do not delete log files by hand.
  3. Move mailboxes to a database on a volume with room, or extend the volume.
  4. Confirm the database is mounted and mailboxes report BelowLimit again.

A volume that fills completely dismounts the database, which turns a quota problem into an outage. Treat low free space as urgent rather than as housekeeping.

Full reference

The codes, and who each one is about

Code Published meaning Who it is about
552 5.2.2 (RFC class) The mailbox is full because a per-mailbox administrative quota or physical capacity was exceeded The recipient
5.2.2 (Exchange Online) Submission quota exceeded – the sender exceeded the recipient rate or message rate limit The sender
550 5.2.121 Recipient’s per hour message receive limit from specific sender exceeded One sender to one recipient
550 5.2.122 Recipient’s per hour message receive limit exceeded All senders to one recipient
452 4.2.2 Mailbox full, reported transiently so the sending server keeps retrying The recipient
550 5.3.3 Selected features specified for the message are not supported by the destination system The destination system

Two of those – 452 4.2.2 and 550 5.3.3 – are not published by Microsoft at all; the meanings above are the RFC class definitions. The practical difference between 552 and 452 is worth holding on to: a 552 is permanent and the sending queue has already given up, so the sender must send again, while a 452 stays queued and retries on its own.

The three quotas, and the flag that governs them

Setting What Exchange does at that size
IssueWarningQuota The user receives a warning message
ProhibitSendQuota The user cannot send; mail still arrives
ProhibitSendReceiveQuota The user cannot send and new mail is not delivered; senders get a non-delivery report
UseDatabaseQuotaDefaults $True means the database values apply. It must be $False for mailbox values to take effect

Reading the mailbox properly

Get-MailboxStatistics user@contoso.com |
  Format-List DisplayName,TotalItemSize,TotalDeletedItemSize,ItemCount,StorageLimitStatus

Get-Mailbox user@contoso.com |
  Format-List ProhibitSendQuota,ProhibitSendReceiveQuota,IssueWarningQuota,
              RecoverableItemsQuota,RecoverableItemsWarningQuota,UseDatabaseQuotaDefaults

TotalItemSize is what the user sees. TotalDeletedItemSize is the Recoverable Items folder, which the user cannot see and Outlook does not count in folder sizes. On a mailbox that is on hold, the second number is frequently the one that hit its limit, which is why the user insists their mailbox is nearly empty and is telling the truth.

Finding a rate limit rather than guessing at one

  • The Mailboxes exceeding receiving limits report shows which mailboxes are receiving large volumes in a short time. Start there rather than with the mailbox the user complained about.
  • Match the code first: 5.2.121 names a specific sender, so you are looking for one system; 5.2.122 does not, so you are looking at total inbound volume.
  • Check whether the sender is an application with a retry loop. A failing integration that retries every few seconds produces this within an hour.
  • Where the recipient is a person receiving machine-generated mail, move that traffic to a shared mailbox or a group and let the people who need it subscribe.

Do not set quotas to unlimited to make the bouncing stop. It moves the failure from one mailbox to the database volume, and a volume that fills dismounts the database and takes everybody offline. Set a limit you can support on the storage you actually have.

When it is the server rather than the mailbox

  1. Check free space on the database and log volumes first, before any quota change.
  2. Confirm Exchange-aware backups are running and truncating logs; a failed backup chain fills a log volume quietly over days.
  3. Look at the distribution of mailboxes across databases. Several very large databases on one volume is a capacity plan, not an accident.
  4. If you are planning to spread mailboxes across more, smaller databases, check the edition first – the number of databases a server may mount is an edition limit.

When a licence is the actual fix

Raising a quota costs nothing, and if that is all you need then stop there. The licensing question becomes real only when you keep running out of room because the server itself is out of capacity or out of databases. Exchange Server is licensed as a server licence plus client access licences, and the editions differ in how many mailbox databases a server may mount: Microsoft publishes five mounted databases for Standard and one hundred for Enterprise, with recovery databases excluded from the count. That is the constraint people hit when they try to spread mailboxes across more, smaller databases to keep each one manageable. Arco supplies Exchange Server Subscription Edition Standard licences and the matching client access licences, and can tell you whether your growth plan actually needs a different edition or simply more storage on the server you already own.

Every code this article covers

Code What it points at Source
552 5.2.2 Mailbox full: a per-mailbox administrative quota or physical capacity was exceeded. Note that Exchange Online publishes 5.2.2 as Submission quota exceeded, which is about the sender instead RFC 3463
550 5.2.121 Recipient’s per hour message receive limit from specific sender exceeded Microsoft Learn
550 5.2.122 Recipient’s per hour message receive limit exceeded, counted across all senders Microsoft Learn
452 4.2.2 The same mailbox-full condition reported transiently, so the sending server keeps retrying. Not published by Microsoft; this is the RFC 3463 class RFC 3463
550 5.3.3 Selected features specified for the message are not supported by the destination system. Not published by Microsoft; this is the RFC 3463 class RFC 3463

Confirm the fix worked

  1. Get-MailboxStatistics user | Format-List StorageLimitStatus reads BelowLimit.
  2. Get-Mailbox user | Format-List *Quota*,UseDatabaseQuotaDefaults shows the values you intended, with inheritance set the way you meant it.
  3. A test message from an external sender is accepted and shows a DELIVER event in the tracking log.
  4. TotalDeletedItemSize is comfortably below RecoverableItemsQuota on any mailbox that is on hold.
  5. Free space on the database and log volumes is above your alerting threshold.

Questions people ask about this

Should I just set the quota to unlimited?

No. Unlimited quotas move the failure from one mailbox to the whole database, and a database volume that fills dismounts and takes everyone offline. Set a limit you can support on the storage you have.

Does the sender need to do anything?

Once the recipient is under quota, the sender resends. A message bounced with 552 is gone from the sending queue and will not be retried, unlike a 452, which stays queued and retries on its own.

Why does Outlook show less data than the server reports?

Cached mode holds only part of the mailbox locally, and Recoverable Items and archive content are not counted in the folder sizes users see. Trust Get-MailboxStatistics over the client.

I got 5.2.2 from Exchange Online and the recipient’s mailbox is nearly empty. Why?

Because Microsoft publishes 5.2.2 in Exchange Online as Submission quota exceeded, which is about the sender exceeding a recipient rate or message rate limit. It can also indicate a compromised account being used to send spam, so check the sending account’s activity.

Can I raise the per-hour receive limits?

No. Those caps are enforced by the service and Microsoft’s documented remedy is for the sending system to try again later and send fewer messages per hour. Fix the sender.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Event ID 2153 and Event ID 4113: DAG database redundancy checks are failing Free Fix 550 5.7.509: your mail fails DMARC so the receiver rejects it outright Free Fix 451 4.4.0 DNS query failed: Exchange cannot resolve the next hop Free Fix Error 1618 and a half finished Exchange CU: setup will not start again
โ† Back to Knowledge Base