A mailbox full bounce is a soft bounce. The recipient address is valid, but their inbox has hit its storage quota, so the mail server temporarily rejects your message. It usually returns an SMTP 4.2.2 code. The mailbox may free up, so retries often succeed within a few days.
What does a mailbox full bounce mean?
It means the recipient exists but cannot receive your email right now because their inbox is over its storage limit. The receiving server holds the address as active and returns a temporary failure. Your mail platform will usually retry for 24 to 72 hours before it gives up and logs a hard failure.
This is different from an invalid address, where the mailbox does not exist at all. Here the mailbox is real and the owner may still be active. Their account simply ran out of space, or a synced client has not cleared old mail yet. Consumer accounts on providers with tight storage caps and small business servers with strict per-user quotas trigger these bounces most often. The right first move is patience, followed by a decision about the address only if the problem repeats.
Why over-quota mailboxes soft bounce
Mail servers separate permanent failures from temporary ones on purpose. A permanent failure returns a 5xx code and tells the sender to stop. A temporary failure returns a 4xx code and tells the sender to hold the message and try again later. A full mailbox is temporary by nature. Space frees up when the user deletes messages or the provider expands the quota, so the server asks you to wait rather than reject you outright.
That retry behavior protects both sides. The sender does not lose a legitimate message over a short-term storage issue. The receiver does not permanently reject mail from a contact who did nothing wrong. Your sending platform queues the message and attempts redelivery on a schedule, usually backing off from minutes to hours across the retry window before it gives up. The exact schedule depends on your provider, but most run several attempts across the first two to three days. During that window there is nothing to fix on your end. The message is in flight, and the result depends on whether the recipient clears space in time.
How to read mailbox full bounce codes
Bounce messages carry two useful signals: the SMTP reply code and the enhanced status code. A leading 4 means temporary. A leading 5 means permanent. The enhanced code adds detail on the reason. Here are the ones you will see tied to a full mailbox.
| Code | Type | What it means |
|---|---|---|
| 452 | Temporary (soft) | Mailbox is out of storage space, try again later |
| 4.2.2 | Temporary (soft) | Enhanced status code for a full mailbox |
| 422 | Temporary (soft) | Recipient mailbox has exceeded its quota |
| 552 | Permanent (hard) | Quota exceeded and the server will not retry |
| 5.2.2 | Permanent (hard) | Enhanced code when a full mailbox is treated as permanent |
Do not act on the code alone. A single 452 is routine and self-healing. What matters is how often the same address returns one of these results. Log the reason code with each send so you can spot a mailbox that is full every time rather than just full today. That record is what turns a noisy soft bounce into a clear decision.
How should you handle a mailbox full bounce?
Let your platform run its automatic retries first. Do not remove the address after one soft bounce. Track how many campaigns bounce full for the same contact. If it clears, keep sending. If it stays full across several sends over two to three weeks, suppress the address so it stops dragging your bounce rate down.
- Confirm the bounce type. Check the code. A 4xx is soft, so no immediate action is needed.
- Let automatic retries run for the full 24 to 72 hour window before you judge the address.
- Tag the contact as a repeat soft bouncer if the same full-mailbox result comes back on two or more separate sends.
- Suppress the address after roughly three to four failed sends over two to three weeks. Persistent full usually means abandoned.
- Keep your overall bounce rate under 2%. Soft bounces that never clear still count against you at the mailbox providers.
Check your list right now, free
10 checks a day with no signup. 100 a day with just your email.
When a full mailbox turns into a hard bounce
A soft bounce does not stay soft forever. If the mailbox stays full past the retry window, your platform stops trying and marks the message as failed. Some servers skip the wait and return a permanent 552 right away when a quota has been exceeded for a long time. At that point the address behaves like any hard bounce, and repeated hard bounces are what damage your sender reputation. Mailbox providers read a rising bounce rate as a sign of a stale or purchased list.
Watch for the pattern, not the single event. One full mailbox is noise. The same address bouncing full across a month is a signal that the account is abandoned. Abandoned accounts often turn into spam traps later, and a recycled trap hit costs you far more than one suppressed contact ever would.
How do you prevent mailbox full bounces?
You cannot control a recipient's storage, but you can stop mailing addresses that are already dead. Verify every list before you import it, remove contacts that have not opened in six months or more, and re-verify older segments before a big send. Clean lists keep soft bounces rare and your reputation intact.
A quick pre-send checklist
Run each import through the free verifier before it reaches your sending tool. Drop contacts with no opens in six months. Re-verify older segments ahead of any large campaign. Keep suppression lists current so retired addresses never sneak back in. These four habits keep full-mailbox bounces rare and easy to absorb when they do happen.
Full mailboxes will always happen on a healthy list, and a small number is normal. The goal is not zero soft bounces. The goal is a list where full-mailbox results clear on retry instead of piling up as permanent failures. Verify early, retry patiently, suppress the addresses that never recover, and your bounce rate stays where inbox providers want it.