Article

10 SMTP Error Codes Every Email Marketer Should Know (With Actions)

By Unlimited Verifier Team ·

Diagram showing how an email marketer reads an SMTP bounce's reply code, enhanced status code and text to choose between retrying and suppressing.

Summary

The SMTP error codes that matter most for email marketers are 550 5.1.1, 550 5.1.2, 553 5.1.3, 554 5.7.1 and six others covering full mailboxes, throttling, deferrals, access blocks and login failures. Each code calls for a different action: suppress permanent recipient failures, correct malformed addresses, retry temporary deferrals, and investigate policy refusals.

The ten SMTP error codes every email marketer should know are 550 5.1.1 and 550 5.1.2 (permanent recipient or domain failures), 553 5.1.3 (malformed address), 554 5.7.1 (policy refusal), and six more covering full mailboxes, throttling, temporary deferrals, access blocks and login failures. Each one calls for a different action, and 554 5.7.1 is the one most often misread. This guide covers all ten for list owners, agencies and SaaS teams cleaning large databases for deliverability and compliance. For the wider framework, start with our email bounce codes guide.

Quick answer

Which SMTP error codes matter most for email marketers?

Read three parts of every bounce: the reply code, the enhanced code and the text. The first digit of the reply code is the most important signal. Under RFC 5321, a 4xx reply is temporary and a 5xx reply is permanent. The enhanced code, such as 5.1.1, adds the subject: 5 is permanent and 4 is transient, and the middle number identifies the category (addressing, mailbox, routing, policy or security). For a deeper walkthrough, see 4xx vs. 5xx SMTP errors and the enhanced status code list.

Quick picks by situation

Code What it means Hard or soft First action
550 5.1.1 Mailbox doesn't exist Hard Suppress
550 5.1.2 Domain or host can't be reached Hard (domain-level) Confirm mail server, suppress domain
553 5.1.3 Address syntax invalid Hard Correct or suppress
552 5.2.2 Mailbox full Permanent code; often treated as soft Retry, then apply your written rule
450 4.2.1 Mailbox temporarily not accepting mail Soft Retry
450 4.7.1 Greylisting or temporary policy deferral Soft Retry
421 4.7.0 Throttled or reputation-limited Soft (warning if persistent) Slow down, check reputation
554 5.7.1 Refused for policy or blocking Policy (address may be valid) Investigate sender
535 5.7.8 Login credentials rejected Sender-side Fix credentials
550 5.4.1 "Access denied" for recipient Usually hard; wording varies Check single addresses vs. whole domain

Bottom line: the reply code sets the timing, the enhanced code sets the subject, and the table above is a default to test against your own logs.

How we compared these codes (and limitations)

This comparison is based on public documentation: the SMTP standards and common provider behavior. We judged each code on four criteria:

  1. Frequency in marketing sends: codes that commonly appear in ESP bounce reports and list-cleaning work.
  2. Decision difference: codes where the right action is clear and where marketers often act incorrectly.
  3. Standards grounding: each code is defined in RFC 5321 (reply codes), RFC 3463 (enhanced status codes) or RFC 4954 (SMTP authentication), or is documented by a major mailbox provider.
  4. Coverage: recipient, domain, policy and sender-side failures, so no single category dominates the list.

Limitations. We did not analyze a bounce dataset, so we make no claim about how often each code appears on your list. Receiving servers word messages differently and sometimes omit enhanced codes. The same code can mean different things at different providers, and vendors don't always use enhanced codes as the RFCs define them. Thresholds such as the 1% hard-bounce target are recommendations, because no single number is standardized across providers. If you use a verification tool, its accuracy figures are the vendor's claims. For example, Unlimited Verifier states 99.5% accuracy for deep verification; test any claim on a sample of your own list.

Bottom line: the codes and enhanced codes tell you more than the text, but neither replaces reading your own bounce logs.

What are the 10 SMTP error codes every email marketer should know?

Each entry covers what the code means, whether it's hard or soft, what usually triggers it, what to do, and where marketers go wrong.

1. 550 5.1.1: Mailbox doesn't exist

For the full breakdown, see 550 5.1.1 user unknown meaning.

2. 550 5.1.2: Bad destination host or domain

See 550 5.1.2 bad destination host meaning for more on domain-level failures.

3. 553 5.1.3: Invalid address syntax

