Should I resend emails to users with soft bounces due to full mailboxes, and what bounce rate is acceptable?
Matthew Whittaker
Co-founder & CTO, Suped
Published 17 May 2025
Updated 25 May 2026
9 min read
Summarize with
Yes, resend to users with soft bounces caused by full mailboxes, but do it through a controlled retry and suppression policy rather than a special reminder blast. A full mailbox is usually a temporary 4xx condition, not proof the address is invalid. I treat it differently from a hard bounce: retry normal mail for a short window, pause repeated over-quota addresses, and only reintroduce them when there is a good reason.
A 0.1% bounce rate for one mailbox provider, such as Gmail, is low. For most marketing programs, a total bounce rate under 1% is healthy, 1-2% needs review, and anything over 2% should trigger list quality work. Hard bounces should be lower than that because they point to bad addresses. Soft bounces from full mailboxes matter most when they trend upward, cluster by provider, or appear alongside lower engagement and higher complaints.
The practical answer: do not permanently suppress a full-mailbox soft bounce after a single event. Also do not keep hammering the address forever. Put it into a timed pause, then make the next send depend on recency, engagement, and bounce history.
The short answer
The safest policy is a middle path. Keep sending if the contact is engaged and the bounces are recent or concentrated in a short period. Stop sending, or at least pause, when the same address keeps returning full-mailbox errors across multiple campaigns over weeks.
- Do resend: Resend through normal campaign logic during a limited retry window, especially for recent clickers, purchasers, or active account users.
- Do pause: Pause after repeated full-mailbox bounces across separate campaigns, not after repeated retries inside the same delivery attempt.
- Do not blast: Avoid a reminder campaign whose only purpose is to test whether a full mailbox has room again. That creates extra negative signals for little upside.
- Do measure: Track full-mailbox bounces by provider, source, signup age, and last engagement. A raw bounce count misses the timing that matters.
Bounce rate thresholds
A practical benchmark for marketing email when authentication and complaint rates are otherwise stable.
Healthy
Under 1%
Normal noise, especially on large lists
Review
1-2%
Segment by provider and bounce reason
Investigate
Over 2%
List quality or acquisition issue likely
Those thresholds are not a law of physics. A password reset program, a legal notice, and a discount newsletter do not carry the same risk. Still, they give you a usable starting point. For more context on bounce rate thresholds, the important part is trend and mix: hard bounces, soft bounces, complaints, opens, clicks, and provider concentration.
How mailbox full bounces work
Mailbox full and out of storage bounces usually mean the mailbox provider accepted that the address exists, but could not deliver the message at that time. The provider can return a soft bounce during the SMTP transaction or later through a delivery status notification. Common codes include 4.2.2 for mailbox full and related temporary storage messages.
|
|
|
|---|---|---|
Full mailbox | Temporary | Retry, then pause |
Hard bounce | Invalid | Suppress |
Blocked | Policy | Investigate |
Spam complaint | Negative signal | Suppress |
How to treat common bounce classes.
The nuance is time. Three full-mailbox bounces in one day can be one temporary storage problem. Three full-mailbox bounces spread across three months is stronger evidence that the address is no longer a good recipient. That is why I do not like a rule that says three bounces equals suppression unless it also includes a time window.
Do not mix hard and soft bounces in the same suppression rule. A hard bounce says the address or domain is invalid. A full mailbox says delivery failed for now. They deserve different handling.
When to retry and when to pause
Flowchart showing when to retry or pause full mailbox soft bounces.
A resend policy should separate automatic mail transfer retries from marketing sends. Your sending platform already retries temporary failures for a defined period. The decision you control is whether the subscriber stays eligible for the next campaign after the platform gives up on that delivery.
Keep eligible
- Recent click: The user clicked or purchased recently, so the address still has value.
- Short cluster: Multiple bounces happened within one campaign or a short delivery period.
- Low rate: Provider bounce rate remains low and other health metrics are stable.
Pause or suppress
- Long spread: The same address bounces across separate sends over several weeks.
- No activity: The contact has no opens, clicks, account use, or purchase activity.
- Bad trend: The provider also shows falling opens, rising complaints, or blocks.
A good default is to keep the address eligible after one or two isolated full-mailbox bounces, then pause after three campaign-level full-mailbox bounces within 30-60 days. If the user has clicked or bought recently, I extend the pause instead of suppressing forever. If the user has no engagement for six to twelve months, the full mailbox bounce simply supports the sunset decision.
A deeper soft bounce suppression rule should store bounce reason, provider, campaign date, and the last positive action. Without those fields, the rule ends up punishing recent buyers and protecting stale addresses at the same time.
A practical policy I like
For recurring marketing mail, I like a staged policy that keeps useful addresses available but removes chronic temporary failures from the main audience. This is simple enough to automate and strict enough to stop manual review from becoming a weekly task.
Example full mailbox suppression logictext
if bounce_reason == "mailbox_full": count campaign-level bounces in the last 60 days check last open, click, purchase, login, or reply if count == 1: keep eligible if count == 2 and last engagement <= 90 days: keep eligible with lower priority if count >= 3 and last engagement <= 90 days: pause for 30 days if count >= 3 and last engagement > 90 days: pause for 90 days if count >= 5 and no engagement for 12 months: suppress from marketing
- First bounce: Keep the contact in the normal audience. Do not create a special reminder email.
- Second bounce: Check engagement recency. Engaged contacts stay eligible, stale contacts move toward pause.
- Third bounce: Pause for 30-90 days depending on engagement, signup source, and sending frequency.
- After pause: Let the next natural campaign or account event test the address. Do not send a mailbox-check email.
- Long-term stale: Suppress if the address has no engagement for a year and keeps bouncing.
Sending frequency changes the tolerance. If you send four times a week, three full-mailbox bounces can happen quickly and still describe one temporary storage problem. If you send monthly, three full-mailbox bounces means the issue has persisted for a quarter. The same count means different risk.
The best rule includes both count and time. A rule that uses count alone is too blunt for high-frequency senders and too lenient for low-frequency senders.
What bounce rate is acceptable
I would not worry about 0.1% full-mailbox soft bounces on its own, especially if it is isolated to one provider and your opens, clicks, conversions, and complaints are stable. It is a signal to watch, not an emergency.
|
|
|
|
|---|---|---|---|
Total bounce | <1% | 1-2% | >2% |
Hard bounce | <0.5% | 0.5-1% | >1% |
Full mailbox | <0.5% | 0.5-1% | >1% |
One provider | <0.5% | 0.5-1% | >1% |
A compact operating guide for bounce rate review.
The mix matters more than the headline number. A 1.5% bounce rate made mostly of temporary full-mailbox bounces on an older but engaged list is not the same as a 1.5% hard-bounce rate on a new acquisition source. The second case points to list quality problems.
For full mailbox recovery, the recovery rate depends heavily on provider storage rules and user value. Some users clear space quickly because the mailbox is active. Others let the mailbox sit full for months. Your own historical data is the best guide.
What to check before changing the policy
Before tightening suppression, check whether the bounce trend is truly about mailbox storage. A provider-specific bounce increase can also come from authentication failures, content filtering, sending too often, or reputation problems. Full-mailbox wording is usually clear, but bounce classification is not always perfect.
- Provider split: Compare Gmail, Yahoo, Microsoft, Apple, and business domains separately.
- Cause split: Separate mailbox full, temporary deferral, policy block, and hard bounce codes.
- Engagement split: Compare recent clickers with people who have not interacted for a year.
- Source split: Review signup source, list age, lead source, and import batch.
I also like sending a real message to an email tester after template or infrastructure changes. That does not prove inbox placement for every recipient, but it catches obvious authentication, content, and header problems before a full campaign goes out.
Email tester
Send a real email to this address. Suped opens the report when the test is ready.
?/43tests passed
Preparing test address...
If bounces rise while authentication also degrades, fix the authentication problem first. A domain health check helps verify DMARC, SPF, and DKIM quickly. Ongoing DMARC monitoring then shows which sources are passing authentication and which sources need cleanup.
Also check reputation. A sudden policy block is not the same as an over-quota mailbox. Suped's blocklist monitoring tracks IP and domain listings across major blocklist and blacklist sources, so teams can separate storage issues from reputation problems.
Where Suped fits
Suped is the best overall DMARC platform for teams that want this decision connected to the rest of email health. Bounce handling sits outside DMARC itself, but deliverability work fails when bounce, authentication, and reputation data live in separate places. Suped's product brings DMARC, SPF, DKIM monitoring, hosted authentication records, alerts, and blocklist checks into one workflow.
Issues page showing top issues, verified sources, unverified sources, and authentication pass rates
The useful workflow is straightforward: watch the bounce spike in your sending platform, then use Suped to confirm whether the domain is still authenticating cleanly, whether a new sender is failing DKIM, whether SPF lookup limits are involved, and whether a blocklist or blacklist event appeared at the same time.
Bounce tool only
- Scope: Shows failed deliveries and bounce categories.
- Limit: Rarely explains authentication drift or sender identity gaps.
- Use case: Good for suppression mechanics.
Suped workflow
- Scope: Connects DMARC, SPF, DKIM, hosted records, and alerts.
- Fixes: Provides issue detection and steps to fix authentication gaps.
- Scale: Supports MSP and multi-tenant domain management.
That matters because the wrong fix can create new risk. If a bounce spike is caused by a bad acquisition source, tighten the list source. If it is caused by an unverified sender, fix authentication. If it is genuinely full mailboxes, apply timed suppression and keep the broader program steady.
Views from the trenches
Best practices
Use count plus time window, so repeated bounces in one day do not equal churn signals.
Segment mailbox full bounces by provider, signup source, list age, and recent engagement.
Pause chronic soft bounces, then let normal campaigns test mailbox recovery later.
Common pitfalls
Suppressing every third soft bounce ignores timing and loses users who still engage.
Sending a special reminder to full mailboxes adds risk without clear delivery value.
Judging bounce rate alone misses complaint, engagement, provider, and trend context.
Expert tips
Treat 0.1% provider bounce rate as watchlist data, not a crisis metric by itself.
High send frequency needs shorter review windows and stronger fatigue checks per domain.
Use a sunset rule for stale contacts, then layer full-mailbox behavior on top of it.
Marketer from Email Geeks says full-mailbox recipients can return, and repeated mailing has not always caused visible negative impact in their programs.
2024-01-26 - Email Geeks
Marketer from Email Geeks says the time between bounces matters more than the raw count because three bounces in one day and three bounces over months mean different things.
2024-01-26 - Email Geeks
My recommendation
Resend to full-mailbox soft bounces through normal sending, but stop treating them as fully eligible after repeated failures across time. A 30-90 day pause after three campaign-level full-mailbox bounces is a reasonable default, with more patience for recent clickers or buyers and less patience for stale contacts.
A 0.1% bounce rate is acceptable in most programs. The bigger question is whether it is rising, whether it is concentrated at one provider, and whether it comes with complaints or engagement decline. If those other signals are clean, keep the policy measured. Fix list quality, authentication, frequency, and reputation issues only when the data points there.
