Mailbox Full Bounce: What the Error Means and What to Do
A mailbox full bounce is usually a soft failure, but the same words can appear in a permanent one. Here is how to read the codes, when to retry and when to suppress.

TL;DR
- A mailbox full bounce means the recipient's mailbox is over its storage quota and cannot accept new mail.
- It is normally a soft bounce, shown as a
4.2.2code. The same condition can also appear as a permanent5.2.2code. - Retry a few times over a few days. If it keeps failing, suppress the address.
- Do not keep mailing a full mailbox. Repeated failures can hurt your sender reputation.
What is a mailbox full bounce?#
A mailbox full bounce happens when the receiving server accepts your connection but cannot store the message, because the recipient has used up their storage. Most providers give each mailbox a quota. When the quota is reached, new messages are refused until the owner frees space.
The bounce message usually says something like "mailbox full", "over quota" or "insufficient storage". It comes from the recipient's server, not from your mail software.
The codes behind a mailbox full bounce#
SMTP uses enhanced status codes from RFC 3463. In that system, the X.2.2 code means mailbox full. The first digit decides how the failure is treated.
| Code | Type | Meaning |
|---|---|---|
| 4.2.2 | Persistent transient (soft) | Mailbox full, try again later |
| 5.2.2 | Permanent (hard) | Mailbox full, the server will not retry |
| 552 | Basic SMTP reply | Storage allocation exceeded, as defined in RFC 5321 |
| 452 | Basic SMTP reply | Insufficient system storage, a temporary condition |
Providers word these differently and choose their own codes. Some return a permanent code for a mailbox that is full, so read the message text, not only the number.
Our guide to email bounce codes lists other common codes, and shows how to tell soft bounces from hard ones.
Why mailboxes get full#
- The person stopped using the account but never closed it.
- A free account has a small quota that fills with attachments.
- A shared or role address, such as
info@, receives mail nobody clears. - An old employee mailbox remains active after they leave.
That last reason matters for B2B outreach. A full mailbox is often a sign that the address is no longer read.
Should you retry a full mailbox?#
Yes, but only a few times. Most mail servers already retry a soft bounce for some time before reporting failure. After that, the decision is yours.
- First failure: let your sending platform retry automatically.
- Second or third failure: wait a few days and try once more.
- Still full: suppress the address and move on.
For a hard-coded 5.2.2, many platforms treat the address as undeliverable at once. Follow your platform's rule, but do not loop on the same address.
How a mailbox full bounce affects your reputation#
Bounces tell mailbox providers how well you maintain your list. A few soft bounces are normal. A large share of failures from the same list says you are mailing without checking addresses. Over time that can lower your standing with providers and push more of your mail to spam. Read more in our guide to sender reputation.
How to reduce full mailbox bounces#
- Verify addresses before sending. An email verifier can flag mailboxes that cannot accept mail. Some verifiers report a full mailbox directly.
- Clean old lists. Contacts go stale. Re-verify any list older than a few months.
- Suppress repeat failures. Add addresses to a suppression list after repeated soft bounces.
- Watch role addresses. Prefer named contacts over shared inboxes.
- Find a fresh contact. If a person has left, look for their replacement with a domain search.
What to do if your own mailbox is full#
If you are the one receiving the bounce on your side, free space fast. Delete large attachments, empty the trash and spam folders, and archive old mail. Check your storage plan. Until space is free, senders will see bounces and may give up on you.
How to read the bounce message#
Open the full bounce, not just the subject line. Look for three things. First, the status code, such as 4.2.2 or 5.2.2. Second, the text, which often says "over quota" or "mailbox full". Third, the name of the server that sent it, which tells you whether the problem sits with the recipient's provider or with a company mail system. A bounce from a company server about a full mailbox often points to a forgotten account. A bounce from a large free provider often points to a user who simply never clears their inbox. In both cases, your next step is the same: limit retries, then stop. Log each case so you can see patterns.
FAQ#
Is a mailbox full bounce a hard or soft bounce?#
Usually soft. A 4.2.2 code signals a temporary condition. Some servers use a hard code for the same problem.
How many times should I retry?#
A few attempts over several days is common. After that, suppress the address.
Does a full mailbox mean the email is invalid?#
Not exactly. The address exists, but it may no longer be monitored.
Will bounces hurt deliverability?#
Frequent bounces can, especially when they come from a poorly maintained list.
Can a verifier detect a full mailbox?#
Some can, but not always. A mailbox check depends on how the receiving server answers.
Keep your list clean#
Check your list before the next send. Tomba's email verifier helps you remove addresses that are likely to bounce.
// start free
See who Tomba finds at any company
Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.
Free plan · No credit card required · GDPR & CCPA
// about the author