4. 552 5.2.2: Mailbox full

Related reading: common soft bounce reasons.

5. 450 4.2.1: Mailbox temporarily unavailable

See 450 requested mail action not taken meaning for the full set of 450 variants.

6. 450 4.7.1: Greylisting or temporary policy deferral

7. 421 4.7.0: Throttled or reputation-limited

See 421 4.7.0 try again later meaning for the full explanation.

8. 554 5.7.1: Delivery not authorized, message refused

See what does 554 5.7.1 mean for detail on the common variants.

9. 535 5.7.8: Authentication credentials invalid

For the wider set of login and relay errors, see the SMTP code reference list.

10. 550 5.4.1: Recipient address rejected, access denied

Bottom line: the first digit sets whether to retry, the enhanced code sets the subject, and the pattern across addresses sets the action.

How do you triage bounce codes into a clean list with Unlimited Verifier?

Run this triage after any bounce spike and as a monthly habit. It needs only your ESP's bounce export, a spreadsheet and an account. If you don't have one yet, you can sign up for a free account. Free covers small lists.

  1. Export the bounce report from your ESP as CSV, keeping the address, bounce text and any code column. If there's no code column, filter the text for codes beginning with "5." or "4.".
  2. Group by code. Sort into three piles: 5.1.x and 552 5.2.2 (hard candidates), 4.x codes (soft), and 554 5.7.1, 535 5.7.8 and 550 5.4.1 (investigate before suppressing).
  3. Build a hard-bounce file. Keep only the confirmed 5.1.x addresses in one column named "email."
  4. Upload and verify the file. The email column is detected automatically. Files can be up to 10MB. On Free, keep each list to 150 emails. On Pro, keep each list to 25,000.
  5. Read the buckets. Invalid confirms suppression. Valid on an address that just bounced is a conflict to investigate, not a reason to mail it. Risky addresses need segmenting, and any catch-all, disposable or role-based flags tell you why.
  6. Download immediately. Export as CSV, Excel or JSON. Free results are kept 24 hours and Pro results are kept 30 days, so archive every export.
  7. Re-import. Add Invalid addresses to your ESP's suppression list, tag Risky, and keep the soft-bounce pile on its retry schedule. If you're unsure about a single suspicious address, run it through the free email checker first.
  8. Verify the rest of the list. Bounced addresses are already known bad. The value is catching the next bad ones before they bounce.
  9. Automate later. On Pro, you can generate API keys for single checks and for batches of up to 10,000 emails per request, within 100,000 emails a month. This is the core of email verification API and automation.

Worked example

Take a 40,000-address list. The last send produced 900 × 550 5.1.1, 150 × 550 5.1.2, 60 × 553 5.1.3 and 90 × 552 5.2.2.

The next send's bounce rate depends on how many of the remaining 38,890 addresses are invalid. The verification run is how you measure that.

Bottom line: suppress confirmed hard bounces first, then verify the rest of the list so the next send lands under 1%.

How do you choose the right action for a bounce code?

Match the pattern first, then the code. The same code can call for different actions depending on whether it hits one address, one domain or many domains.

Pattern Likely cause Action
One address, 550 5.1.1 or 553 5.1.3 Nonexistent or malformed address Suppress or correct
One domain, 550 5.1.2 Dead or misspelled domain Confirm mail server, suppress domain
One address, 552 5.2.2 across sends Persistently full mailbox Retry, then apply your written rule
Many domains, 4.x codes Provider incident or throttling Retry; check whether it clears
One provider, rising 421 4.7.0 Reputation or volume Cut volume, review list and authentication
554 5.7.1 across domains Your IP, domain or content Investigate sender; don't suppress
535 5.7.8 on the whole batch Broken credentials Fix configuration
550 5.4.1 on a few addresses Nonexistent recipients Suppress those addresses
550 5.4.1 across one domain Domain-wide policy Verify a sample, check before suppressing the domain

If you're choosing a tool to run this triage, see how to choose an email verifier and our overview of best email verification tools. For SaaS signup flows where bad addresses enter at capture, see email verification for ecommerce and SaaS.

Bottom line: a single address points to the recipient, a single domain points to the domain, and many domains point to you.

What mistakes do marketers make with SMTP codes?

Bottom line: most bounce mistakes come from acting on text or the first digit alone, instead of reading the code, subject and pattern together.

