Article

554 Transaction Failed Bounce: What It Means and How to Fix It

By Unlimited Verifier Team ·

Diagram showing a 554 Transaction failed SMTP bounce splitting into recipient-side and sender-side causes.

Summary

A 554 "Transaction failed" bounce is a permanent SMTP rejection, so retrying the same message will not succeed. The enhanced status code and reply text show the cause, which may be a blocklist, an authentication failure, or a nonexistent mailbox. Read those details before deciding whether to delete an address or fix your sending setup.

A 554 "Transaction failed" bounce is a permanent SMTP rejection: the receiving server refused your message, and RFC 5321 classifies 5xx replies as permanent failures, so retrying the same message unchanged will not help. The number alone rarely shows the cause, so read the text and the enhanced status code (such as 5.7.1 or 5.1.1) before you decide whether to delete an address or fix your sending setup.

This guide is for marketers, list owners, agencies and SaaS teams who see 554 bounces in an ESP report or non-delivery notice and need to decide what to suppress, what to fix and what to leave alone. It sits under our email bounce codes pillar and covers the eight causes that public provider and standards documentation describes most often, plus a triage method you can run on a bounced list.

Quick answer

Quick picks by situation

554 causes at a glance

Cause Typical text (example) Where it happens Retry? Does address verification help? First action
IP or domain blocked 554 5.7.1 … blocked using a named blocklist Connection or MAIL FROM No No Check the listed IP or domain, then request delisting
Content or spam rejection 554 5.7.1 … likely unsolicited mail After DATA No No Audit content, list source and complaints
Authentication policy 554 5.7.26 … DMARC policy After DATA No No Fix SPF, DKIM and DMARC alignment
Relay denied 554 5.7.1 Relay access denied RCPT TO No No Check SMTP authentication and submission settings
Recipient organization policy 554 5.4.1 Recipient address rejected: Access denied RCPT TO No Partly Count failures per domain, then decide whether to pause
Mailbox does not exist 554 5.1.1 User unknown RCPT TO No Yes Suppress
Host is not a mail server 554 No SMTP service here Connection greeting No Domain-level Check MX records
No reason given 554 Transaction failed Varies No Address-level only Identify the reporting server and check logs

How we compared (and limitations)

Each cause was assessed against four criteria:

  1. Signal strength: how clearly the code and text point to one cause.
  2. Who can fix it: the recipient, the recipient's provider, or you.
  3. Whether verification can separate it: whether an address-level check would change the decision.
  4. Documentation: whether the wording appears in public provider or standards documentation.

Limitations. This comparison is based on public documentation, RFCs and vendor-published guidance. We did not run test sends or measure how providers respond. Provider wording changes often, and the same code can carry different text on different servers. We cannot see your mail logs, so a cause that looks likely from the text may still need confirmation from your ESP. Unlimited Verifier's SMTP check is one signal, and some providers restrict recipient checks, so Risky or unknown results are common.

Bottom line: the text, stage and enhanced code together identify the cause far more reliably than the number 554 alone.

What does a 554 transaction failed bounce actually mean?

A 554 reply means the server rejected the transaction, and the 5 at the start makes it permanent. RFC 5321 defines 554 as "Transaction failed." When the same code appears in the connection greeting, it means "No SMTP service here," which is a different situation.

The enhanced status code, defined in RFC 3463, adds the subject. The second number identifies the category: 5.1 is addressing, 5.2 is mailbox, 5.3 is mail system, 5.4 is network and routing, 5.5 is mail delivery protocol, 5.6 is message content, and 5.7 is security or policy.

Two details matter in practice:

For how permanent and temporary failures differ, see 4xx vs 5xx SMTP errors difference.

Where sources disagree: providers do not agree on which text maps to which 554 cause. We recommend a simple rule: treat a 5.1.x code as recipient-level, and treat a 5.7.x code as sender-level until you have evidence otherwise.

Bottom line: a 554 is a permanent refusal, and its subject code and text decide whether the fix is on the list or on your side.

