Article
452 4.2.2 Mailbox Full Bounce: What It Means and What to Do
By Unlimited Verifier Team ·

Summary
A 452 4.2.2 bounce means the recipient's mailbox was over its storage quota at delivery time. It is a temporary soft bounce, so the sending server should keep retrying rather than treating the address as invalid. Hold addresses that keep deferring, and suppress only those that stay full for weeks with no engagement.A 452 4.2.2 bounce means the recipient's mailbox is over its storage quota right now, so it is a temporary soft bounce to retry, not proof of an invalid address. Let the sending server retry, verify the affected addresses before any bulk resend, and suppress only addresses that keep deferring and never engage. For the verification step, Unlimited Verifier is our top pick, because standard verification is unlimited on every plan, including Free, so repeat passes don't add per-email cost.
This guide is for marketers, list owners, agencies and SaaS teams who see 452 4.2.2 in ESP reports or delivery logs and need to decide what to delete, what to hold and what to fix. If you're new to codes, start with our complete guide to email bounce codes.
Quick answer
- What it means: The recipient's mailbox was full at delivery time. The leading 4 marks a temporary failure, and 4.2.2 is the enhanced code for "mailbox full."
- What to do first: Let the sending server retry for several days. Don't delete an address after one deferral.
- When to hold: Three deferrals spanning at least seven days.
- When to suppress: Still deferring after 30 days, with no opens or clicks in 90 days (use 180 days for B2B lists with long buying cycles).
- Don't confuse it with: 552 5.2.2, which is a permanent mailbox-full failure, and 452 4.3.1, which is a server-wide storage problem.
What does 452 4.2.2 mean, and does it hurt your reputation?
The 452 reply code is a transient negative response, meaning "try again later." The enhanced code 4.2.2 is defined in RFC 3463 as mailbox full, and it applies to one recipient. A 4.2.2 says nothing about your list quality on its own.
Mailbox providers generally weigh hard bounces and spam complaints more heavily than soft deferrals. Repeated attempts to dead addresses still waste sends and signal weak hygiene over time, which is why the handling below matters even though the code is temporary.
Bottom line: a 452 4.2.2 is a per-recipient, temporary condition. It becomes a list problem only when it repeats without resolution.
How we compared (and limitations)
We judged each fix against the criteria that matter when a soft bounce is hitting real subscribers:
- Risk of wrongful suppression. Does the step avoid dropping readers whose mailboxes were only briefly full?
- Speed of action. How quickly can the step change what you send?
- Cost. Does it add per-message or per-check charges? For how to weigh these models, see email verification pricing.
- Data required. Does it need bounce logs, engagement data or only the bounce report?
- Effort. Can a non-developer run it each week?
Limitations. This comparison draws on public documentation, the relevant IETF standards and vendor-published information. We have not run controlled bounce experiments or measured results from a live sending program. The thresholds in this article are reasoned starting rules, not published industry standards, so tune them to your own data. Vendor figures, including Unlimited Verifier's stated 99.5% accuracy for deep verification, are the vendors' own claims. Test any verifier on a sample of your list before relying on it. For a structured checklist, see how to choose an email verifier.
Bottom line: treat every threshold here as a default to calibrate, not a rule the industry has agreed on.
What are the best ways to handle 452 4.2.2 bounces?
The strongest approach combines a verification pass, the sending server's retry logic and an engagement check. No single step tells you whether a full mailbox will clear, so the decision rests on how the address behaves over time.
Quick picks
- Best overall: Verify the cohort before resending, with Unlimited Verifier.
- Best for zero cost: Let the sending server retry, and read the codes yourself.
- Best for large lists: A written consecutive-bounce rule, so suppression is consistent.
- Best for provider-level problems: Watch for domain-wide 4.2.2 patterns.
- Best for prevention: A sunset and re-permission policy.
| Approach | Cost | Time to act | Best for |
|---|---|---|---|
| Verify the cohort before resending (Unlimited Verifier) | Free, or Pro at $29/mo ($25/mo billed annually) | Minutes per file | Bulk resends and cleanup passes |
| Let the sending server retry | Included in your sending setup | Several days | Every soft bounce |
| Read the DSN and confirm the code | Free | Minutes | Triage and reporting |
| Consecutive-bounce suppression rule | Varies by ESP | One-time setup | Automated hold and suppress |
| Engagement check | Varies by ESP | Weekly | Deciding who is worth retrying |
| Domain-pattern review | Free (log review) | Weekly | Spotting provider issues |
| Alternate channel for notices | Varies | Ongoing | Reaching people you can't email |
| Sunset and re-permission policy | Varies | Quarterly | Preventing recurrence |
Bottom line: verify, retry, then suppress on evidence. Never act on a single 452.
What are the eight fixes for a 452 4.2.2 cohort, ranked?
1. Verify the cohort before resending (Unlimited Verifier, top pick)
Verification answers the question a bulk resend depends on: is this a real address on a domain that accepts mail? Unlimited Verifier runs syntax, domain, MX and SMTP mailbox checks, detects catch-all domains, flags disposable and role-based addresses, and sorts every address into Valid, Risky or Invalid.
Key features
- CSV or Excel upload up to 10MB, with automatic email-column detection.
- Results exported as CSV, Excel or JSON.
- Deep verifications for the Risky group, and an API on Pro for batches of up to 10,000 emails per request.
Pros
- Standard verification is unlimited on every plan, so re-checking a cohort after a retry window adds no per-email cost.
- Risky is its own bucket, so catch-alls aren't forced into either "send" or "delete."
Cons
- Verification can't tell you whether a full mailbox will clear next week. A Risky or deferred result is a hold, not proof the address is dead.
- No native ESP, CRM or Zapier integrations, so you export, verify and re-import, or call the API.
Best for: repeatable cleanup passes on cohorts of any size.
Where it falls short: catch-all domains accept mail for any address, so a catch-all result can't confirm a specific mailbox. See catch-all email verification for how that case is handled.
Pricing: Free ($0) includes 25 lists a month of up to 150 emails each, plus 750 deep verifications. Pro is $29/month, or $25/month billed annually, and includes lists of up to 25,000 emails each and 25,000 deep verifications a month.
Worked example. A cohort of 1,850 addresses deferred with 452 4.2.2 during a cleanup window.
- On Free: 1,850 ÷ 150 = 12.33, so 13 lists. That fits the 25-list monthly allowance. If 400 come back Risky, that's 400 deep verifications, well within 750.
- On Pro: the same 1,850 addresses fit in one upload, far below the 25,000-per-list limit.
- Retention: Free results are kept 24 hours and Pro results 30 days, so export and save the files the same day.
Unlimited Verifier states 99.5% accuracy for deep verification. That is the vendor's figure, so check it against your own bounce history.
Bottom line: verify before a bulk resend, and treat Risky as a hold list, not a delete list.
2. Let the sending server retry
A 452 is transient. A well-behaved sending server queues the message and retries it rather than dropping it. RFC 5321 suggests retry intervals of at least 30 minutes and retries over a period of several days, roughly four to five, before giving up. Your ESP's exact schedule will differ, so check its documentation.
Key features
- Automatic requeue on 4xx replies.
- Retries stop when the message delivers or the give-up window closes.
Pros
- Requires no manual work, and many deferrals clear once the recipient archives mail.
- Keeps you from making a judgment before the retry window has run.
Cons
- Retries do nothing for a dormant mailbox that stays full until the give-up time, then returns as undeliverable.
- Manually resending the campaign to the cohort adds load to a full mailbox and makes your sending pattern look erratic.
Best for: every soft bounce, as the default behavior.
Where it falls short: it can't distinguish a temporarily full mailbox from an abandoned one.
Pricing: included in your sending setup, with no separate charge.
Tip: if you're also seeing other soft bounces, compare them against our list of common soft bounce reasons. For the temporary-versus-permanent distinction, see 4xx vs 5xx SMTP errors and 421 4.7.0 try again later.
Bottom line: let the queue do its job, then judge what's still failing when the window closes.
3. Read the DSN and confirm the code
A bounce report is a Delivery Status Notification, and RFC 3464 defines its format. The Status and Diagnostic-Code fields show what happened. Confirm the enhanced code before acting, because similar-looking codes call for different responses.
Key features
- Reads the enhanced code (for example, 4.2.2) rather than the wording.
- Classifies the first digit: 4 is temporary, 5 is permanent.
Pros
- Prevents the most common triage error: treating a provider storage problem as a list problem.
- Costs nothing and takes minutes.
Cons
- DSN wording varies by receiving server, and some ESP dashboards show only a summary.
- The code tells you the failure type, not how much space is left in the mailbox.
Best for: triage before you change any list.
Where it falls short: it can't diagnose capacity or predict whether a mailbox will clear.
Pricing: free.
Code distinctions:
- 4.2.2: mailbox full for one user, temporary. Retry and monitor.
- 4.3.1: the receiving system's storage is full. Don't suppress your list over it.
- 552 5.2.2: mailbox full, permanent. Many senders suppress these.
- 550 5.1.1: unknown user, permanent. See 550 5.1.1 user unknown.
For a full lookup, see our enhanced SMTP status codes list. If the bounce came from a Microsoft 365 mailbox, check Office 365 NDR bounce codes, since the wording differs.
Bottom line: confirm the code is per-user 4.2.2 before treating it as a list problem.
4. Set a consecutive-bounce suppression rule
Manual judgment doesn't scale, but a written rule does. Our suggested starting rules are:
- Hold: three deferrals spanning at least seven days.
- Suppress: still deferring 30 days after the first deferral, with no opens or clicks in 90 days.
Key features
- Two thresholds, one for hold and one for suppress.
- Requires counting deferrals per address, which means logging them yourself if your ESP doesn't expose soft-bounce counts.
Pros
- Produces the same decision for every address, so the list is easy to audit.
- Scales to large lists without reviewing each bounce.
Cons
- Written as "any soft bounce means suppress," it removes people whose mailboxes were only briefly full.
- Many ESPs don't surface per-address soft-bounce history, so the rule may need a spreadsheet or database to run.
Best for: large lists where hand review is impractical.
Where it falls short: the thresholds are defaults. A monthly sender needs longer windows than a daily one.
Pricing: free to set up in a spreadsheet or your own data; cost depends on your ESP.
Worked example. An address defers on Monday, Wednesday and Friday of one week. That's three deferrals, but they span only four days, so it isn't on hold yet. It defers again the following Monday. Now there are four deferrals spanning seven days, so it moves to hold. If it still hasn't cleared 30 days after the first deferral, and has no opens or clicks in 90 days, it's suppressed.
Bottom line: three spread-out deferrals signal hold; 30 days of deferral plus silence signals suppress.
5. Check engagement before you retry
A full mailbox often belongs to someone who doesn't read mail. Engagement is one of the best signals you have for whether a cohort is worth more sends, though it isn't proof of abandonment on its own.
Key features
- Opens and clicks for each deferred address over a fixed window.
- Clicks weighted above opens, because Apple Mail Privacy Protection and similar features can inflate open counts.
Pros
- Directly answers "is anyone reading this?"
- Lets you retry the engaged and suppress the silent without guessing.
Cons
- Only as reliable as your tracking, which varies by client and by mail setup.
- A deferred address that has been silent isn't necessarily abandoned. The person may read mail elsewhere or the mailbox may be an archive.
Best for: deciding which deferred addresses deserve another send.
Where it falls short: monthly or quarterly senders have sparse engagement history, so a 90-day silence means less when you only mail a few times a year. Extend the window for them.
Pricing: free, using data your ESP already holds.
Tip: for consumer lists, a 90-day window is a common starting point. For B2B lists, 180 days is more forgiving.
Bottom line: a deferred address that opened last week is worth holding; one silent for six months is a suppression candidate.
6. Spot domain-wide patterns
A single 4.2.2 is one person. Hundreds of 4.2.2 bounces at one domain in a single send is a pattern, and it calls for a different response.
Key features
- Groups deferrals by recipient domain and sorts by count.
- Compares timing, to see whether many addresses deferred in the same window.
Pros
- Separates a provider or company-policy issue from a list-quality issue.
- Prevents you from suppressing an entire organization because its mail system is under strain.
Cons
- You can't see the provider's quota settings, so domain patterns are clues, not diagnoses.
- Google's help documentation lists 15 GB of free storage shared across Gmail, Google Drive and Google Photos, so consumer Gmail boxes fill for reasons unrelated to your list.
Best for: finding whether a problem is your list, a provider or a mailbox policy.
Where it falls short: a spike can resolve on its own, so waiting a cycle is often more useful than escalating.
Pricing: free, using your existing logs.
Tip: for Gmail-side reputation, Google Postmaster Tools shows what Google sees from your sending domain.
Bottom line: group by domain before deciding anything about individual addresses.
7. Reach people through another channel
You can't tell a full-mailbox subscriber about the problem by email, because the message will defer too. Plan for other channels in advance.
Key features
- An account notice on your site or app.
- A preference-center prompt asking the subscriber to update their address.
- A request for a second contact address at signup.
Pros
- Reaches the people who matter most, even when email can't.
- Can recover a paying customer who would otherwise churn silently.
Cons
- Most of a typical list will have no alternate channel, so this step is for a small set of valuable addresses.
- Requires a product or website surface you control.
Best for: high-value subscribers and paying customers.
Where it falls short: it doesn't scale to a large list.
Pricing: varies, depending on the site or app tooling you already run.
Tip: keep the notice to what the person needs: that mail isn't reaching them, and how to fix it.
Bottom line: the people you can't email are often still reachable through the product they already use.
8. Prevent recurrence with a sunset and re-permission policy
The best long-term fix for 4.2.2 cohorts is a list that doesn't accumulate abandoned addresses. A sunset policy removes or re-permissions subscribers who haven't engaged in a set period. Our suggested starting point is to re-permission after 6 to 12 months of inactivity, then suppress those who don't respond.
Key features
- Re-permission email to inactive subscribers.
- Real-time checks at signup, covered in real-time email validation.
- Double opt-in, so typos and fake signups never reach the list.
Pros
- Fewer cohorts to manage, and cleaner engagement data.
- Reduces the number of addresses that will sit in your deferral logs.
Cons
- The list shrinks, sometimes sharply, which some teams find uncomfortable.
- Results take months to show.
Best for: any list that has grown without a regular cleanup.
Where it falls short: it doesn't fix the cohort you already have.
Pricing: mostly staff time, plus any verification costs you already carry.
Compliance. Keep the process aligned with your legal obligations. The FTC's CAN-SPAM compliance guide covers US commercial email. Our overview of email verification compliance and hygiene explains where verification fits.
Bottom line: a list maintained regularly produces fewer 4.2.2 cohorts to begin with.
How do you handle a 452 4.2.2 cohort with Unlimited Verifier?
This workflow runs the verification step on a cohort of deferred addresses. Once you have the export, it takes about 15 minutes, and it fits a weekly routine. Pair it with our email list maintenance best practices.
- Export the cohort. From your ESP or sending logs, export every address that returned 452 4.2.2 in the last 14 days, as a CSV. Keep one email column and remove duplicates.
- Create an account. Sign up for free. The Free plan covers small cohorts.
- Split the file if you're on Free. Free lists hold up to 150 emails each, and you get 25 lists a month. On Pro, each list holds up to 25,000.
- Upload and verify. Use the upload and verify page. The email column is detected automatically. Files can be up to 10MB.
- Download the results immediately. Free results are kept 24 hours and Pro results 30 days. Export as CSV, Excel or JSON, and save a copy.
- Triage the three buckets. Invalid goes to suppression. Valid returns to the next campaign. Risky goes to a hold list.
- Deep-verify the Risky group. This is where extra scrutiny changes the decision. Free includes 750 deep verifications a month, and Pro includes 25,000.
- Apply your rule. Addresses that meet the suppression threshold and show no engagement go to suppression. Everything else stays on hold.
- Re-import. Add Invalid addresses to your ESP's suppression list, tag Risky, and keep Valid active. Without the suppression step, the next import can bring dead addresses back.
- Automate on Pro. Generate keys on the email verification API page. The API handles single checks and bulk batches of up to 10,000 emails per request, within a 100,000-email monthly allowance. The Free plan has no API access. For the broader pattern, see email verification API and automation.
For a one-off check of a single address, the free email checker works without setup.
Bottom line: export, verify, triage, suppress by rule, re-import, and repeat weekly.
How do you choose the right fix for your situation?
Match the response to what you're seeing, not to the loudest advice. If you're comparing verification providers, our roundup of the best email verification tools shows how the main options sort results. Whichever you choose, check how it handles catch-alls and temporary failures.
| Your situation | Do this | Why |
|---|---|---|
| One address, one 452 4.2.2 | Wait and let it retry | One deferral is not a signal |
| Spike of 4.2.2 at one company domain | Group by domain and review | Likely a provider or policy issue |
| Large cohort before a bulk resend | Verify with Unlimited Verifier first | Separates Valid, Risky and Invalid |
| Repeated 4.2.2, no opens in 90 days | Suppress | Likely an abandoned mailbox |
| Paying customer with a full mailbox | Send an account notice | Email will keep deferring |
| Recurring cohorts every month | Sunset and re-permission policy | Stops accumulation |
| Developer with a sending pipeline | Verify through the API on Pro | Automates the weekly check |
Bottom line: the right fix depends on whether the problem is one person, one domain or the whole list.
What mistakes do senders make with 452 4.2.2 bounces?
- Deleting on the first 452. A single deferral is not evidence of a dead address.
- Treating 4.3.1 as a list problem. A storage error on the receiving system affects many recipients at once and says nothing about your list.
- Resending the whole campaign to the cohort. It adds load to full mailboxes and makes your sending look erratic.
- Assuming Valid means the mailbox has room. Verification confirms reachability, not capacity.
- Suppressing every Risky address. Catch-all and role-based addresses can include real, engaged readers. Hold them and check engagement.
- Retrying 552 5.2.2 indefinitely. It's a permanent failure, so suppress it rather than waiting.
- Losing the export. Free results expire after 24 hours, so download them the same day. For other recurring errors, see the most common email bounce codes and how to fix them.
- Misreading the notices. If your mailbox keeps receiving these, see why you keep getting mailer-daemon bounce messages.
Bottom line: most 452 4.2.2 mistakes come from acting on one signal instead of a pattern.
Verdict
A 452 4.2.2 is a temporary signal that one mailbox is full. Treat it as a reason to hold and watch, not to delete. Let the sending server retry, read the enhanced code, group deferrals by domain, and suppress only when a consecutive-bounce rule and a lack of engagement agree.
For the cleanup step, Unlimited Verifier is our top pick. Standard verification is unlimited on every plan, its Valid, Risky and Invalid sorting maps directly to send, hold and suppress decisions, and its API covers weekly automation on Pro. Its limits are real: it can't predict whether a mailbox will clear, and it has no native ESP integrations.
Bottom line: verify the cohort, hold what's uncertain, and suppress only what stays silent.
Hold vs. suppress decision thresholds
| Signal | Action |
|---|---|
| 1 deferral | Keep sending, let server retry |
| 3 deferrals over 7+ days | Hold from bulk sends |
| Still deferring after 30 days, no opens or clicks in 90 days | Suppress |
| B2B list, long buying cycle | Use 180 days instead of 90 for engagement window |
| 552 5.2.2 (permanent) | Treat as hard bounce, remove now |
| Many domains with 452 4.3.1 | Investigate receiving infrastructure |
Frequently asked questions
What does 452 4.2.2 mean?
452 4.2.2 means the recipient's mailbox is full and cannot accept the message right now. The 4 at the start marks it as a temporary failure, and 4.2.2 is the enhanced status code for mailbox full, defined in RFC 3463. The sending server should retry later, since the mailbox may free up space on its own.
Is 452 4.2.2 a hard or soft bounce?
It is a soft bounce. The 4xx class signals a temporary condition, so the message can be retried. This differs from a 5xx permanent failure, where retrying is unlikely to succeed. Many senders still track repeated soft bounces over time, because an address that defers for weeks may be effectively dead.
How long should I keep retrying a 452 4.2.2 address?
Most teams let the sending server retry for several days before acting. A common reasoned starting rule is to hold the address after three deferrals spanning at least seven days, then consider suppression only if it still defers after about 30 days with no opens or clicks. Tune these thresholds to your own data.
Should I delete addresses that bounce with 452 4.2.2?
Usually not right away. A single 452 4.2.2 reflects a condition at one moment, and the mailbox may recover. Deleting after one deferral risks removing engaged subscribers. Hold the address, watch for repeated deferrals and engagement signals, and remove it only if the pattern persists.
What is the difference between 452 4.2.2 and 552 5.2.2?
452 4.2.2 is temporary, meaning the mailbox is full now and retrying may work. 552 5.2.2 is a permanent failure with the same underlying mailbox-full meaning, so the server treats it as a rejection and generally stops retrying. Handle 552 5.2.2 as a hard bounce and remove the address from active sending.
What is the difference between 452 4.2.2 and 452 4.3.1?
452 4.2.2 concerns one recipient's mailbox being full. 452 4.3.1 indicates a server-wide problem, such as insufficient system storage on the receiving server, which can affect many recipients at once. If you see 4.3.1 across many domains, the issue is likely on the receiving infrastructure rather than your list.
Does a 452 4.2.2 bounce hurt my sender reputation?
A single temporary deferral is generally not a major reputation signal, since mailbox providers weigh hard bounces and spam complaints more heavily. However, repeatedly sending to addresses that keep deferring wastes volume and can signal weak list hygiene over time. Managing these addresses through holds and suppression helps limit that risk.
Should I verify addresses that show 452 4.2.2 before resending?
Verification can help before a bulk resend, because it can flag addresses that are invalid or risky, which may be a separate problem from the full mailbox. Verification results are not a guarantee of deliverability, so test any verifier on a sample of your list and combine its output with your own bounce and engagement data.
Can I fix 452 4.2.2 bounces by changing my sending settings?
Generally no, because the cause is on the recipient's side: their mailbox is over quota. You can reduce repeated attempts by pausing sends to deferring addresses, segmenting them into a hold group, and reviewing list growth. Asking subscribers to clear space is rarely practical, so focus on managing retries and list hygiene.
How do I suppress 452 4.2.2 addresses safely?
Move addresses to a hold segment first rather than deleting them. Suppress only those still deferring after roughly 30 days with no opens or clicks over 90 days, or 180 days for B2B lists with long buying cycles. Keep a record of suppressed addresses so you can review them if an engaged subscriber asks to rejoin.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.