Verdict

The ten codes reduce to three actions. Suppress permanent recipient failures (550 5.1.1, 550 5.1.2, 553 5.1.3 once it's confirmed malformed). Retry temporary ones (450 4.2.1, 450 4.7.1, and 552 5.2.2 under a written rule). Investigate sender-side and policy codes (554 5.7.1, 535 5.7.8, a persistent 421 4.7.0, and domain-wide 550 5.4.1).

Verification handles the first group before the damage happens. Unlimited Verifier runs syntax, domain, MX and SMTP mailbox checks, sorts results into Valid, Risky and Invalid, and offers unlimited standard verification on every plan, including Free. The trade-off is that there are no native ESP, CRM or Zapier integrations, so the workflow is export, verify and re-import, or an API call on Pro. For most list owners, that's a 15-minute routine once a week.

Bottom line: suppress the permanent failures, retry the temporary ones, and investigate anything that points at your own sending setup.

Bounce response playbook

Code Decision Action
550 5.1.1 Suppress Remove after first occurrence
553 5.1.3 Fix or suppress Correct obvious typos, else remove
450 4.2.1 Retry Retry within the window, then apply your rule
554 5.7.1 Investigate Check IP, content, authentication and complaints
535 5.7.8 Fix credentials Check login details, do not touch the list

Frequently asked questions

What is the difference between a hard bounce and a soft bounce?

A hard bounce is a permanent failure, usually a 5xx reply such as 550 5.1.1, meaning the address should be removed. A soft bounce is a temporary failure, usually a 4xx reply such as 450 4.2.1, meaning the message can be retried later. Many ESPs classify bounces this way, but some treat certain 5xx codes such as 552 5.2.2 as soft in practice, so check your provider's rules.

Should I suppress an address after one 550 5.1.1 bounce?

Yes. A 550 5.1.1 response means the mailbox does not exist, which is a permanent recipient failure. Retrying will not fix it, and repeated attempts can hurt your sender reputation. Suppress the address after the first occurrence and keep it off future sends unless the subscriber re-confirms.

What does 554 5.7.1 mean?

554 5.7.1 is a policy refusal. The receiving server rejected the message because of its policy, such as sender reputation, content, authentication or IP blocking. It does not necessarily mean the recipient address is invalid. Investigate your sending setup, authentication records and complaint or bounce trends before changing your list.

How long should I retry a soft bounce?

Retry soft bounces for the retry window your sending platform or MTA defines, then judge the message by its final outcome. Most platforms queue and retry temporary failures over a period of hours to days before giving up. If the address still fails after the window ends, apply your written rule for soft bounces, such as suppression after several consecutive failures.

Does 421 4.7.0 mean I have been blocked?

Not necessarily. 421 4.7.0 is a temporary response indicating the server is throttling your connection or limiting you based on reputation. It is a signal to slow down. If it persists across sends, treat it as a warning, reduce volume and rate, and check your sending reputation and authentication.

What does 535 5.7.8 mean for email marketers?

535 5.7.8 means the server rejected your login credentials during SMTP authentication. This is a sender-side problem, not a recipient problem. Check the username, password or API key, confirm the authentication method your provider requires, and make sure the credentials have not been rotated or revoked. Do not remove recipients based on this code.

What does 550 5.4.1 mean?

550 5.4.1 is generally an access-denied response, often seen when a receiving system refuses delivery. The wording varies by provider, so it can mean a single address is blocked or that the whole domain rejects you. Test a few known addresses at the same domain. If many addresses at one domain return it, treat it as a domain-level issue and investigate before suppressing individually.

What is an enhanced SMTP status code?

An enhanced status code, such as 5.1.1, is a three-part code defined in RFC 3463 that adds detail to the basic SMTP reply. The first number is the class: 2 is success, 4 is persistent transient failure and 5 is permanent failure. The second number is the subject, such as 1 for addressing or 7 for security or policy. The third number gives the specific detail.

Should I remove addresses that return 553 5.1.3?

Correct the address if the error is obvious, such as a missing @ sign, a typo in the domain or a stray space, and then re-verify it. If the address cannot be corrected with confidence, suppress it. A 553 5.1.3 code means the address syntax is invalid, so it will never deliver as written and should not stay in an active sending list.

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.