What are the most common causes of a 554 bounce?

The eight causes below are the patterns most often described in public guidance. Each shows the text you will typically see, where the rejection happens and what to do.

1. 554 5.7.1: IP or domain blocked for reputation

What it means: the server refused your connection or sender because your IP or domain is listed on a reputation blocklist.

How to recognize it: the text names a blocklist or says the client host was blocked. The rejection happens before your message body is transferred, so it often affects every recipient at one provider at once.

Likely cause: a compromised account, a shared IP with poor neighbors, or a purchased list.

First fix: look up the IP and domain named in the error with Spamhaus, then follow the delisting process of the list that named you. Reduce volume to the affected provider until you are removed.

Where verification fits: it does not. The addresses may be perfectly valid. Our free domain blacklist checker helps only with the domain-side question.

Worked example: if 1,800 of 2,000 bounces to one provider carry this code, you have one sender problem, not 1,800 bad addresses. Deleting them would remove real subscribers.

Bottom line: a blocklist 554 is a sender reputation problem; fix the sender and keep the addresses.

2. 554 5.7.1: content or "likely unsolicited" rejection

What it means: the provider scanned your message and classified it as unwanted.

How to recognize it: text such as "Our system has detected that this message is likely unsolicited mail," which Gmail uses. This rejection arrives after DATA, so the full message was received.

Likely cause: message content, link patterns, sending behavior or user complaints.

First fix: check your domain in Google Postmaster Tools, where Google's sender guidelines describe the spam-rate thresholds. Google advises keeping the user-reported spam rate below 0.3% and recommends staying under 0.1%. That is a complaint rate, not a bounce rate.

Where verification fits: limited. Verification removes nonexistent mailboxes, which reduces one risk. It does not evaluate content, and no verifier can reliably catch every spam trap.

Tip: if the 554 appears on one campaign only, inspect that campaign's content and links before touching the list.

Bottom line: content-based 554s are a reputation signal, and verification addresses only part of the problem.

3. 554 5.7.26: authentication policy failure

What it means: the message did not pass authentication checks that the recipient's domain requires.

How to recognize it: text such as "Unauthenticated email … is not accepted due to domain's DMARC policy." The enhanced code 5.7.26 is the same whether the reply is 550 or 554, so check the subject code as well as the number.

Likely cause: the message did not pass SPF or DKIM in a way that aligns with the visible From domain. Common triggers include sending through an ESP without custom DKIM, a missing ESP entry in SPF, or a From domain that differs from the authenticating domain.

First fix: publish DKIM for your sending domain, include your ESP in SPF, and publish a DMARC record. RFC 7489 defines DMARC. Many senders begin with a monitoring policy (p=none) and tighten it after reviewing reports.

Where verification fits: it does not. Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It does not check SPF, DKIM or DMARC.

Tip: if failures cluster on a few recipient domains, those domains likely enforce DMARC strictly.

Bottom line: authentication 554s are a DNS and configuration fix, not a cleaning task.

4. 554 5.7.1 "Relay access denied": your server is not allowed to send

What it means: your sending server asked to relay mail it is not authorized to send.

How to recognize it: "554 5.7.1 : Relay access denied," which is common on self-hosted servers and application SMTP settings. It arrives at RCPT TO.

Likely cause: the sending application failed SMTP authentication, or it connected from an address the server does not trust. An application pointed at the wrong host is a frequent culprit.

First fix: confirm that the sending system uses authenticated submission, typically port 587 with STARTTLS, and that its credentials and allowed networks are correct.

Where verification fits: no. Recipients are not the issue.

Tip: send one test message to a mailbox you control. If every domain fails, it is configuration. If only certain recipients fail, look elsewhere.

Bottom line: if the failure happens for every domain, the problem is your server, not your list.

5. 554 5.4.1 "Recipient address rejected: Access denied"

What it means: the recipient organization's policy rejected your sender.

