Article

SMTP Error Codes List with Meanings: Basic and Enhanced Codes Explained

By Unlimited Verifier Team ·

Diagram of an SMTP error code 550 5.1.1 showing the permanent failure digit and the enhanced address code that explains the SMTP error meaning.

Summary

SMTP error codes are three-digit replies from a receiving mail server: 2xx accepts, 4xx defers and retries later, and 5xx permanently refuses. The enhanced status code, such as 5.1.1 or 5.7.1, explains the specific reason and tells you whether the problem is the address or your sending.

SMTP error codes are the three-digit replies a receiving mail server sends when it accepts, defers or rejects a message: 2xx means accepted, 4xx means try again later, and 5xx means permanently refused. Most modern bounce reports also include an enhanced status code such as 5.1.1, which names the specific reason. This guide lists the codes you will meet most often, explains what each one means, and shows what to do about it. For the wider picture, start with our email bounce codes overview.

Quick answer

What are SMTP error codes and how are they structured?

SMTP error codes follow a fixed grammar defined in RFC 5321. Each reply has two layers, and most people only read the first.

The basic reply code is three digits:

The enhanced status code takes the form class.subject.detail, defined in RFC 3463:

Read 550 5.1.1 this way: 5 is a permanent failure, 5 is the mail system category, and 0 is the syntax digit in the basic code. The enhanced code then says 5.1 addressing and .1 the mailbox does not exist. Log the enhanced code, because providers often reuse the same basic code for different problems. For a full reference, see our enhanced SMTP status codes list.

Bottom line: Log the enhanced code, not just the three-digit reply, because it tells you whether the problem is the address, the mailbox or your sending.

Why does the same SMTP code mean different things at different providers?

The basic codes are standardised, but the text after them is not, and providers apply enhanced codes unevenly. A 550 from one server can mean a missing mailbox, while a 550 from another can mean your IP is blocked. Wording is written for administrators, and many providers link to their own help pages inside the message.

This gap causes most misclassified bounces. For example, a 550 5.1.1 user unknown reply is strong evidence that an address is dead, but a 550 with a 5.7.x code is evidence about your sending.

Two patterns recur. Providers return 5.7.x policy codes for reputation, authentication or content decisions, which say nothing about whether the recipient exists. And some servers return a 5.1.x address code when the real cause is routing or DNS. When the codes and your sending data disagree, check your side before you suppress anyone.

Bottom line: A code tells you what the server decided, not always why. Cross-check the enhanced code against the bounce text and your own sending data.

What does each common SMTP error code mean?

The table covers the codes list owners and marketers see most. The "Bucket" column is the handling decision, which the decision table later in this guide expands on.

Code (basic + enhanced) Meaning Typical cause Bucket
421 4.7.0 Service temporarily unavailable; connection closed Throttling, or reputation-based deferral (Gmail has used this text for temporary deferrals) Retry
450 4.2.1 Mailbox unavailable or busy Recipient receiving mail too fast; rate limits Retry, slow down
450 / 451 4.7.1 Temporary deferral Commonly greylisting, often with a "try again later" message Retry
451 4.3.0 Local processing error on receiving server Server-side fault Retry
452 4.2.2 Mailbox full (transient) Recipient over quota Retry, suppress if repeated
452 4.5.3 Too many recipients in one transaction Batch too large for the server Split batch
500 / 501 Syntax error in command or parameters Malformed sending software or headers Fix your sender
503 Bad sequence of commands Client-side SMTP fault Fix your sender
530 5.7.0 Authentication required Unauthenticated sending Fix authentication
535 5.7.8 Authentication credentials invalid Wrong SMTP username or password Fix credentials
550 5.1.1 Mailbox does not exist ("user unknown") Typo, closed account, dead address Suppress
550 5.1.2 Bad destination host or system Domain or host not found Check domain, then suppress
553 5.1.3 Bad destination mailbox syntax Address breaks syntax rules Suppress
552 5.2.2 Mailbox full (permanent wording) Quota exceeded, sometimes persistent Retry, suppress if repeated
552 5.3.4 Message too big Attachments or images push size over the limit Reduce size
554 5.4.4 Unable to route DNS or routing failure Check domain
550 5.7.1 Refused on policy or reputation Blocklisting, spam signals, unsolicited-mail rules Investigate
550 5.7.26 Unauthenticated sender Missing or failing SPF, DKIM or DMARC for the sending domain Fix authentication
554 5.7.9 Message not accepted for policy reasons Policy decision; Yahoo has used this wording Investigate

