Article
Enhanced SMTP Status Codes List: Meaning, Format and Fixes
By Unlimited Verifier Team ·

Summary
An enhanced SMTP status code is a three-part code such as 5.1.1 or 4.7.0 that explains why a mail server rejected or delayed a message. The first digit shows success, temporary failure or permanent failure, the second the category, and the third the specific reason. Use it to tell dead addresses apart from sender-side blocks.An enhanced SMTP status code is a three-part code such as 5.1.1 or 4.7.0, defined in RFC 3463, that a receiving mail server attaches to a delivery reply to say what went wrong and whether to retry. The first digit gives the outcome, the second the category and the third the specific reason.
Quick answer
- Format:
class.subject.detail. The first digit is the outcome:2success,4temporary failure (retry),5permanent failure (hard bounce). - Address-level failures to suppress now:
5.1.1(unknown mailbox),5.1.2(domain or host not found),5.1.3(bad address syntax) and5.2.1(mailbox disabled). These mean the address itself is dead. - Most often misread:
5.7.xand4.7.x. These are policy or reputation decisions about your sending, so deleting addresses won't fix them. - Where to find it: the reason text in your ESP's bounce log, or the Diagnostic-Code field of a delivery status notification.
- Act on it: suppress address-level failures, re-verify ambiguous contacts, and fix authentication and sending volume for
5.7.x.
What is an enhanced SMTP status code?
An enhanced status code is a finer-grained status that sits alongside the three-digit SMTP reply code. The reply code (such as 550 or 421) comes from RFC 5321 and tells the sending server whether a command failed temporarily or permanently. The enhanced code adds the reason: a bad address, a full mailbox, a network fault or a policy decision.
The extension is defined in RFC 2034. A server advertises it with the ENHANCEDSTATUSCODES keyword in its EHLO response. In practice, most major mailbox providers include enhanced codes in their replies, though not every server does.
The reply code alone can't tell you whether an address is dead. Compare these two replies:
550 5.1.1 <jane@example.com>: Recipient address rejected: User unknown550 5.7.1 Message rejected due to sender reputation
Both use 550 and both are hard failures. Only the first means the address is dead. The second means the receiving server rejected your mail, and the address may be perfectly valid.
Bottom line: The enhanced code is the most reliable way to separate a dead address from a sender-side block in the same bounce log.
How do you read an enhanced status code?
Read the code as three questions: what happened (class), who has to act (subject) and why (detail).
- Class (first digit):
2success,4persistent transient failure (retry later),5permanent failure (do not retry). - Subject (second digit):
0other or undefined,1addressing,2mailbox,3mail system,4network and routing,5mail delivery protocol,6message content or media,7security or policy. - Detail (third part): the specific condition within that subject.
So 5.1.1 reads as "permanent failure, addressing, bad destination mailbox." And 4.7.0 reads as "temporary failure, security or policy, other or undefined." In practice, a 4.7.0 is often a temporary throttle, which is why retrying later usually works.
The subject digit is a useful shortcut for ownership. A 1 usually points to your list. A 4 usually points to DNS, MX or routing. A 7 usually points to your authentication and sending reputation. A 2 often means the recipient's mailbox is full or disabled.
Bottom line: Read the class to decide on retry logic, and read the subject to see who owns the fix.
What is the full enhanced SMTP status codes list?
RFC 3463 defines the full code space, but a list owner sees a small set of codes again and again. The first table covers the subject categories. The second covers the codes that drive list-hygiene decisions.
Subject categories at a glance
| Subject digit | Category (RFC 3463) | Examples | Usual owner of the fix |
|---|---|---|---|
| 0 | Other or undefined | 5.0.0, 4.0.0 |
Read the full text |
| 1 | Addressing | 5.1.1, 5.1.2, 5.1.3 |
List owner |
| 2 | Mailbox | 5.2.1, 5.2.2, 4.2.2 |
List owner or recipient |
| 3 | Mail system | 5.3.4, 4.3.1 |
Recipient's provider |
| 4 | Network and routing | 4.4.1, 4.4.7, 5.4.6 |
DNS, MX or forwarding setup |
| 5 | Mail delivery protocol | 5.5.1, 5.5.2, 5.5.3 |
Your sending software |
| 6 | Message content or media | 5.6.1, 5.6.2 |
Message content |
| 7 | Security or policy | 5.7.1, 5.7.26, 4.7.0, 4.7.28 |
Sender reputation and authentication |
The codes you will see most often
| Code | Meaning | Class | Action |
|---|---|---|---|
5.1.1 |
Bad destination mailbox (user unknown) | Hard | Suppress permanently |
5.1.2 |
Bad destination system (domain or host not found) | Hard | Suppress; check the domain for typos |
5.1.3 |
Bad destination mailbox syntax | Hard | Suppress; fix the capture form |
5.1.4 |
Destination address ambiguous | Hard | Suppress the duplicate alias |
5.1.6 |
Destination mailbox has moved | Hard | Suppress; request a new address |
5.2.1 |
Mailbox disabled, not accepting messages | Hard | Suppress |
5.2.2 |
Mailbox full (permanent reply) | Hard by reply; address may be valid | Hold out of primary sends; re-verify |
5.2.3 |
Message exceeds the recipient's size limit | Hard | Reduce attachment or file size |
5.5.3 |
Too many recipients | Hard | Send in smaller batches |
5.7.1 |
Delivery not authorised, message refused | Hard by reply; policy decision | Diagnose the sender; keep the address |
5.7.26 |
Gmail: unauthenticated mail blocked by the domain's DMARC policy | Hard | Fix SPF, DKIM and DMARC alignment |
4.2.2 |
Mailbox full (temporary) | Soft | Retry; escalate if it repeats |
4.4.1 |
No answer from host | Soft | Retry; check MX records |
4.4.7 |
Delivery time expired | Soft until queue expiry | Investigate repeated expiries |
4.7.0 |
Temporary security or policy failure, often throttling | Soft | Slow down; retry later |
4.7.1 |
Delivery not authorised (temporary) | Soft | Check authentication and reputation |
4.7.28 |
Gmail: unusual rate of unsolicited mail from your sending IP | Soft | Reduce volume and complaint exposure |
5.7.26 and 4.7.28 are provider extensions. Google documents them in its public error text, but other receivers may not use them. Microsoft 365 also uses its own 5.7.x sub-codes, so the reason text often matters more than the number.
For the reply-code side, see our guides to 550 5.1.1 user unknown, 554 5.7.1, 421 4.7.0 and 550 5.1.2 bad destination host. For a broader reference with plain-English meanings, see SMTP error codes list with meanings, and for the ten codes marketers meet most, see 10 SMTP error codes every email marketer should know.
Bottom line: About ten codes cover most list-hygiene decisions. Learn the 5.1.x, 5.2.1, 5.2.2 and 5.7.x families first.
Which enhanced codes are hard bounces and which are soft?
The class digit sets the default: 5 is permanent (hard) and 4 is transient (soft). But the class describes what the server intended on that one attempt. It does not tell your database what to conclude about the address. For the reply-class side of this, see 4xx vs 5xx SMTP errors.
Most platforms treat any 5xx as a hard bounce and retry 4xx for a limited period. Your own database should track two separate things: the reply class and an address verdict. Triage in this order:
- Read the class. A
5is a candidate for suppression. A4is a candidate for retry. - Check the address-level codes.
5.1.1,5.1.2,5.1.3,5.1.4,5.1.6and5.2.1are verdicts on the address. Suppress them immediately. - Check for sender-side codes.
5.7.xand4.7.xthat appear across many receiving domains are about how you send. Do not suppress the addresses. - Count repeats. A soft bounce that repeats across sends becomes a verdict on the address.
Our recommended policy, based on the RFC definitions and provider documentation:
- Suppress immediately:
5.1.1,5.1.2,5.1.3,5.1.4,5.1.6,5.2.1. - Quarantine (no more sends, then verify):
5.2.2,4.2.2, and any4.xthat repeats. - Fix the sender, keep the address:
5.7.xand4.7.xspread across many domains.
Suppression is part of email verification compliance and hygiene. Once an address is confirmed dead, it should never receive another campaign. Sources also disagree on how many soft bounces should convert to a suppression. We recommend three soft bounces on three separate sends, with no successful delivery in between. This is our judgement rather than a standard, and some ESPs use a time window instead, so check your platform's rule before relying on ours.
Bottom line: Treat the reply class as one server's verdict on one attempt, and keep your own verdict on the address.
Why do 5.7.x and 4.7.x codes need a different fix?
The security or policy subject (7) is where list owners most often misdiagnose a problem. A 5.7.1 on a freshly verified list often means the receiver judged your mail, not your addresses.
Three checks will separate a sender problem from a list problem:
- Group
7-family bounces by receiving domain. If most come from one provider, that provider's policy or reputation view of you is the likely cause. If they are spread across many providers, look at your authentication and content. - Verify authentication. Google's sender guidelines ask bulk senders (generally those sending 5,000 or more messages a day to Gmail) to authenticate mail with SPF or DKIM and publish a DMARC policy. They also ask you to keep the user-reported spam rate below 0.10% in Postmaster Tools and never reach 0.30%. These are Google's published figures, and other providers set their own.
- Check reputation directly. Google Postmaster Tools shows domain and IP reputation, spam rate and authentication results for Gmail traffic. Use it to confirm a
5.7.xpattern before you change anything.
The common mistake is to suppress these addresses. You remove contacts who may be fine, and you leave the real cause, usually authentication or volume, untouched.
Bottom line: A 7 in the subject digit means "fix how you send." Cleaning the list will not clear it.
How do you find the enhanced code in your bounce data?
Each data source keeps a different amount of detail. Check which one you have before you start classifying.
| Source | Where to find it | Includes enhanced code? | Best for |
|---|---|---|---|
| ESP bounce or activity export | Platform dashboard, CSV export | Often in the reason field; some exports summarise to "hard bounce" | Bulk counting |
| Delivery status notification (DSN) | Return-path mailbox | Yes, in the Diagnostic-Code field, per RFC 3464 | Investigating single messages |
| Mail server logs | Your MTA, such as Postfix status lines | Yes, with the server's full response | Engineers debugging delivery |
| Google Postmaster Tools | Google's web dashboard | No per-message codes; shows reputation trends | Confirming 5.7.x patterns |
The most common hidden problem is an ESP export that keeps only a summary such as "Hard bounce" and drops the raw text. Some servers also omit enhanced codes entirely. If a bounce has no recognisable code, fall back to the three-digit reply and the reason text, and set those rows aside for manual review. Don't guess.
Bottom line: No code, no classification. Confirm your export includes the raw reason text before you build any suppression list.
How do you classify a bounce log in Unlimited Verifier?
This process takes about 30 minutes for a log of tens of thousands of bounces, most of which is spent on the export.
- Export the raw bounce log from your ESP, with columns for the email address and the full reason text. Name the reason column
reason, or rename it before step 2. - Extract the codes with a short script. It counts each enhanced code it finds:
import csv, re
from collections import Counter
# Matches enhanced codes such as 5.1.1 or 4.7.0.
# Skips IP fragments like 10.5.1.1 and longer numbers like 5.1.1.2.
CODE = re.compile(r'(?<![\d.])([245])\.(\d{1,3})\.(\d{1,3})(?!\.?\d)')
counts = Counter()
with open('bounces.csv', newline='', encoding='utf-8') as f:
for row in csv.DictReader(f):
m = CODE.search(row.get('reason') or '')
counts[m.group(0) if m else 'no-code'] += 1
for code, n in counts.most_common():
print(code, n)
The lookarounds matter. Without them, a plain pattern matches 5.1.1 inside an IP address such as 10.5.1.1 and inflates your counts. The negative lookahead also stops a match from swallowing the first part of a longer number.
- Build two files. The suppression file holds addresses that returned
5.1.xor5.2.1. The verification file holds addresses that returned5.2.2or a repeated4.x. Each file needs anemailcolumn. Rows with no recognisable code go to manual review first, not into verification. - Sign up if you don't have an account. The Free plan covers 25 lists a month of up to 150 emails each.
- Upload the verification file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Read the three buckets. Valid addresses can return to a low-volume send. Invalid addresses join your suppression list. Risky addresses, such as catch-all, disposable or role accounts, stay out of sends for now. For catch-all domains specifically, see catch-all email verification.
- Export the results as CSV, Excel or JSON. Add Invalid addresses to your ESP's suppression list and create a new segment from Valid addresses. Unlimited Verifier has no native ESP integrations, so re-import the files manually. Results are kept for 24 hours on Free and 30 days on Pro, so save your own copy of each export.
- Repeat monthly. If you want the same check inside your own systems, the email verification API is available on Pro, with 100,000 emails a month and bulk requests of up to 10,000 emails. For the workflow patterns, see email verification API and automation. To stop new
5.1.1bounces at the source, add real-time email validation to your sign-up forms.
Before you choose a tool for this, compare the criteria in how to choose an email verifier and the best email verification tools roundup. For a broader cleaning routine, see email list maintenance best practices.
Bottom line: Extract the codes, suppress the dead addresses, verify the ambiguous ones, and re-import only what comes back Valid.
What does classifying 10,000 bounces look like?
This example is illustrative. The counts and results are hypothetical, but the arithmetic and plan limits are real.
A B2B SaaS team sends a product newsletter and gets 10,000 bounces in one month. The raw reason text breaks down like this:
| Code group | Count | Share | Action |
|---|---|---|---|
5.1.1 unknown mailbox |
6,200 | 62% | Suppress |
5.7.1 / 5.7.26 policy and authentication |
1,400 | 14% | Fix authentication and volume; keep addresses |
4.2.2 / 4.7.0 repeated soft bounces |
1,100 | 11% | Verify |
5.2.2 mailbox full |
400 | 4% | Hold out of sends; verify |
4.4.x network and routing |
200 | 2% | Check DNS and MX |
| Other or no code | 700 | 7% | Review manually |
Check: 6,200 + 1,400 + 1,100 + 400 + 200 + 700 = 10,000.
Step 1: Suppress the dead addresses. The team suppresses the 6,200 addresses in the 5.1.1 group. This is the largest and clearest action.
Step 2: Verify the ambiguous addresses. The verification list is 1,100 + 400 = 1,500 addresses.
- On the Free plan, 1,500 ÷ 150 = 10 lists. That fits within the 25-list monthly allowance, but it means ten manual uploads.
- On Pro, the same 1,500 addresses fit in one list, well under the 25,000-email list cap.
- Standard verification is unlimited on every plan. Deep verification is capped at 750 a month on Free, so checking all 1,500 addresses deeply requires Pro's 25,000 deep verifications.
Assume the results come back as Valid 1,020 (68%), Risky 330 (22%) and Invalid 150 (10%). Check: 1,020 + 330 + 150 = 1,500.
Step 3: Act on the buckets.
- Add the 150 Invalid addresses to suppression. Total suppressions from this bounce log: 6,200 + 150 = 6,350.
- Send the 1,020 Valid addresses in a low-volume test.
- Hold the 330 Risky addresses until the main list shows stable delivery.
- Leave the 1,400
5.7.xaddresses alone. Fix authentication and check Google Postmaster Tools before the next send.
Step 4: Check the cost. Pro is $29 a month, or $25 a month billed annually ($300 a year). If you use the full 25,000 deep-verification quota, the monthly plan works out to about $1.16 per 1,000 deep checks ($29 ÷ 25), and the annual plan to $1.00 per 1,000 ($25 ÷ 25). For how verification costs compare across vendors, see email verification pricing.
Bottom line: The biggest win came from suppressing 6,200 dead addresses. The second came from not suppressing the 1,400 policy bounces that were never caused by the list.
What are the most common mistakes with enhanced status codes?
- Reading only the three-digit code.
550covers both5.1.1and5.7.1, which need opposite actions. - Suppressing every
5.xcode. This removes valid contacts and hides the real problem, which is usually sender reputation or authentication. - Treating
4.xas harmless. A4.xthat repeats across sends points to a list or infrastructure problem.4.4.7means the message expired in the queue. - Retrying
5.1.1addresses "to be safe." Every retry to a dead mailbox adds another bounce to your rate. - Assuming codes match across providers. Google's
5.7.26and4.7.28are not used by every receiver, and Microsoft 365 uses its own sub-codes. - Matching IP fragments by mistake. A naive pattern reads
10.5.1.1as5.1.1. Use the lookarounds in the tutorial script. - Relying on a summary label. "Hard bounce" tells you the class, not the reason.
- Verifying before fixing the cause. Cleaning the list will not clear a
5.7.1caused by failed authentication.
Our pillar guide to email bounce codes covers how these codes feed into bounce-rate limits and account reviews. For the 4.x side in more depth, see common soft bounce reasons. If you keep seeing unexplained bounces from mailer daemons, why you keep getting mailer-daemon bounce messages covers the most common causes.
Bottom line: Most bounce mistakes come from treating one digit or one label as the whole story.
How we compared (and limitations)
This article is based on public documentation: RFC 3463 for the enhanced status code structure, RFC 5321 for reply codes, RFC 2034 for the enhanced-codes extension, RFC 3464 for delivery status notifications, and public help text from Google. Provider-specific codes come from published documentation, not from controlled tests. We have not run tests against any ESP or receiving server.
Provider codes and error text change over time, so check the current wording in your own logs. Our suppression thresholds (three soft bounces across three sends) reflect our judgement, not a standard, and ESPs use different rules.
Unlimited Verifier's 99.5% accuracy figure for deep verification is the company's stated figure, not an independent benchmark. The worked-example counts and results are hypothetical.
Triage: which code, which action
| Code | Meaning | Action |
|---|---|---|
| 5.1.1 | Unknown mailbox | Suppress address |
| 5.1.2 | Domain or host not found | Suppress address |
| 5.2.1 | Mailbox disabled | Suppress address |
| 4.2.2 | Mailbox full (temporary) | Retry later, monitor |
| 4.7.0 | Temporary policy or throttle | Slow sending, retry |
| 5.7.1 | Policy or reputation rejection | Fix authentication and sending practices |
Frequently asked questions
What does 5.1.1 mean in an SMTP bounce?
5.1.1 means a permanent failure related to addressing, specifically that the recipient mailbox does not exist. The address is invalid, so you should remove it from your list and stop sending to it. Retrying will not succeed.
What is the difference between 4.x.x and 5.x.x codes?
A 4.x.x code is a temporary failure, so the sending server should retry later. A 5.x.x code is a permanent failure, so the message should not be retried. The first digit sets whether delivery attempts continue.
What does 5.7.1 mean?
5.7.1 is a permanent security or policy rejection. The receiving server has refused the message for reasons tied to your sending, such as authentication, reputation or content. Deleting the recipient address usually won't fix it.
Where can I find the enhanced status code for a bounce?
Check the reason text in your email service provider's bounce or delivery log. You can also find it in the Diagnostic-Code field of a delivery status notification (DSN), which is a standard bounce message format.
Is RFC 3463 the same as RFC 2034?
No. RFC 2034 defines the SMTP extension that adds enhanced status codes and the ENHANCEDSTATUSCODES keyword. RFC 3463 defines the actual code values and their meanings. Both are needed to understand the full system.
Do all mail servers return enhanced status codes?
No. Enhanced codes are optional and depend on the server advertising support in its EHLO response. Most major mailbox providers include them, but smaller or older servers may return only the basic three-digit reply code.
Should I retry messages that return a 4.x.x code?
Usually yes, because 4.x.x codes signal a temporary condition that often clears. However, if the same address keeps returning 4.x.x over several days, treat it as a persistent problem and investigate instead of retrying indefinitely.
Why does 5.7.x need a different response than 5.1.x?
5.1.x codes point to a bad recipient address, so the fix is list hygiene. 5.7.x codes point to a decision about your sending, so the fix is authentication, volume, content or reputation. Removing addresses won't resolve a 5.7.x block.
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.