How to recognize it: "Recipient address rejected: Access denied," often reported with Microsoft-hosted recipients. Failures cluster on one organization's domain.

Likely cause: a sender-restriction or directory rule set by the recipient's administrator. You usually cannot clear it from your side.

First fix: count failures by recipient domain. If they cluster on one company, the restriction is organizational. Pause sends to that organization. If you have a legitimate relationship, ask the recipient to allow your sending address.

Where verification fits: partly. A Valid result shows the mailbox appears to exist, but not that your mail will be accepted.

Worked example: 260 failures across 12 addresses at one company points to a single organizational policy. Treat it as one suppression or pause decision for that organization, not 260 list problems.

Bottom line: access-denied 554s are about the recipient organization's policy, so count per domain before you decide.

6. 554 5.1.1 "User unknown" sent as 554

What it means: the mailbox does not exist.

How to recognize it: "554 5.1.1

: Recipient address rejected: User unknown." Some servers send 554 where others send 550. The rejection happens at RCPT TO, before any message body is transferred.

Likely cause: a typo, a closed account, or a stale address from an old import.

First fix: suppress the address and do not retry. Look for typo domains such as gmial.com in your source data, and validate addresses at signup with real-time email validation. The same condition often appears as 550 5.1.1, covered in 550 5.1.1 user unknown meaning.

Where verification fits: strongly. Uploading the bounced addresses to Unlimited Verifier shows which ones check as Invalid.

Worked example: 900 user-unknown bounces in a 60,000-address list is 1.5%. That is above the 1% per-send target many teams use as an internal guideline, so clean the source list too.

Bottom line: 5.1.1 bounces are the one 554 type where cleaning the list is the right first response.

7. "554 No SMTP service here": the host is not a mail server

What it means: the host answered the connection but does not offer SMTP service for the domain.

How to recognize it: "554 No SMTP service here" in the connection greeting.

Likely cause: the MX record points to a host that does not run mail service, the destination is a web server, or the domain has no working mail setup.

First fix: check the domain's MX records with a DNS lookup. If there is no working MX, the domain cannot receive mail. 550 5.1.2 bad destination host meaning covers the related host-level failure.

Where verification fits: at the domain level. Unlimited Verifier's domain and MX checks should surface a domain-wide failure like this, so test a sample of affected addresses to confirm.

Tip: distinguish a domain that cannot receive any mail, which means suppressing the whole domain, from one bad mailbox.

Bottom line: if the host is not a mail server, every address on that domain is affected, so treat the domain as a unit.

8. Bare "554 Transaction failed" with no reason

What it means: something in the delivery path rejected the message without giving a reason.

How to recognize it: "554 Transaction failed" or "554 5.0.0 Transaction failed," with no explanation.

Likely cause: the reporting server may be your ESP's relay, a corporate gateway or an intermediate filter rather than the mailbox provider.

First fix: read the full bounce message and identify the reporting server. The Reporting-MTA field and the remote host name are the usual clues. Check your ESP's activity log, then contact ESP support with the full bounce, timestamp and message ID.

Where verification fits: only at the address level. If the address verifies Invalid, suppress it. If it verifies Valid, do not assume the bounce was about the address.

Bottom line: a bare 554 is a diagnosis task; find the reporting server before changing your list.

How do you triage a bounced list with Unlimited Verifier?

Use this process to separate address failures from sender failures. For a few thousand bounces, the hands-on work usually takes under an hour once you have the export.

  1. Export every 554 bounce from your ESP. Include the address, the full status text, the timestamp and the recipient domain.
  2. Group by text, not by number. Sort into three buckets: 5.1.x (address), 5.7.x (policy or authentication) and bare or other.
  3. Build a CSV for verification. Include one email column. Keep the code in a reference column if you want to filter later.
  4. Sign up for a free account if your bounced list is small. The Free plan allows 25 lists a month of up to 150 emails each, plus 750 deep verifications a month.
  5. Upload the file. The email column is detected automatically. Files can be up to 10MB.
  6. Read the three buckets. Valid, Risky and Invalid each lead to a different decision, shown in the table below.
  7. Download results promptly. Free results are kept for 24 hours and Pro results for 30 days. Export as CSV, Excel or JSON.
  8. Update your ESP. Add Invalid addresses to suppression, keep Valid addresses that failed for sender-side reasons, and tag Risky addresses for engagement review.
  9. Test after you fix the cause. Send a small test to the domains that previously failed, and confirm the 554 does not return.