Two rows need more explanation. The 5.1.2 row is often misread, because it describes the destination host, not the individual person. Its failures usually show up across every address at one domain. The 552 5.2.2 row is an exception to the rule that 5xx is final. Mailbox-full is the one permanent-class code that many senders treat as soft, because the mailbox can empty. For a deeper look at the 5.7.x family, see what 554 5.7.1 means.

Bottom line: The table gives meanings, but the bucket column is the action, and the action depends on whether the problem sits with the address, the server or your sending.

Which SMTP codes are temporary and which are permanent?

Codes starting with 4 are temporary and codes starting with 5 are permanent. RFC 5321 recommends that a sender keep retrying a temporarily failed message for a long period, at least four to five days, before giving up.

Providers do not all retry on the same schedule, so treat that RFC window as a planning ceiling rather than a promise about any one platform. A 4xx means "this may succeed later." A 5xx means "this will keep failing." Two practical exceptions apply:

The 4xx and 5xx split matters for your database, but so does the enhanced code. For the broader difference, read our 4xx vs 5xx SMTP errors comparison, and for what counts as a soft bounce in practice, see common soft bounce reasons. The 421 4.7.0 and 450 codes both behave as temporary, but their causes differ enough to warrant separate handling.

Bottom line: 4xx means retry and 5xx means stop, with the two exceptions above. Read the enhanced code before you decide.

Should you retry or suppress an address?

The right action depends on the enhanced code's subject and the number of attempts. Use this table as your working rule set.

Enhanced code family Likely cause Action Suppress when
5.1.1, 5.1.3 Address does not exist or is malformed Suppress On the first hard bounce
5.1.2, 5.4.4 Domain or routing failure Check the domain, then act on addresses at it Domain is confirmed dead
5.2.2, 4.2.2 (mailbox full) Quota exceeded Retry on a schedule Three or more soft bounces across separate sends
4.x.x (other) Throttling, greylisting, server fault Retry with backoff Still failing after the retry window
5.7.x (policy, auth, reputation) Your IP, domain or content Investigate and fix the sender Only after the recipient is verified invalid
5.3.4 Message too large Reduce message size Never; the address is fine

The third row is the one that matters most. Our recommendation is to suppress a soft-bouncing address after three or more soft bounces across separate sends, with a retry window of about five days. Platforms set their own rules, so treat three as a working default, not an industry standard.

The 5.7.x row is where list owners go wrong. A policy block tells you about your sending. Suppressing the recipient removes good contacts while the real cause keeps damaging future sends.

Watch for conflicts too. If a 5.1.1 bounce comes back for an address that your verifier marks Valid, don't suppress blindly. Check whether the bounce was a timing issue, a typo on a different form, or a misrouted message. Pair the decision with real-time email validation at signup so bad addresses never reach the list.

Bottom line: Suppress on address evidence, retry on transient evidence, and fix your sender when the code points at policy or authentication.

How do verification tools use SMTP codes?

A best email verification tool checks the SMTP mailbox by opening a conversation with the recipient's mail server and asking whether it will accept mail for that address, without sending a message to the person. The server's reply is what drives the final result. For a checklist when comparing vendors, see how to choose an email verifier.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, and sorts every address into Valid, Risky or Invalid. The company states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark.

