The 552 5.2.2 error means the recipient’s mailbox is full — storage quota exhausted, unable to accept new messages.
Fix it by notifying the recipient through alternate channels to clear space. As the sender, you can reduce attachment size or send links instead, but the core problem requires action from the recipient.
Unlike addressing errors (where the address is wrong) or authentication errors (where your configuration is wrong), 552 5.2.2 indicates a recipient-side problem you cannot directly fix.
Your email is valid, properly authenticated, and accepted by the receiving server — the individual mailbox simply has no room.
Quick skim — 552 5.2.2 error overview
The 552 5.2.2 error indicates recipient storage exhaustion rather than sender issues.
| Attribute | Details |
| Error code | 552 5.2.2 |
| Category | Mailbox state/quota |
| Meaning | Recipient’s mailbox cannot accept messages (full) |
| Severity | Temporary (resolves when the recipient clears the space) |
| Common causes | Inbox neglect, large attachments accumulation, and retention policies |
| Fix approach | Notify recipient → reduce payload → retry later |
What does mailbox over quota mean?
Email providers allocate storage per mailbox. When usage reaches the limit, new messages bounce with 552 5.2.2.
Common storage limits are:
| Provider | Free Tier | Paid Tier |
| Gmail | 15 GB (shared with Drive) | 30 GB+, depending on plan |
| Outlook.com | 15 GB | 50 GB+ with Microsoft 365 |
| Yahoo Mail | 1 TB | — |
| Exchange Online | — | 50-100 GB depending on plan |
Here’s what consumes quota most:
- Archived messages
- Calendar attachments (some systems)
- Emails with attachments (particularly large files)
- Trash and spam folders (count until permanently deleted)
A single email with a 25 MB attachment consumes 25 MB of quota. Accumulation is faster than most users realize.
Why does the 552 5.2.2 error occur?
Quota exhaustion happens gradually, then suddenly blocks all incoming mail.
Inbox neglect
Recipients who rarely delete messages accumulate years of email. Large inboxes eventually hit limits.
Large attachments
Frequent receipt of files (photos, documents, videos) fills quota faster than text-only correspondence.
Trash not emptied
Deleted messages move to Trash but still count toward quota until permanently deleted (usually 30 days auto-empty, but not always).
Retention policies
Organizations sometimes apply retention holds that prevent deletion, filling mailboxes with messages users can’t remove.
Forwarding loops
Misconfigured forwarding to another full mailbox can cause the original mailbox to receive bounces, further consuming quota.
How do you fix 552 5.2.2?
Your fix depends on whether you’re the sender (limited options) or recipient (full control).
For recipients
If you’re receiving this bounce for your own mailbox (someone trying to reach you):
Delete unnecessary emails
Start with large messages:
- Search for messages with attachments
- Sort by size in the email client
- Remove old newsletters and notifications
- Delete duplicate files
Empty trash and spam
Deleted items count until permanently removed:
- Empty Trash folder
- Empty Spam folder
- Permanently delete rather than just delete
Archive to external storage
For messages you need to keep:
- Download attachments to local storage
- Export to backup service
- Delete originals after backup
Increase quota
If available:
- Upgrade email plan
- Request quota increase from IT (enterprise)
- Purchase additional storage
Check retention holds
For enterprise accounts:
- Contact IT about litigation holds
- Request removal if no longer needed
- Understand compliance requirements
For senders
You cannot fix the recipient’s quota problem, but you can work around it:
Reduce attachment size
Make your message smaller:
- Compress files before attaching
- Use cloud links instead (Google Drive, OneDrive, Dropbox)
- Send only essential files
Cloud links don’t consume recipient quota — files stay on your storage.
Notify via alternate channel
Contact the recipient to alert them:
- Phone call
- Text message
- LinkedIn message
- Secondary email address
Let them know their inbox is full and your message is waiting.
Retry strategically
If the message isn’t urgent:
- Wait 24-72 hours (recipient may clear space)
- Retry once or twice
- Don’t hammer with repeated attempts (can affect your sender reputation)
Accept the bounce
For marketing or bulk mail:
- Log the bounce
- Skip retries for this recipient
- Try next campaign again (they may have cleared space)
How do you handle persistent quota bounces?
Repeated 552 5.2.2 errors from the same recipient indicate chronic neglect — treat differently from one-time occurrences.
For important contacts
Escalate outreach:
- Call directly
- Send physical mail
- Contact through colleagues
For marketing lists
Consider suppression:
- Repeated quota bounces signal inactive accounts
- Continuing to send wastes resources
- Temporary suppression (90 days), then retry
Monitor bounce rates
Track 552 5.2.2 bounces separately from hard bounces:
- Quota bounces are technically soft bounces (temporary)
- But chronic quota bounces behave like hard bounces
- High rates affect deliverability metrics
Still stuck after trying the fix?
Some email errors are easy to clear. Others point to deeper deliverability issues involving authentication, sender reputation, blacklisting, routing, or mailbox provider policy. If you would rather have an expert review it, speak with an email delieverability consultant for free and we can help diagnose the issue and fix it on your behalf.
We look beyond the error message itself to find what is actually breaking delivery, trust, or inbox placement.
From SPF, DKIM, and DMARC to blacklist cleanup, DNS alignment, and sending setup, we can guide or implement the fix.
We assess whether the error is part of a bigger pattern hurting opens, replies, and overall campaign performance.
Talk to a real deliverability expert, get honest guidance, and see the next best step without pressure or upsells.
When should you book a consultation? If the error keeps coming back, affects multiple mailboxes or domains, started after an ESP or DNS change, or is tied to spam placement, low inboxing, high bounce rates, or authentication failures, it is usually faster to get an expert involved early.
Frequently asked questions
Here are some commonly asked questions about this error:
Technically soft — the address is valid, and delivery will succeed once space is cleared. However, if the recipient never clears space, it behaves like a hard bounce. Most email platforms classify persistent quota bounces as hard after multiple failures.
Initial retry: 24-48 hours (reasonable time for the recipient to notice and clear space). If that fails, wait 1 week. After 2-3 failures over 2-3 weeks, suppress the address and try alternate contact methods.
Often yes. Gmail shares quota with Google Drive and Photos. Exchange Online may share with OneDrive. Recipients with full mailboxes may also have trouble with other cloud storage.
You can suggest it, but you can’t do it for them. Enterprise users should contact their IT department. Free account users can upgrade to paid plans or delete existing messages.