Worked example (illustrative numbers). Suppose 8,000 addresses bounced with 554 in one month:

  • Free plan: 8,000 ÷ 150 ≈ 54 files. The Free plan allows 25 lists a month (25 × 150 = 3,750 addresses), so you would have to split the work across months or move to Pro.
  • Pro plan: the whole set fits in one list, since Pro allows up to 25,000 emails per list.
  • Results (illustrative): 2,100 Invalid (about 26%), 900 Risky (about 11%) and 5,000 Valid (62.5%).
  • Decisions: suppress the 2,100 Invalid addresses. For the 900 Risky addresses, use catch-all email verification to see which results come from catch-all domains, then check engagement rather than deleting on bounce alone. The 5,000 Valid addresses appear to exist, so 554s on them point to a sender-side cause.

The Valid share is the insight to act on. If most of a bounced set still checks as Valid, you have a delivery problem to fix, not a list to purge.

Tip: spend deep verifications on the Risky bucket, where extra checks can change decisions. The Pro plan includes 25,000 deep verifications a month. Unlimited Verifier states 99.5% accuracy for its deep verification. That is the vendor's own figure, so test it on a sample of your list.

Automating at scale. If you re-check bounces weekly, the email verification API on Pro accepts bulk batches of up to 10,000 emails per request, within a 100,000-email monthly allowance. Our email verification API and automation guide covers the pattern. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the workflow runs as export, verify and re-import, or as API calls.

Bottom line: verification tells you whether the address is the problem; the 554 text tells you whether the sender is.

Which fix should you choose for a 554 bounce?

Situation Action Verification's role
5.1.x on a few addresses Suppress Confirms Invalid
5.1.x on many addresses from one source Suppress and audit the source Confirms Invalid and surfaces typo domains
5.7.1 blocklist on one provider Fix sender reputation, pause volume None
5.7.1 content rejection Audit content and list source None
5.7.26 authentication Fix DKIM, SPF and DMARC None
Relay denied on every domain Fix SMTP configuration None
5.4.1 access denied at one organization Pause that organization, consider asking for an allow Partly
No SMTP service on a domain Check MX, suppress the domain Domain-level
Bare 554 Identify the reporting server Address-level only

If your list is large or mixed, compare options in our roundup of best email verification tools and our guide to how to choose an email verifier. SaaS teams whose signup flow generates bounces should read email verification for ecommerce and SaaS. Verification costs depend on volume and frequency, and our email verification pricing overview explains how the models differ.

Bottom line: match the fix to the subject code, and use verification only where the cause is the address.

Common mistakes with 554 bounces

  • Retrying 554s on the normal schedule. A permanent failure will not clear by itself. Fix the cause, then send a fresh test.
  • Deleting every address that bounced. Reputation and authentication 554s hit valid subscribers. Deleting them shrinks your audience without fixing the problem.
  • Reading only the number. 554 means different things depending on the text and subject code.
  • Treating a Valid result as proof of delivery. It means the mailbox appears to exist, not that this sender will be accepted.
  • Ignoring per-domain patterns. A single provider's blocklist can look like list decay until you count failures by domain.
  • Expecting verification to fix authentication. SPF, DKIM and DMARC are DNS and sender-configuration tasks.
  • Letting compliance slide. Clean lists help deliverability, but consent and suppression obligations are separate. See email verification compliance and hygiene and email list maintenance best practices.