Four details matter when you compare a verifier's result against a bounce code:

Compare the two sources. A 5.1.1 bounce that the verifier also marks Invalid is consistent evidence. A 5.1.1 bounce marked Valid deserves a second look.

Bottom line: Treat a verifier's Invalid result and a 5.1.x bounce as corroborating evidence, and treat Risky as a reason to hold an address, not to delete it.

How do you triage a bounce export? A hands-on tutorial

This tutorial uses Google Sheets and Unlimited Verifier. It takes about ten minutes for a few hundred bounces and works the same at larger volumes.

  1. Export the bounce log as a CSV. Use the activity or bounce export from your sending platform. Make sure the full diagnostic text, which includes the code, is in one column. Assume it is in column A.
  2. Open the file in Google Sheets. Paste the formula below into cell B2 to pull out the basic code: =REGEXEXTRACT(A2,"\b[245][0-9]{2}\b")
  3. Extract the enhanced code into column C: =REGEXEXTRACT(A2,"\b[245]\.[0-9]{1,3}\.[0-9]{1,3}\b") If the result is blank, the bounce has no enhanced code, so fall back to the basic code.
  4. Build a lookup tab. On a second sheet called Buckets, list each enhanced code from the table above in column A and its bucket (Suppress, Retry, Investigate or Fix sender) in column B.
  5. Assign buckets in column D: =IFERROR(VLOOKUP(C2,Buckets!A:B,2,FALSE),"Review") Any code not in your lookup tab shows "Review" so nothing gets dropped silently.
  6. Check a sample. Read about 20 rows by eye before trusting the formulas. Regex matches can catch numbers in an address or a timestamp.
  7. Filter and export one CSV per bucket. Each file needs the email, basic code, enhanced code and bucket.
  8. Verify the Suppress and Retry groups. Go to upload and verify a list and drop in each file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Files you export from a Pro account can hold up to 25,000 emails per list. Free lists are capped at 150 emails each, so split larger files first. Standard verification is included on every plan.
  9. Export results before they expire. Unlimited Verifier keeps results for 24 hours on the Free plan and 30 days on Pro. Export as CSV, Excel or JSON as soon as each run finishes.
  10. Reconcile and act. Where a bounce says Invalid and the verifier says Valid, investigate. Where both agree, suppress. Schedule the Retry group and log the Investigate group against a ticket.

If you are seeing Mailer-Daemon messages in your own inbox rather than in a platform report, why do I keep getting Mailer-Daemon bounce messages explains where they come from.

Bottom line: Extract the enhanced code, bucket it, and verify before you suppress, so each address gets the action its evidence supports.

What does triage look like for 4,000 bounces?

The figures below are illustrative, built to show the arithmetic.

A list owner sends a campaign to 50,000 contacts and gets 4,000 bounces, an 8% bounce rate. After bucketing, the codes split like this:

Bucket Codes Count Share of bounces Share of sent
Suppress 550 5.1.1, 550 5.1.2 2,200 55% 4.4%
Retry 452 4.2.2, 421 4.7.0 600 15% 1.2%
Investigate 550 5.7.1, 554 5.7.9 900 22.5% 1.8%
Fix sender 530 5.7.0, 552 5.3.4 300 7.5% 0.6%

The arithmetic points one way. The hard-address group alone is 4.4% of everything sent. That is more than double the 2% ceiling we recommend, so the list has a real hygiene problem, not a one-off blip. The bucket counts add back to 4,000 (2,200 + 600 + 900 + 300), and each share checks out against the 50,000 sent.

The 900 5.7.1 and 5.7.9 bounces should not be suppressed on sight. They point to a reputation or content problem. Suppressing those contacts would delete good people while the underlying cause keeps hurting future sends.

Handling it on Unlimited Verifier:

Result: Suppress the 2,200 addresses the verifier also marks Invalid, hold the 600 for retries, and fix authentication and content before sending to the 900 policy-bounced addresses again.

