Opens in a new tab

SMTP 554: transaction failed — what it means and the fix

554 is SMTP’s catch-all permanent failure. After the message it means the server refused it outright; as the greeting, it means the server will not talk to this client at all. Many servers use it for blocklist hits and content rejections.

Code554
MeaningTransaction failed — or, as a greeting, “No SMTP service here”
KindPermanent failure — the sender gives up
Sent in reply toThe connection greeting, DATA, the end of the message — and, at many servers, RCPT
What the sender doesStops and returns the message to the sender
Defined inRFC 5321, sections 3.1 and 4.2

Paste your bounce

Paste the line with the code — or the whole bounce: we explain each code in it, say whether the sender will try again, and link the service’s own page where it has one. It is read in your browser; nothing is sent.

What causes it

  • The sending address is on a blocklist the receiver uses.
  • The message’s content was rejected — malformed, too big, or judged harmful.
  • The server refuses this client entirely, from the first line.

What to do

  • Read the text: it usually names the blocklist or the reason.
  • For a blocklist: check the address, remove the cause, then ask the list for removal.
  • For a malformed message: check its headers against RFC 5322 — one From, a Message-ID, well-formed dates.

What each provider means by it

WhoWhat they say
Gmail554 5.4.6 for a message that went through more than 50 hops (a loop); 554 5.6.0 for a malformed message; 554 5.7.0 for too many unauthenticated commands.
Yahoo553 and 554 are its permanent errors: an invalid recipient, a DMARC or DKIM failure, policy content, an address listed by Spamhaus. Its own sample bounce reports a missing mailbox as “554 delivery error: dd This user doesn’t have a yahoo.com account”.
PostfixThe default for a hard reject: access-map REJECT, relay denied, and blocklist (DNSBL) hits.
Exim554 SMTP synchronization error when a client talks out of turn; 554 Security failure after a failed STARTTLS.

Bounces with this code

Worth knowing

A server that greets with 554 must still wait for QUIT, and answers other commands with 503.

For a host that never takes mail at all, RFC 7504 added 521; 554 stays the code for refusing particular clients.

Related: 550, 521, 5.7.1, 503.

Sources

Checked on 27 September 2026 against these official sources:

See every bounce before your customers do

Add your domain and send us a test message: we show what a receiving server saw — authentication, reverse DNS, blocklists, TLS — and monitor the servers you send from for blocklistings every day. Free for your first domain.

Create a free account