For related failure types, see common soft bounce reasons list and enhanced SMTP status codes list. If non-delivery notices keep appearing in your own inbox, why do I keep getting mailer-daemon bounce messages explains the likely source.

Bottom line: most 554 mistakes come from treating every failure as the same problem.

Verdict

A 554 "Transaction failed" bounce is a permanent refusal, and its cause is in the text. Address-level codes such as 5.1.1 are the cases where cleaning the list is the right response, and verification confirms them directly. Reputation, content, authentication and relay 554s are sender-side problems that verification cannot solve.

For bounced lists, Unlimited Verifier shows which addresses are dead and which still appear valid. That split tells you whether to clean the list or fix your sending setup. It does not check authentication or content, so use your ESP's diagnostics for those.

Bottom line: verify the bounced addresses to find out whether the list or the sender is responsible, then fix that one.

554 triage steps

  1. Group bounces by receiving domain and reply text.
  2. If text says user unknown or does not exist, suppress the address.
  3. If text cites a blocklist, IP or domain reputation, check the listing and request delisting.
  4. If text cites DMARC or authentication, fix SPF, DKIM and DMARC alignment.
  5. If the reply is bare, pull the full SMTP transcript from your ESP or MTA logs.
  6. Verify a sample of bounced addresses: Invalid means a list problem; Valid points to sender-side causes.
  7. Resend a small test batch only after the cause is fixed.

Frequently asked questions

Should I retry a 554 bounce?

No. A 554 is a permanent 5xx SMTP failure, so retrying the same message unchanged will generally fail again. Fix the cause shown in the reply text first, then send a new message. Retrying on your normal schedule only adds noise to the receiving server's logs and can hurt sender reputation.

What does 554 5.7.1 mean?

554 5.7.1 usually means the receiving server rejected the message for policy reasons, most often a blocklist listing of your sending IP or domain, or a content or reputation decision. The reply text usually names the reason. Check the listed resource, resolve the issue, and request delisting if needed before resending.

What does 554 5.1.1 mean?

554 5.1.1 means the recipient address does not exist at that domain, often shown as "User unknown". This is a list-quality issue. Suppress the address so you stop sending to it. Verification tools can confirm whether an address is Invalid before you remove it from your active list.

Is 554 Transaction failed the same as a hard bounce?

Usually yes. A 5xx reply is a permanent failure, so most ESPs classify a 554 as a hard bounce. However, some providers apply their own rules, so check the reason text. Treat it as a hard bounce for suppression only when the cause points to the recipient address.

Can a 554 bounce be caused by my SPF, DKIM or DMARC setup?

Yes. A 554 with a 5.7.26 code or text mentioning DMARC or authentication indicates the receiver rejected the message because it failed authentication policy. Check that SPF includes your sending service, DKIM signs with a domain you control, and DMARC alignment passes before changing your list.

Why do I get 554 bounces with no reason given?

A bare "554 Transaction failed" gives no specific cause, so the reply came from a server that does not explain its decision. Identify which receiving server sent it, check your MTA or ESP logs for the full SMTP transcript, and compare failures across domains to find a pattern.

How do I know if a 554 is my fault or the recipient's?

Group bounces by receiving domain and reply text. If failures cluster on one provider or cite your IP, domain or authentication, the cause is on the sending side. If failures are scattered and mention unknown users, the cause is the address. Verifying a sample of bounced addresses helps separate the two.

Does a 554 bounce hurt my sender reputation?

Repeated bounces can, particularly when a high share of your sends bounce. Receivers track bounce and complaint rates. Suppressing addresses that bounce for recipient-side reasons and fixing sender-side causes both protect reputation. Continuing to send to bad addresses or retrying blocked messages tends to make reputation worse.

How long should I wait before emailing an address that returned 554?

Do not resend to an address that returned a 554 for an unknown mailbox. For sender-side causes, wait until the blocklist, authentication or content issue is fixed, then send a small test batch to a known-good inbox before resuming full volume.

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.