Bottom line: Separate address failures from sender failures first. Only the first group is a list-cleaning problem.

How long should you keep retrying a soft bounce?

Keep retrying for a few days, and never retry indefinitely. RFC 5321 describes a retry period of at least four to five days for queued mail. That guidance is for message delivery between servers, not a rule for managing your list.

Where sources disagree, we recommend one number. For a marketing list, use three soft bounces across separate sends, or a retry window of about five days, whichever comes first. Mailbox-full and greylisting cases usually clear inside that window. Anything still failing afterwards is effectively dead, and a longer window only inflates your bounce rate without adding reach. For how repeated soft bounces fit into list hygiene, see our guide to email list maintenance best practices.

Bottom line: Retry for a few days, then suppress. Indefinite retries do not recover reach.

What mistakes do people make with SMTP error codes?

Bottom line: Most errors come from reading the three-digit reply without the enhanced code, or treating a sender problem as a recipient problem.

How we compared (and limitations)

This guide is based on public documentation: RFC 5321 for the SMTP reply grammar, RFC 3463 for enhanced status codes, RFC 3464 for delivery status notifications, and the postmaster guidance from Google and Yahoo. We have not run tests against any provider's live mail system.

Provider wording changes without notice, and the same code can carry different text on different servers. The example text in the table is indicative. Where providers disagree on how to classify a code, we recommend one approach and explain why. The three-soft-bounce threshold and the five-day window are working defaults, not an industry standard.

The Unlimited Verifier figures come from the company's published plan details. The 99.5% accuracy figure is the company's stated number for deep verification and has not been independently verified here. The worked example is illustrative, and its percentages are hypothetical.

Quick triage of common SMTP codes

Code Outcome Typical meaning Action
421 Temporary (4xx) Service unavailable Retry automatically
452 Temporary (4xx) Storage or too many recipients Retry, then batch
550 5.1.1 Permanent (5xx) Mailbox does not exist Suppress address
550 5.7.1 Permanent (5xx) Policy or reputation block Investigate sending
554 Permanent (5xx) Generic refusal Read enhanced code and text
535 Permanent (5xx) Authentication failed Fix credentials

Frequently asked questions

What does SMTP error code 550 mean?

A 550 reply is a permanent failure, meaning the receiving server refused the message and will not accept a retry. The meaning depends on the enhanced code that follows, such as 5.1.1 for an unknown mailbox or 5.7.1 for a policy or reputation block.

What is the difference between a 4xx and a 5xx SMTP error?

A 4xx error is a temporary failure, so the sending server should retry the message later. A 5xx error is a permanent failure, so the sender should stop retrying and handle the message as undeliverable.

What does SMTP error 421 mean?

A 421 reply means the service is not available, usually because the server is closing the connection or is overloaded. It is a 4xx temporary failure, so the message should be queued and retried automatically.

What does SMTP error 452 mean?

A 452 reply is a temporary failure indicating insufficient system storage or too many recipients in one transaction. Retry later, and if it persists, split large recipient lists into smaller batches.

What does SMTP error 554 mean?

A 554 reply is a generic permanent failure, often returned when the transaction fails for policy, spam or content reasons. Check the enhanced code and the server's text to find the exact cause.

What does SMTP error 535 mean?

A 535 reply means authentication failed, usually due to wrong credentials or a misconfigured login method. Verify your username, password and authentication settings with your mail provider.

Should I remove an address after a 5.7.1 bounce?

Not automatically. A 5.7.1 code usually points to your sending reputation, IP block or policy rule rather than a bad address, so investigate your sending first and suppress the address only if other evidence confirms it is invalid.

Where can I find the full list of enhanced SMTP status codes?

The enhanced status code structure is defined in RFC 3463, and the basic reply codes are defined in RFC 5321. Major mail providers also publish their own bounce documentation that explains how they apply these codes.

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 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.