Article
What Is a Mailbox Full Result in Email Verification?
By Unlimited Verifier Team ·

Summary
A mailbox full result in email verification means the mail server recognised the address but refused delivery because the recipient's storage quota is exhausted. It is usually signalled by SMTP reply 452 4.2.2 or 552 5.2.2. Treat it as a Risky state to recheck later, not as an invalid address.In email verification, a mailbox full result means the mail server recognised the address but refused delivery because the recipient's storage quota is exhausted, usually signalled by SMTP reply 452 4.2.2 or 552 5.2.2. The address is real, but it cannot receive mail right now.
This is a state, not a verdict. How you classify it decides whether you keep a paying customer or send thousands of messages into a full inbox. This page covers what the code means, how it differs from other failures, how to classify it, and how to act on it, with a worked example. It sits within the wider process described in how email verification works.
Quick answer
- It means the address exists but is full. The server answered the check and cited storage, not an unknown user.
- Look for SMTP 452 4.2.2 or 552 5.2.2. Servers differ on which code they send, so classify on the code plus the message text.
- Don't delete on one check, and don't send to it. Hold these addresses in a Risky segment, recheck about 14 days later, and suppress only if the pattern persists with no engagement.
- Watch the bounce arithmetic. We recommend a 2% total bounce ceiling. A full-mailbox segment worth 3% of a list breaches that ceiling on its own.
What does "mailbox full" mean in email verification?
A verifier checks an address by opening an SMTP conversation with the recipient's mail server and issuing RCPT TO for that address. The server replies before any message body is sent, so nothing is delivered. A mailbox full result is that reply saying the recipient exists but its storage allocation is exhausted. What does RCPT TO mean in email verification explains this step in detail, and how does an email verifier check if an address exists shows where it fits in the full sequence.
Two standards define the codes:
- RFC 5321 describes reply 552 as the response for exceeded storage allocation.
- RFC 3463 defines enhanced status codes. The X.2.2 code means "mailbox full," with 4.2.2 as the transient form and 5.2.2 as the permanent-class form.
Real servers don't always follow the textbook. Gmail is commonly reported to return a 452 4.2.2 response with wording about the account being over quota, and Microsoft-hosted mailboxes are commonly reported to use 552 5.2.2. The same condition can therefore arrive with either the temporary or the permanent code. Classify on the full response, not on the first digit.
Two practitioner observations matter here:
- A full mailbox is a snapshot. Consumer accounts fill with attachments, photos and cloud files, not just email. Google states that free accounts share 15 GB across Gmail, Drive and Photos. A user who clears a few large files can often receive mail again soon after.
- The verifier sees one moment. Any conclusion drawn from a single check is a forecast, not a finding.
Bottom line: A mailbox full result proves the address exists and is refusing mail right now. It says nothing yet about whether the person still uses it.
Is a mailbox full address valid or invalid?
Neither, yet. In a three-bucket scheme of Valid, Risky and Invalid, mailbox full belongs in Risky. Invalid means the address fails: a 550 5.1.1 response, or a domain that accepts no mail at all. A mailbox full address is one the server recognises.
The distinction changes what you do. Put these contacts in Invalid and you'll delete customers who simply haven't cleared space. Put them in Valid and you'll keep sending into a full inbox and build bounces on purpose.
Unlimited Verifier sorts results into Valid, Risky and Invalid, and flags catch-all, disposable and role-based addresses. A mailbox-full label isn't among the categories its documentation lists, so these contacts will sit in Risky without a specific tag. Spot-check a sample with the free email checker to confirm the cause before you act on the group.
Bottom line: Mailbox full is a Risky-state observation. It is neither a validity verdict nor a reason to delete.
Which SMTP responses produce a mailbox full result?
Only the X.2.2 family indicates a full mailbox. Several other failures look similar in a verification report, and mixing them up is the most common source of bad list decisions.
| SMTP reply | Enhanced code | What the server is saying | How to classify it |
|---|---|---|---|
| 452 | 4.2.2 | Mailbox full, temporary-class code | Risky: mailbox full. Recheck. |
| 552 | 5.2.2 | Mailbox full, permanent-class code | Risky: mailbox full. The code class doesn't prove permanence, so confirm with a recheck before suppressing. |
| 450 or 421 | 4.x.x | Greylisting, throttling, or service busy | Not mailbox full. Retry later. |
| 550 | 5.1.1 | Recipient address does not exist | Invalid. Suppress. |
| 550 | 5.7.x | Policy rejection, such as reputation or authentication | Not a validity verdict. Do not count as mailbox full or Invalid on this alone. Investigate the sending side. |
The 4.x.x group is the one to watch. Greylisting, where a server temporarily rejects unfamiliar senders, produces 4xx responses that look like deferrals but have nothing to do with storage. If you label those addresses as mailbox full, you'll hold back perfectly good contacts for no reason.
Bottom line: Read the enhanced code and the message text together. A 4.x.x response is a retry, not a full inbox.
Why does a mailbox full address matter so much?
It matters because the three most common explanations call for different actions. The same result can come from an active person with a cluttered account, a dormant account nobody reads, or, rarely, a misreported state. Find out which one you're dealing with before you decide to send, hold or delete.
- Active but cluttered. The person still uses the account and will clear space eventually. These contacts are worth keeping, and they often recover on their own.
- Dormant or abandoned. The mailbox stays full for months because nobody reads it. This is the pattern to worry about. The M3AAWG best practice guidance describes how abandoned addresses can be recycled into spam traps, so sending to them carries risk beyond the bounce itself.
- Misreported. Provider-side quota problems or automated replies can occasionally look like full mailboxes. These are rare, so don't build a policy around them.
The bounce arithmetic matters too. Every send to a full mailbox adds a bounce, and a full-mailbox segment can push a healthy list past an ESP's review threshold. An email service provider (ESP) is the platform that sends your campaigns. Amazon SES publishes a 5% bounce rate as the point at which it reviews an account, as set out in its documentation. Other platforms can act at lower levels, particularly on a single campaign to an unproven list. Sources disagree, so we recommend a 2% ceiling. Planning to the lower line costs you little and leaves room for the re-entry sends that get extra scrutiny.
There is also a compliance point. Email verification compliance and hygiene is about deliverability and consent, not deletion. A mailbox full address may belong to a customer who opted in. Suppressing it from campaigns is a deliverability decision. Deleting the record is a separate decision that should follow your data-retention policy.
For email verification for ecommerce and SaaS teams, this distinction is where most mistakes happen. Ecommerce customers often buy occasionally, and their addresses look dormant between orders. Treating them as dead can cost real revenue.
Bottom line: A mailbox full result is a reason to hold and recheck, not a reason to delete. The pattern over time shows whether the account is alive.
How should you classify mailbox full addresses?
Classify on pattern, not on a single result. Use three inputs: the response code, how many checks have returned the same result, and whether the contact has engaged recently.
| What you observe | Classification | Action |
|---|---|---|
| First 452 4.2.2 or 552 5.2.2 result; recent opens or clicks | Risky: mailbox full | Hold. Recheck in about 14 days. |
| Full on two checks at least 14 days apart; no engagement in 12 months | Risky: likely abandoned | Suppress from campaigns. Keep the record. |
| Full on a recheck, now deliverable | Valid | Release to your send segment. |
| Any 550 5.1.1 response | Invalid | Suppress permanently. |
| Full result on a catch-all domain | Risky: catch-all | Handle separately, as described below. |
The catch-all row needs care. A catch-all domain accepts mail for any address, so a verifier can't confirm the individual mailbox. How do verifiers detect catch-all domains explains the detection, and what does accept-all mean in an email verifier covers how the label is applied. Bounce-based catch-all verification describes one way that uncertainty gets resolved. For how Unlimited Verifier handles those domains, see the catch-all email verification page. Mailbox full and catch-all are different problems, and a contact shouldn't be filed under one just because it shows the other.
The two-check rule is our recommendation, not a published standard. One check can catch a temporary state. Two checks spaced two weeks apart separate a busy inbox from an abandoned one. The spacing also stops you from spending allowance on an unchanged result.
Bottom line: Pattern beats a single reading. Hold on the first result, and suppress only when a persistent full mailbox shows no engagement.
What are your options for mailbox full contacts?
You have four realistic options, and each suits a different kind of contact.
| Option | Upside | Downside | Best for |
|---|---|---|---|
| Send normally | Maximum reach if the mailbox clears in time | Each send to a full mailbox becomes a bounce | Almost no marketing sends. Consider it only for transactional messages you cannot reroute. |
| Hold in a Risky segment and recheck | Keeps active customers; avoids bounces | Delays reaching those contacts | Contacts with recent engagement |
| Suppress | Protects bounce rate and sender reputation | You lose contacts who might recover | Persistent full mailboxes with no engagement |
| Contact the account holder through another channel | Reaches the real owner | Needs a channel you already have permission to use | High-value accounts such as B2B clients |
The suppression option has a cost people underrate. Suppressing a contact removes it from campaigns, but the record should stay in your database with its status and date. That history lets you recognise a returning contact later and avoid re-adding it blindly. Email list maintenance best practices covers how to set up that kind of suppression record and keep it current.
Bottom line: Hold recently engaged contacts, suppress persistent dead ones, and reach high-value accounts through a channel you already have permission to use.
How do you handle mailbox full results in Unlimited Verifier?
Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the workflow runs as export, verify and re-import, or through the API. The steps below use the standard web workflow.
- Export your contacts as a CSV. Include the email column and a last-engagement date, such as last open, last click or last purchase. Save an untouched copy of the export. That original is your audit trail.
- Create an account. You can sign up. The Free plan covers 25 lists a month of up to 150 emails each, with 750 deep verifications a month and results kept for 24 hours. The Pro plan is $29 a month, or $25 a month billed annually. It handles lists of up to 25,000 emails each, with 25,000 deep verifications a month and results kept for 30 days.
- Upload the file. Go to Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. If your file exceeds the per-list cap for your plan, split it first.
- Run verification. Each address is checked for syntax, domain and MX records, and the SMTP mailbox. Catch-all domains are flagged, along with disposable and role-based addresses. Standard verification is unlimited on every plan, including Free.
- Open the Risky bucket. Sort it by flag. Rows with a catch-all, disposable or role-based flag have a different path, and how do verifiers detect disposable email domains explains that flag. Rows with none of those flags are the likeliest mailbox full candidates. Confirm a sample individually before you act on the group.
- Export the results as CSV, Excel or JSON. Name each file with the run date. The retention window matters here: results are kept 24 hours on Free and 30 days on Pro. Your saved file is the record, not the platform.
- Re-import in three segments. Import Valid contacts to your send list. Import Invalid contacts to your suppression list. Import Risky contacts into a segment named something like "Risky, recheck [date]," and keep that segment out of campaigns.
- Schedule the recheck. Set a reminder for about 14 days out. On that date, upload only the Risky segment and repeat steps 3 to 6.
For ongoing use, the email verification API lets you run the recheck from a script rather than a manual upload. Pro includes 100,000 API emails a month, and each bulk request accepts up to 10,000 addresses. Email verification API and automation covers the common patterns. For signup forms, real-time email validation can catch many of the same results at the point of entry, before they reach your list.
Bottom line: Export, verify, sort Risky by flag, save the dated results, re-import in three segments, and put the recheck on the calendar.
What does a worked example look like?
This example is illustrative. The numbers are hypothetical, but the plan limits and the arithmetic are real.
The starting point. A SaaS company has a 40,000-row list of trial users and past customers, exported from its CRM.
Plan fit. Pro handles lists of up to 25,000 emails each, so the file splits into two uploads of 25,000 and 15,000. Free cannot process the whole list in a month. At 150 emails per list and 25 lists a month, Free covers 3,750 emails, which is 9.4% of the file.
First run (standard verification, hypothetical results):
- Valid: 33,400 (83.5% of 40,000)
- Risky: 4,100 (10.25%)
- Invalid: 2,500 (6.25%)
Check: 33,400 + 4,100 + 2,500 = 40,000.
Of the 4,100 Risky rows, 2,900 carried a catch-all, disposable or role-based flag: 1,900 catch-all and 1,000 disposable or role-based. The other 1,200 carried none of those flags, and the company's sample check showed mailbox full responses for them.
Check: 1,900 + 1,000 + 1,200 = 4,100.
Mailbox full is 1,200 ÷ 40,000 = 3.0% of the list. Sent in one go, those contacts alone would have produced a bounce rate above the 2% ceiling.
Deep verification budget. A deep re-run on the 4,100 Risky addresses uses 4,100 of Pro's 25,000 monthly deep verifications. That leaves 20,900 for rechecks and spot-checks. For more on the difference between the two check types, see deep email verification vs standard verification.
The recheck at 14 days (hypothetical):
- Now Valid, quota cleared: 780
- Still mailbox full: 300
- Now Invalid: 120
Check: 780 + 300 + 120 = 1,200.
What the company did:
- The 780 recovered contacts went to the send list, starting with those who had engaged most recently.
- The 120 Invalid contacts were suppressed permanently.
- The 300 still-full contacts were checked again at day 28. Those with no engagement in 12 months were suppressed. Those with recent engagement stayed in the Risky segment for one more cycle.
Cost. One Pro month at $29, or $25 a month on the annual plan. The second upload and the recheck both fit within that month's allowances. Compare plans against your own volumes using email verification pricing.
Bottom line: A 1,200-row segment that looks small is 3% of this list. Holding it for a recheck costs far less than the bounces it prevents.
What mistakes should you avoid with mailbox full results?
- Deleting on the first result. A cluttered inbox looks identical to an abandoned one on day one. Hold first, and delete only once the pattern is clear.
- Sending to the whole Risky bucket. Catch-all, disposable and mailbox full results need different handling. Lumping them together hides the one that matters.
- Treating 4.x.x responses as mailbox full. Greylisting and throttling return temporary codes, and they usually resolve on a retry.
- Rechecking too often. Verifying the same unchanged address daily wastes allowance and tells you nothing new. A two-week gap is a sensible starting point.
- Losing the history. Exporting a clean list and discarding the original removes the evidence of what happened. Keep dated exports.
- Ignoring plan caps. Free handles 150 emails per list, and Pro handles 25,000. Files over the cap should be split before upload.
- Forgetting the 24-hour retention on Free. Results are kept 24 hours on Free, so download them the same day.
- Assuming vendor labels match. Verification vendors draw the Risky line differently. Compare outputs on a sample before you change your process.
- Forgetting that a full mailbox can belong to a real customer. Suppress for deliverability, but keep the contact and its consent record.
Bottom line: Most mistakes come from treating a snapshot as a verdict. Hold, recheck, and let the pattern decide.
How long should you wait before rechecking?
There is no published industry standard for this window, so treat the 14-day and 28-day cadence as a practical default. A shorter window spends allowance on addresses that haven't had time to change. A longer one leaves contacts in limbo without a decision.
Two checks spaced two weeks apart suit most lists. High-value segments, such as enterprise accounts, can justify a third check before you suppress.
Bottom line: Recheck at about two weeks and again at four. Beyond that, the pattern is usually clear enough to act on.
How we compared (and limitations)
This guidance is based on public documentation: RFC 5321 and RFC 3463 for the status codes, Google's published account storage information, Amazon SES's documentation for bounce thresholds, and general deliverability practice described by M3AAWG. We have not run controlled tests against individual mailbox providers, and provider behaviour changes without notice.
Three limitations to keep in mind:
- Codes vary by provider. The same condition can return different codes, so classify on the full response text. Yahoo and AOL behave differently in some cases, as covered in does email verification work for Yahoo and AOL addresses.
- Verifier labels vary. Tools place the Risky line in different places. If you're weighing vendors on how they report temporary states, test them on your own sample. A guide to the best email verification tools and a checklist for how to choose an email verifier can help structure that comparison.
- The worked example is hypothetical. The percentages are illustrative. The plan limits come from Unlimited Verifier's published plan facts.
Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark, and it doesn't guarantee how any single mailbox will respond at any given moment.
For how the underlying checks work, see how do verifiers check if a domain accepts mail.
Bottom line: Treat a mailbox full result as a time-stamped observation. Recheck it, record it, and decide on the pattern.
Worked example: bounce ceiling arithmetic
Assume a 100,000-address list with a 2% total bounce ceiling, meaning no more than 2,000 bounces per send.
| Segment | Share | Addresses | Action |
|---|---|---|---|
| Valid | 94% | 94,000 | Send |
| Mailbox full (Risky) | 3% | 3,000 | Hold and recheck in 14 days |
| Invalid | 3% | 3,000 | Suppress |
If the 3,000 full-mailbox addresses were mailed, they alone would exceed the 2,000-bounce ceiling before any invalid address is counted. Holding them in Risky keeps the send within limits.
Frequently asked questions
Is a mailbox full address valid?
Not fully. A mailbox full result means the address exists but cannot accept mail at the moment. Most verification schemes place it in a Risky bucket rather than Valid or Invalid, so it can be rechecked before any decision to keep or remove it.
What SMTP code means mailbox full?
The standard code is 552 5.2.2 for exceeded storage allocation, and 452 4.2.2 is the temporary form. RFC 3463 defines X.2.2 as mailbox full. Servers vary, so classify on the enhanced code and the message text together.
Should I delete addresses that return mailbox full?
No, not after a single check. Hold them in a Risky segment, recheck after about 14 days, and suppress only if the address stays full and shows no engagement over that period.
Is mailbox full a hard bounce or soft bounce?
It is usually treated as a soft bounce because the condition can clear once the user frees space. A 552 5.2.2 response is permanent-class in code, while 452 4.2.2 is transient, so the handling should follow the full response text and repeat behaviour.
Does a mailbox full result hurt sender reputation?
Repeated sends to full mailboxes can add bounces that signal poor list hygiene. Keeping total bounce rate under a ceiling, such as 2 percent, and not mailing Risky addresses helps protect reputation.
How long should I wait before rechecking a mailbox full address?
A recheck around 14 days is a reasonable starting point because many people clear space within that window. Adjust the interval based on your list's engagement and how often the same address returns the same result.
Can a mailbox full address still receive email?
Not while the quota is exhausted. Once the user frees storage, the server can accept mail again. Until then, messages are refused at the RCPT TO stage, so no body is delivered.
Why does a verifier return mailbox full for Gmail or Outlook addresses?
Consumer accounts share storage across email, cloud files and photos, so they fill up often. Providers such as Google state that free accounts share a fixed quota, and a full account will answer with a storage-related SMTP reply.
Does mailbox full mean the person has stopped using the address?
Not necessarily. It is a snapshot of storage, not of activity. An active user can be full temporarily, so engagement history is a better signal than one verification result.
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.