Article
Most Common Email Bounce Codes and How to Fix Them
By Unlimited Verifier Team ·

Summary
The most frequent bounce codes in bulk sends are 5.1.1 (user unknown), 5.1.2 (bad destination host), 4.2.2 (mailbox full) and 5.7.1 (policy block). Address-level 5.x codes are fixed by suppressing dead addresses, while 5.7.x and throttling codes require changes to your sending setup.The bounce codes that appear most often in bulk sends are SMTP 5.1.1 ("user unknown"), 5.1.2 ("bad destination host") and 4.2.2 (mailbox full), plus 5.7.1 policy blocks. Address codes are fixed by suppressing dead addresses; policy and reputation codes need changes to your sending setup.
Quick answer
- 5.x.x codes are permanent. Suppress address-level ones (5.1.1, 5.1.2, 5.2.1) now, because retries won't succeed.
- 4.x.x codes are temporary. Mailbox-full (4.2.2) and throttling (4.7.0) usually clear on their own. Suppress only after repeated failures.
- 5.7.x policy codes usually aren't list problems. Blocklists, authentication gaps and sending speed are the common causes, so deleting addresses won't fix them.
- Verify before the next send. Sorting addresses into Valid, Risky and Invalid removes address-level failures before they reach a campaign.
What do email bounce codes mean and how are they structured?
A bounce code is the status a receiving server returns when it refuses or defers a message. The first digit of the SMTP reply tells you whether the failure is temporary (4) or permanent (5), as defined in RFC 5321. The enhanced status code, defined in RFC 3463, adds three parts in the form X.Y.Z.
For the full taxonomy, start with our email bounce codes guide. This page covers the codes behind most failures and how to fix each one. For the temporary-versus-permanent split in depth, see 4xx and 5xx SMTP errors.
| Position | What it tells you | Values you'll see |
|---|---|---|
| X (class) | Outcome | 2 = success, 4 = temporary, 5 = permanent |
| Y (subject) | Area of the problem | 1 = address, 2 = mailbox, 3 = mail system, 4 = network/routing, 5 = protocol, 6 = content, 7 = security/policy |
| Z (detail) | Specific reason | 5.1.1 = mailbox doesn't exist |
The subject digit is the most useful for triage. A 5.1.x code points at the recipient address, while a 5.7.x code points at policy, which often means your sending infrastructure. The full reference is in our enhanced SMTP status codes list.
Receivers return these codes in a non-delivery report (NDR), usually sent to your return-path address. RFC 3464 defines that format. Many ESPs summarize NDRs into a single label, so the raw text is often more useful than the dashboard. If you're seeing repeated notices in your inbox, see why you keep getting MAILER-DAEMON bounce messages.
Bottom line: The first digit decides retry versus remove. The subject digit tells you whether the problem is the address, the mailbox, the network or your sending.
Which bounce codes cause the most problems?
Most bounce logs are dominated by a small group of codes. The table covers the ones you'll see most, with the usual cause and fix. For every code, see the SMTP error codes list with meanings.
| Code | What it usually means | Fix |
|---|---|---|
| 5.1.1 | Mailbox doesn't exist | Suppress; correct the form or import that captured it |
| 5.1.2 | Domain or host doesn't exist, or has no mail server | Suppress the domain; check for typos or expiry |
| 5.1.3 | Address string is malformed | Clean the export (spaces, stray characters), then re-verify |
| 5.2.1 | Mailbox disabled or closed | Suppress; common when B2B contacts change employers |
| 4.2.2 / 5.2.2 | Mailbox full | Retry later; suppress only if it persists |
| 5.3.4 | Message too large | Remove large attachments and link to files instead |
| 5.7.1 | Blocked or policy rejection | Check blocklists, relay settings and content; don't delete the address |
| 5.7.26 | Gmail rejecting mail that fails authentication | Fix SPF, DKIM and DMARC alignment |
| 4.4.1 / 4.4.2 | No answer from host, or bad connection | Retry; check network paths |
| 4.7.0 / 421 4.7.0 | Temporary rate limit | Slow the send rate; send to engaged contacts first |
Two details matter here. Mailbox-full appears as both a 4 and a 5 code, and providers don't use them consistently, so judge it by persistence rather than class. Also, a 5.1.x code can arrive alongside a 4.x code from the same server, so read the full reply text.
Bottom line: Ten code groups explain most bounces in a typical campaign report. Learn them and you can diagnose most of your logs.
How do you fix hard bounces caused by bad addresses?
Suppress the address permanently and fix whatever let it onto the list. A 5.1.1 will not succeed on retry, so hard-bounce cleanup is mainly a data-quality task.
5.1.1 and 5.1.2: nonexistent mailboxes and domains
Sort bounced addresses by domain before you suppress anything. Misspelled popular domains such as gmial.com or yaho.com often produce a dense cluster of failures, which usually points to one faulty signup form or import. Fix the validation at the source first. Then decide case by case whether a corrected address is worth contacting. Only resend to a corrected address you can confirm belongs to that person, and check it with the Free email checker first.
If every address on one domain returns 5.1.2, the domain is probably expired or has no mail server. A 5.1.10 response is different: it signals a "null MX" record, meaning the domain has stated that it accepts no mail, as RFC 7505 describes. In both cases, suppress the whole domain rather than individual addresses. For the detail behind 5.1.2, see the 550 5.1.2 bad destination host guide. For the single-address case, the 550 5.1.1 user unknown explainer covers the wording you'll see from different providers.
5.1.3: malformed strings created during export
A 5.1.3 usually comes from how the data moved, not from the contact. Trailing spaces, a "Name
" pattern carried over from a CRM, or a stray comma inside a cell all produce it. Clean the column and re-verify. Suppressing the person in this case throws away a valid contact.5.2.1: disabled mailboxes
A disabled mailbox means the owner or employer closed the account. There's no retry path, so suppress it. This is common in B2B lists, where people change jobs and their work address stops working.
Bottom line: Hard address codes are a data problem. Suppress the failures, fix the capture point, and re-verify before you resend.
How do you handle soft bounces without damaging your list?
Treat 4.x.x codes as a reason to retry. Convert one into a suppression only after it repeats across separate sends. RFC 5321 defines 4yz replies as transient, so the sending server is expected to queue the message and try again.
Mailbox-full and connection issues
Mailbox-full (4.2.2) clears when the recipient frees space, so it usually recovers on a later send with no action from you. Connection timeouts (4.4.1, 4.4.2) are usually network or routing problems, and a later attempt typically succeeds. The common soft bounce reasons list covers the rest of this group.
Throttling and reputation signals
A 4.7.0 or 421 4.7.0 response usually means the receiver is rate-limiting your IP or domain. Retrying harder makes this worse. Slow the send rate and send first to your most engaged contacts. The 421 4.7.0 try-again-later guide explains the timing.
Gmail's 421 4.7.28 response signals an unusual rate of unsolicited mail. That's a reputation signal, not a retry prompt. Reduce volume to engaged segments and check your complaint rate before resending.
Greylisting
Greylisting is a deliberate temporary rejection, often seen as 450 4.7.1 or 451 4.7.1. The receiver wants to see the sender retry after a short delay. The 450 requested mail action not taken guide covers the details. Retrying normally succeeds, so no list action is needed.
Our suppression rule
We recommend suppressing a soft-bouncing address only after three consecutive failed sends across at least two weeks. Platform behavior varies here: some suppress after a single soft bounce, while others keep retrying for days. We recommend three sends because it spares contacts whose mailbox was temporarily full, and it still clears addresses that never recover.
Bottom line: Soft bounces are about timing and throttling. Slow down and retry, and suppress only when the failure persists.
Why does reading the bounce text matter more than the code?
The code gives you a category, but the text gives you the cause. Receivers reuse codes broadly. 5.7.1 is the clearest example: it can mean a blocklist hit, a relay refusal, a content rejection or a policy decision, and each needs a different fix. The 554 5.7.1 explanation shows how to tell them apart. A 5.7.1 that mentions a blocklist is a reputation problem. One that says the user is unknown is a list problem.
Two patterns matter in practice:
- Catch-all domains accept first and bounce later. Some domains accept any address at SMTP time, then return an NDR afterward. Late bounces can arrive hours or days after the send, so "delivered" is not proof of a real mailbox. Treat Risky results on catch-all domains as unknown, not Valid. The catch-all email verification page explains how these domains are flagged.
- The dashboard label is a summary. Many ESPs group NDRs into "hard" and "soft" buckets, and the bucket can hide the detail. Pull the raw reason before you act on a label.
Bottom line: Classify by code and diagnose by text. Never suppress a whole category based on the summary label alone.
Do Gmail, Outlook and Yahoo use the same bounce codes?
Most providers use the standard enhanced codes, but their policy wording differs, so the same code can mean different things at each one. Gmail returns 5.7.26 for mail that fails authentication checks and 421 4.7.28 for an unusual rate of unsolicited mail. Microsoft's Outlook and Exchange Online systems return 5.7.515 when a sender's domain fails DMARC and the domain publishes a reject policy. Yahoo and other providers word their rejections differently, so match on the enhanced code and then read the reply text.
Bottom line: Provider-specific policy codes usually point to authentication and reputation, not list quality. Check your DNS records and sending setup before you touch the list.
Which bounces should you suppress and which should you retry?
Apply this decision table to each bounce category before you change your list.
| Bounce pattern | Example codes | Action | Why |
|---|---|---|---|
| Address doesn't exist | 5.1.1, 5.1.2, 5.1.10 | Suppress now | Retries can't succeed |
| Mailbox closed | 5.2.1 | Suppress now | The account is gone |
| Malformed string | 5.1.3 | Fix the string, re-verify, then send | The person may still be reachable |
| Policy or reputation | 5.7.1, 5.7.26, 5.7.515 | Pause affected sends, fix the cause, don't suppress | The address is likely valid |
| Mailbox full | 4.2.2, 5.2.2 | Retry; suppress only after persistent failure | Quota clears over time |
| Throttling | 4.7.0, 4.7.1, 421 4.7.28 | Slow down; send to engaged contacts first | A reputation signal |
| Connection | 4.4.1, 4.4.2 | Retry | Usually a network issue |
Bounce-rate thresholds: where sources disagree
Amazon SES's documentation describes bounce-rate thresholds of 5% for review and 10% for possible pause. Most other platforms publish fewer exact figures. Google's sender guidelines set a spam-complaint ceiling of 0.3%, a different metric from bounces.
We recommend a 2% total bounce ceiling and a 1% address-level target, both measured against attempted sends. Total bounces include policy codes you fix rather than delete, so the 1% target applies to the address codes you control.
Bottom line: Use 2% total and 1% address-level as your operating limits. Platform thresholds are where enforcement starts, not where you should aim.
How do you triage a bounce log step by step?
Work through this seven-step framework after any campaign that bounces above your ceiling.
- Export the raw bounce log for one campaign, including the code and the reason text.
- Count by enhanced code (for example, 5.1.1) rather than by the ESP's summary label.
- Sort each code into one bucket: address, mailbox, policy or transient.
- Calculate two rates: total bounces divided by attempted sends, and address-level hard bounces divided by attempted sends.
- Suppress address-level hard bounces and keep your own copy. Suppression lists don't always migrate between platforms.
- Verify the remaining list before the next send.
- Fix policy and transient causes, resend to a small engaged segment, and recheck the same codes.
Bottom line: The log sorts into buckets. Act on each bucket, not on the total.
How do you verify a list to catch address bounces before sending?
Address-level bounces are the easiest to prevent, because you can check every address before it reaches your sender. Teams comparing best email verification tools should look at three things: whether the tool checks the SMTP mailbox, how it sorts results, and how its pricing scales. Our buyer's checklist for choosing a verifier covers those in detail. Teams running email verification for ecommerce and SaaS face the same triage at larger volumes.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It flags catch-all, disposable and role-based addresses and sorts results into Valid, Risky or Invalid. Standard verification is unlimited on every plan, with no per-email fees.
Address checks line up with the 5.1.x codes. They can't see blocklists or throttling, so they won't catch 5.7.x or 4.7.x problems. Use these steps for the address side of your triage:
- Export the remaining list. Include the contacts left after suppression, the email column and any engagement field such as last open date.
- Sign up. The Free plan allows 25 lists a month of up to 150 emails each, plus 750 deep verifications. It has no API access, and results are kept for 24 hours.
- Choose a plan by volume. The Free plan caps you at 3,750 emails a month (25 lists × 150). Pro costs $29 a month, or $25 a month billed annually. It allows lists of up to 25,000 emails each, 25,000 deep verifications a month, and API access (100,000 emails a month).
- Upload and verify a list. Upload a CSV or Excel file up to 10MB. The email column is detected automatically. On Pro, split any file above 25,000 rows first.
- Read the three buckets. Invalid addresses are suppressed permanently. Risky rows, including those with the catch-all, disposable or role-based flags, are held back from the first sends. Valid addresses are the only ones you send to.
- Export results as CSV, Excel or JSON. Download them before they expire: 24 hours on Free, 30 days on Pro.
- Re-import only Valid contacts into your ESP as a new segment. Add Invalid ones to your ESP suppression list and to your own file.
- Recheck after the next send. Compare per-code counts against the previous log.
There are no native ESP, CRM or Zapier integrations. The workflow runs as export, verify and re-import, or through the email verification API in your own scripts.
Bottom line: Verification removes address-level failures before they happen. It does not fix policy or reputation codes, so keep those in your triage.
What does a real bounce triage look like with numbers?
This example is illustrative and the code counts are hypothetical. The arithmetic and plan limits are real.
A retailer sends one campaign to 80,000 contacts and logs 2,400 bounces:
| Code | Count | % of 80,000 sends | Bucket | Action |
|---|---|---|---|---|
| 5.1.1 | 1,500 | 1.88% | Address | Suppress |
| 5.1.2 | 420 | 0.53% | Address | Suppress |
| 5.7.1 | 200 | 0.25% | Policy | Investigate; don't suppress |
| 4.2.2 | 180 | 0.23% | Transient | Retry |
| 4.7.0 | 100 | 0.13% | Transient | Slow down |
| Total | 2,400 | 3.00% |
Percentages are rounded to two decimals.
The arithmetic gives four results:
- Total bounce rate: 2,400 ÷ 80,000 = 3.00%, above the 2% ceiling.
- Address-level hard bounces: 1,920 ÷ 80,000 = 2.40%, the figure to suppress.
- Policy bounces: 200 ÷ 80,000 = 0.25%, to investigate rather than delete.
- Transient bounces: 280 ÷ 80,000 = 0.35%, to retry.
Suppression: 80,000 − 1,920 = 78,080 contacts remain.
Verification capacity: On Free, 78,080 ÷ 150 = 521 lists. At 25 lists a month, that's about 21 months, so Free doesn't fit this job. On Pro, the file splits into four lists: 25,000 + 25,000 + 25,000 + 3,080. Standard verification covers all 78,080 with no per-email fee. Use the 25,000 deep verifications on the riskiest slice, such as imported contacts with earlier soft-bounce history.
Cost: One Pro month is $29. If you use the full 25,000 deep allowance, that works out to $29 ÷ 25 = $1.16 per 1,000 deep checks. Annual billing lowers the monthly price to $25. For how these costs compare across vendors, see our guide to email verification pricing.
Illustrative follow-up: Suppose verification flags another 3% as Invalid. That's 78,080 × 0.03 ≈ 2,342 more contacts removed, leaving about 75,738. A 1% hard-bounce target on the next send allows at most about 757 hard bounces.
Bottom line: Remove the 2.4% of address failures, keep the 0.25% policy group in place while you fix the cause, and note that Pro is the plan that fits a list this size.
How do you prevent these bounce codes at capture?
Prevention works where addresses enter your system. Three measures cover most of the codes above.
- Validate at signup. Use real-time email validation so typos and dead domains are caught before they're stored. Through the email verification API, you can check single addresses in real time or send batches of up to 10,000 emails per request. Pro includes 100,000 API emails a month, or ten full batches. A form that gets 3,000 signups a month uses 3% of that allowance. This fits into broader email verification API and automation workflows.
- Authenticate your sending. Google's sender requirements call for SPF, DKIM and DMARC for bulk senders who send more than 5,000 messages a day to Gmail addresses. Missing authentication is a common cause of 5.7.26-type rejections.
- Re-verify on a schedule. Check active lists monthly and dormant lists quarterly. The list maintenance schedule lays out the cadence. Verification confirms an address can receive mail, not that the person agreed to receive it. The email verification compliance and hygiene guide covers that difference.
Bottom line: Validate at signup, authenticate your sending and re-verify on a schedule. Together these prevent most address-level bounces from reaching a campaign.
What mistakes make bounce problems worse?
- Retrying 5.1.1 and 5.1.2 addresses. These don't recover, and each retry adds to your bounce rate.
- Deleting 5.7.1 addresses. You lose engaged contacts and leave the blocklist or authentication cause in place.
- Trusting "delivered" on catch-all domains. Late NDRs show the mailbox may not exist.
- Resending the full list after a 4.7.0 response. Throttling gets worse with volume, so slow the sends first.
- Reading only the ESP's summary label. The grouping can hide a policy block inside a "hard" bucket.
- Guessing corrected addresses. A fixed typo may still belong to someone else.
- Losing suppression history during a migration. Export it with the contact file, or the bounced addresses will return.
- Letting Free-plan results expire. Results are kept for 24 hours on Free, so download them the same day.
Bottom line: Most worsening comes from acting on the summary label instead of the code, its text and its persistence.
How we compared (and limitations)
This guide is based on public documentation: the SMTP and status-code RFCs cited above, Google's sender guidance and Amazon SES's published thresholds. We have not run controlled tests against any receiving provider or ESP. Reply text varies between providers and changes without notice, so treat code meanings as typical, not guaranteed. The 2% and 1% targets and the three-send suppression rule are our recommendations, not platform requirements. Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's stated figure, not an independent benchmark. The worked-example counts are hypothetical.
Bounce codes at a glance
| Code | Type | Action |
|---|---|---|
| 5.1.1 | Hard | Suppress address now |
| 5.1.2 | Hard | Suppress domain, check typos |
| 4.2.2 | Soft | Retry, suppress after repeats |
| 4.7.0 | Soft | Slow sending and retry |
| 5.7.1 | Policy | Fix authentication and reputation |
Frequently asked questions
What does SMTP bounce code 5.1.1 mean?
SMTP 5.1.1 means the recipient mailbox does not exist at the receiving server. It is a permanent failure, so retrying will not work. Remove the address from your list, and check the source of the address for typos or outdated imports.
What does bounce code 5.1.2 mean?
Code 5.1.2 means the destination domain or host could not be found, or it has no mail server. It is permanent. Suppress the whole domain and check for misspellings such as gmial.com or an expired domain.
Should I retry emails that bounce with 4.2.2?
Usually yes, at least for a while. Code 4.2.2 means the mailbox is full, which is temporary and often clears on its own. Suppress the address only after repeated failures across several sends.
What is the difference between a hard and soft bounce?
A hard bounce is a permanent 5.x.x failure, such as a nonexistent address. A soft bounce is a temporary 4.x.x failure, such as a full mailbox or a server being busy. Hard bounces should be removed immediately, while soft bounces should be retried.
What does bounce code 5.7.1 mean?
Code 5.7.1 is a security or policy rejection. The receiver blocked the message, often because the sending IP is listed on a blocklist, authentication such as SPF, DKIM or DMARC is missing or failing, or content triggered a filter. Removing addresses will not fix it.
How do I find the bounce code for a failed email?
Check the non-delivery report (NDR) your ESP or mail server received, or the bounce log in your sending platform. The code appears in the SMTP reply text, usually in the form 5.1.1 or 550 5.1.1. Many platforms summarize it, so open the raw error for the exact code.
Why do I get bounces to addresses that were valid before?
Addresses go stale when people leave jobs, close accounts or change providers. Purchased or old lists also decay over time. Re-verify lists regularly and suppress addresses that have hard bounced.
Can a bounce rate hurt my deliverability?
Yes. High bounce rates signal poor list quality to mailbox providers and can reduce inbox placement. Keeping hard bounces low by removing invalid addresses before sending is one of the most effective protections.
Is a 550 error the same as a 5.1.1 code?
Not exactly. The 550 is the basic SMTP reply code, and 5.1.1 is the enhanced status code that explains the reason. Receivers often send both together, such as 550 5.1.1, so the enhanced code gives the more specific cause.
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.