Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 452 4.2.2 The email account that you tried to reach is over quota | Exchange admin centre (EAC) > Mail flow > Message trace | -> Status=Pending or Failed |
| ProhibitSendReceiveQuota limit | 50 GB for Exchange Online Plan 2, 100 GB for Microsoft 365 E3 with archive enabled | Exchange admin centre (EAC) > Recipients > Mailboxes | -> Mailbox usage |
| Registry key or OMA-URI involved | None required as this is a configuration issue in Exchange Online | N/A | |
| Relevant service/endpoint URL | https://admin.exchange.microsoft.com | Exchange admin centre (EAC) | -> Mail flow > Message trace |
| Log line signature | 452 4.2.2 The email account that you tried to reach is over quota | Exchange Online PowerShell: Get-Mailbox -Identity <user> | Select-Object ProhibitSendReceiveQuota,TotalItemSize | |
Log Files to Check
C:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking\*.emlC:\Program Files\Microsoft\Exchange Server\V15\Logging\Protocol\*.log
What This Error Actually Means
The error code "452 4.2.2 The email account that you tried to reach is over quota" signifies a situation where the recipient's mailbox has exceeded its storage limit, preventing it from accepting new messages. This condition arises when an Exchange Online user's mailbox reaches their ProhibitSendReceiveQuota threshold, which is set by Microsoft or configured within your organization's tenant settings. The error is generated by the Exchange Online server and communicated back to the sending server as a Non-Delivery Report (NDR), indicating that the recipient's mailbox cannot accept any new messages until space is freed up.
Affected Versions and Scope
This issue affects all versions of Exchange Online and Microsoft 365 plans where mailboxes are provisioned. The error specifically targets users whose mailboxes have reached their ProhibitSendReceiveQuota limit, which can vary depending on the plan:
- For Exchange Online Plan 2, this limit is set at 50 GB.
- For Microsoft 365 E3 with archive enabled, it's increased to 100 GB.
It does not affect users who are below their quota limits or those in plans where the ProhibitSendReceiveQuota has been explicitly raised beyond these defaults. Additionally, this error is tenant-specific and will only occur if the mailbox size exceeds its configured limit within your organization’s Exchange Online environment.
Where To Look First: Logs and Event IDs
To diagnose an issue with the "452 4.2.2" error code, you should first check the following logs and event IDs:
- **Exchange Admin Centre (EAC) > Mail flow > Message trace**: This section will show messages that have been rejected due to a quota exceedance, displaying 'Status=Pending' or 'Status=Failed' with detail '452 4.2.2'.
- **Exchange Online PowerShell**: Use the command
Get-Mailbox -Identity <user> | Select-Object ProhibitSendReceiveQuota,TotalItemSize to retrieve information about the user's mailbox size and quota limits.
- **Event IDs**:
- Event ID 1074: This event is logged when a message delivery attempt fails due to a recipient’s mailbox being over its storage limit. It can be found in the
C:\Program Files\Microsoft\Exchange Server\V15\Logging\MessageTracking directory.
- Event ID 3286: This event indicates that an action has been taken on a user's mailbox due to reaching quota limits, such as disabling send/receive capabilities.
Root Causes
The root causes for the "452 4.2.2" error can be categorized into several distinct scenarios:
User Mailbox Size Exceeded Quota Limit
This is the most common cause where a user's mailbox has reached its ProhibitSendReceiveQuota limit, preventing it from accepting new messages. You can identify this by checking the user’s mailbox size and quota limits through the Exchange Admin Centre or PowerShell.
Online Archive Policy (MRM) Issues
If the online archive policy is no longer moving items to the archive due to a license change or archive being disabled, it can lead to the mailbox reaching its limit. This can be confirmed by reviewing the user's mailbox settings in the EAC and checking if their archive status has been altered.
Large Attachment Loops
A common issue is when large attachments are auto-forwarded repeatedly within a loop, filling up the mailbox quickly. You can identify this by searching for patterns of repeated large email messages sent back to the same user or group.
Fix Procedure
To resolve the "452 4.2.2" error and allow the recipient's mailbox to accept new messages again, follow these steps:
- Increase Mailbox Quota: Use PowerShell to increase the ProhibitSendReceiveQuota for the affected user.
Set-Mailbox -Identity <user> -ProhibitSendReceiveQuota 1024GB
This command will set a new limit, allowing more space in the mailbox. Note that this should be done cautiously and with consideration of your organization's policies.
- Enable Archive for User: If applicable, enable an archive to move older items out of the primary mailbox.
New-MailboxPlan -Name "MyArchivePlan" -ArchivingEnabled $true
Set-CalendarProcessing -Identity <user> -AddOrganizerToSubject $false
These commands create a new mailbox plan with archiving enabled and configure calendar processing to prevent unnecessary notifications.
- Review and Adjust Archive Policy: Ensure that the online archive policy is correctly configured and not preventing items from being moved.
Get-Mailbox -Identity <user> | Set-CalendarProcessing -AddOrganizerToSubject $false
Set-UserMailboxPolicy -Identity <user> -MailboxPolicy "MyArchivePlan"
These commands adjust the user's mailbox policy to ensure proper archiving.
- Remove Large Attachments: If large attachments are causing issues, manually remove them or configure transport rules to prevent their delivery.
New-TransportRule -Name "BlockLargeAttachments" -ConditionsAttachmentSizeGreaterThan 50MB -ActionsDeleteMessage
This command creates a new transport rule that blocks messages with attachments larger than 50 MB.
- Monitor and Clean Up: Regularly monitor mailbox sizes and clean up unnecessary items to prevent future quota issues.
Get-MailboxStatistics -Identity <user> | Select-Object TotalItemSize,ItemCount
This command retrieves the total size of items in a user's mailbox.
Be cautious when increasing mailbox quotas or enabling archives as it may affect performance and storage costs. Ensure that your organization’s policies are followed to prevent unintended consequences.
Error Code Variants
| Code | Description | Distinguishing Factors |
| 451 4.3.0 | The server is temporarily unable to service the request due to a transaction limit. | This error indicates temporary issues with message delivery, not permanent mailbox quota exceedance. |
| 421 4.7.0 | The mail system is busy or unavailable. | Different from "452 4.2.2" as it does not indicate a mailbox storage issue but rather a server availability problem. |
Verification
To verify that the fix has been applied successfully, check the following:
- **Exchange Admin Centre**: Navigate to
EAC > Recipients > Mailboxes, select the user's mailbox, and review their current storage usage against the quota limit.
- **PowerShell Verification**: Use the command
Get-Mailbox -Identity <user> | Select-Object ProhibitSendReceiveQuota,TotalItemSize
to confirm that the mailbox size is below its new or adjusted quota limit.
Prevention
To prevent recurrence of this issue:
- Implement regular monitoring and alerts for mailbox sizes approaching their limits.
- Configure transport rules to automatically move large attachments to archives or block them from delivery.
- Regularly review and adjust user quotas based on actual usage patterns and organizational needs.
- Educate users about best practices for managing email storage, such as archiving old items and deleting unnecessary emails.
By following these guidelines and implementing proactive measures, you can effectively manage mailbox sizes in Exchange Online and prevent issues like the "452 4.2.2" error from recurring.