Mailbox Full and Bouncing Inbound Mail? Managing Email Storage the Right Way
Your mailbox hit quota and senders got a 552 bounce. Here's how to diagnose, archive vs delete, set retention, and plan storage so it doesn't happen again.
Your mailbox hit quota and senders got a 552 bounce. Here's how to diagnose, archive vs delete, set retention, and plan storage so it doesn't happen again.
The email that could have saved the deal never arrived. Not in spam. Not delayed. Just... bounced.
I found out three days later when the sender forwarded me their bounce notification. "552 5.2.2 Mailbox full — user quota exceeded." My mailbox had been silently rejecting inbound mail for 72 hours. No warning. No notification to me. Just a wall that senders hit and I never knew existed.
Felt like an idiot. I'd been complaining about "slow email" all week. (Turns out the email wasn't slow — it was bouncing at the door. Classic.)
A full mailbox doesn't queue your mail somewhere waiting for space. It rejects incoming messages outright. The sender gets a bounce. You get nothing. And unless they tell you about the bounce — or you notice nobody's emailing you anymore — you won't know there's a problem.
This is one of those issues that hits everyone eventually. Doesn't matter if you're on Google Workspace, Microsoft 365, Zoho, or any other provider. Quotas exist. Storage fills up. And when it does, the failure mode is surprisingly brutal — similar to how email deliverability failures silently tank your campaigns without warning.
Here's how to diagnose it, clean it up fast, and set things up so it doesn't happen again.
By the end of this, you'll know how to check your current mailbox quota, identify what's eating storage, clear space quickly without losing important mail, and set up retention policies to prevent future quota emergencies. You'll also understand how 552 bounces work so you know exactly what happens when your mailbox hits the wall.
Before you start deleting things, make sure quota is the actual problem. A mailbox can stop receiving mail for other reasons — DNS issues, authentication problems, server outages.
Check your quota status:
If you're at 95%+ capacity, you're in the danger zone. Some servers start rejecting mail at 90% to leave buffer for system mail. If you're running ad campaigns, this becomes especially critical — a missed lead notification while running Google Ads click fraud protection means wasted spend with no recovery.
The thing most people miss: storage isn't just your Inbox. It's every folder — Sent, Drafts, Trash, Spam, and any custom folders. Trash alone can hold gigabytes if you delete but never empty.
Open your mailbox in an IMAP client. Thunderbird is my go-to for this because it makes sorting by size dead simple, and it's free.
The fast audit:
In my experience, the breakdown for most bloated mailboxes looks like this:
| Folder | Typical % of Usage |
|---|---|
| Sent (attachments) | 30-40% |
| Inbox (attachments) | 20-30% |
| Trash (unflushed) | 10-20% |
| Spam | 5-10% |
| Newsletters/notifications | 10-15% |
That Sent folder stat surprises people. Myself included — I genuinely thought I was being smart by "not keeping attachments in my inbox." Joke's on me: every file I emailed lived in Sent. You replied to that email with the same attachment quoted? Another copy. Reply chains with embedded images balloon fast.
Not everything should go in the trash. But not everything needs to be kept either.
Delete without regret:
Archive before deleting:
How to archive locally:
In Thunderbird, select emails → right-click → Save As → choose a local folder. In Outlook, File → Open & Export → Import/Export → Export to a file. In Apple Mail, drag emails to a local folder outside IMAP.
You can also use Google Takeout for Gmail (exports entire mailbox as mbox) or Microsoft's export tool for Outlook.com.
Local archives don't count against server quota. And if you need the email later, you can search your archive or re-upload it. For teams using browser-based workflows, keeping local email archives organized alongside your browser profiles prevents context-switching chaos.
Once you've decided what's deletable, here's how to clear it fast.
In Thunderbird:
In Outlook:
In Gmail:
Gmail doesn't have native sort-by-size in the web interface. Use the search operator larger:10M to find emails over 10MB. larger:5M for 5MB+. Delete from search results.
For newsletters: search from:newsletter@ or unsubscribe to find bulk mail, then mass delete.
Important: After deleting, most IMAP clients need to "compact" or "expunge" the folder to actually free space on the server. In Thunderbird: File → Compact Folders. In Outlook it's automatic. In webmail, usually automatic on logout.
Don't skip the Trash empty step. I know, obvious. But I've done it. Deleted mail sits in Trash until purged — that's your safety net for accidental deletes. But if you're cleaning up 2GB, that 2GB moves to Trash and still counts against quota until you empty it. Ask me how I know.
Cleaning up once is fine. Cleaning up every three months because you're at quota again? That's a workflow problem.
Server-side retention (if your provider supports it):
Some providers let you auto-delete mail older than X days. This is aggressive — make sure you're okay with automatic deletion before enabling.
mail_plugins with expire plugin and set per-folder retentionClient-side retention:
If your provider doesn't offer server-side retention, you can use IMAP client rules:
In Thunderbird:
This moves old mail to a local folder or deletes it, reducing server storage.
Smart folder rules:
I run a filter that moves any email over 5MB out of my server mailbox and into a local archive within 30 days. Keeps server storage lean. I can still search locally when I need old attachments. If you're tracking email performance alongside other metrics, unified analytics dashboards help you spot patterns across all your tools.
Once you're out of the immediate crisis, think about storage as an ongoing resource.
Understand what you actually need:
Example math:
50 emails/day × 100KB average × 365 days = ~1.8GB/year of accumulation. If you're on a 10GB quota, you've got about 5 years before you're in trouble — assuming you never delete anything.
But throw in a few 20MB attachments per week and that math changes fast.
Platform considerations:
On JustEmails, you start with 10GB storage for $49/year. If you need more, storage adds at $100/year per 100GB block. No per-mailbox limits — it's pooled across your account. Good for agencies or multi-domain setups where one mailbox might need 15GB and another uses 500MB.
Google Workspace Business Starter gives 30GB per user shared with Drive. Microsoft 365 Business Basic gives 50GB per mailbox. Per-user pricing means storage scales automatically as you add seats — but so does cost.
The real question: do you need lots of storage per mailbox, or lots of mailboxes with modest storage? I'll be honest — if you're running a single inbox, per-user pricing probably works fine. But if you're juggling 10+ domains? Flat-fee wins. Flat-fee vs per-mailbox pricing models shape this decision more than most people realize.
"552 5.2.2 Mailbox full" / "Over quota"
Cause: Recipient mailbox has no space. Server rejects delivery. Fix: Recipient (you) needs to clear storage. Sender should retry after you confirm cleanup.
"452 4.2.2 Mailbox full — try again later"
Cause: Soft failure — the server is suggesting retry. Some servers use this instead of 552. Fix: Same as above. Clear space, sender retries. The difference is 452 is a temp failure (server might accept later) while 552 is permanent (won't accept until space exists).
Quota shows space available but mail still bouncing
Cause: Could be per-folder limits (some systems cap individual folders), or cached quota data that hasn't updated. Also check if Trash/Spam are counted differently. Fix: Empty Trash/Spam, wait 15 minutes for quota to refresh, test again. If still failing, contact your provider.
Deleted emails but quota didn't change
Cause: IMAP requires "expunge" to actually remove deleted mail from server. Some clients mark as deleted but don't expunge immediately. Fix: In Thunderbird, File → Compact Folders. In other clients, look for "Purge deleted items" or "Compact." Or empty Trash folder — that usually forces an expunge.
Client says "folder full" but quota isn't maxed
Cause: Some IMAP servers have per-folder message count limits (not size limits). Rare, but old Dovecot configs sometimes have this. Fix: Move messages to subfolders or archive locally. Or contact provider to increase folder limits.
Now that your mailbox is breathing again:
Email storage management isn't glamorous. But a mailbox that silently bounces inbound mail is a business problem disguised as a technical one. Clients don't know you didn't get their email. They just think you're ignoring them.
Fix the quota. Set up retention. And maybe — just maybe — you won't have to explain a 72-hour silence to a client who thought you were ghosting them.
The receiving mail server rejects the message with a 552 bounce — typically "552 5.2.2 Mailbox full" or "Over quota." The sender gets a bounce-back notification saying delivery failed. Your mail server never accepts the message, so it doesn't queue anywhere waiting for space. It's gone unless the sender retries after you clear storage. This is different from spam filtering — there's no "full mailbox" folder to check later.
Sort your inbox by size in any IMAP client — Thunderbird, Outlook, Apple Mail all support this. Look for emails with large attachments: PDFs, images, zip files. Check your Sent folder too — attachments you sent count against your quota. Also check Trash and Spam folders, which often hold deleted mail until manually emptied. In many cases, 60-70% of mailbox bloat is attachments in Sent and unflushed Trash.
Depends on whether you need the content later. Archive if you might need the emails for compliance, reference, or legal reasons — export to local storage or a backup service. Delete if it's genuinely disposable: newsletters, automated notifications, marketing emails. Most people accumulate years of notification spam that can safely go. Archive anything with attachments you might need; delete the rest.
Some email providers support retention policies that auto-delete mail older than a set period (30 days, 90 days, etc.). IMAP clients like Thunderbird let you set folder-specific retention rules locally. If your provider doesn't offer server-side retention, you can use client-side rules to move old mail to a local folder and delete from server. Be careful with auto-delete on important folders — a 30-day retention on your main inbox means any email you don't act on within a month disappears.
Unlimited custom domain email hosting for $49/year flat — unlimited domains, unlimited mailboxes, 10 GB storage, full IMAP/SMTP. Built for agencies, freelancers, and anyone managing email across more than one domain.