Skip to content
Yahoo and AOL · permanent error

554: recipient does not exist

The Yahoo or AOL account you wrote to does not exist. The failure is permanent: check the address with the recipient, and remove it from any list.

Yahoo
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
554
Temporary or permanent
PermanentRefused for good: the message comes back to the sender, and resending it gets the same answer.
Who has to act
The sender. The fix is on the sending side: your domain, your server or your list.

What it means

Yahoo returns this when the account named in the address cannot be found. Yahoo's own example bounce shows it as a 554 reply stating that the user does not have a yahoo.com account. It is a permanent failure: Yahoo says the message will never be delivered and should not be retried. The usual reasons are a typing mistake, where a single wrong letter is enough, an account that was closed or moved, or an address that was never real. Yahoo also lists sending to many invalid recipients as a problem in its own right, so the address should come off a mailing list at the first bounce.

Common causes

  • The address was mistyped, sometimes by a single letter.
  • The account was closed or moved.
  • The address was invented or entered carelessly at sign-up.

How to fix it

  1. 01Do not retry: the message will not be delivered to this address.
  2. 02Check the spelling, and confirm the correct address with the recipient another way.
  3. 03Remove the address from your mailing list and suppress it so it is not imported again.
  4. 04Use confirmed opt-in so mistyped and invented addresses never reach your list.

Sources

What this page rests on, checked on 20 Oct 2026. The explanation is ours; the reply text is the server's.

  1. 553Permanent rejection (553).Yahoo or AOL rejected the message for good with a 553. Yahoo groups 553 with 554 as its permanent errors, so retrying will not help until the cause is fixed.YahooPermanent
  2. 554Permanent rejection (554).Yahoo or AOL rejected the message for good with a 554. Yahoo uses this code for several problems, from failed authentication to unacceptable content, so the wording of the reply tells you which.YahooPermanent
  3. 554Transaction failed.The server permanently refused the transaction, often after receiving the message data or straight away when the connection opened.StandardPermanent

554 at other providers

  1. 554No reverse DNS (PTR) record.Xfinity refused the connection because your sending IP has no PTR record. Every server sending to Xfinity needs valid reverse DNS, so the owner of the IP must add one.ComcastPermanent
  2. 554Rejected for breaking GMX guidelines.GMX refused the message permanently because the connection broke its guidelines. GMX points to its requirements page and asks for the full error message if the problem continues.GMX, WEB.DEPermanent
  3. 554IP address on the GMX blocklist.Your sending IP is on a blocklist that GMX manages itself, so its servers refuse the connection. GMX keeps a strict no tolerance policy toward spam.GMX, WEB.DEPermanent
  4. 554IP address on a Spamhaus blocklist.GMX refused the connection because your sending IP is listed on a Spamhaus blocklist. GMX makes no exceptions; the listing has to be removed at Spamhaus.GMX, WEB.DEPermanent
  5. 554Reverse DNS does not meet GMX requirements.GMX refused the connection because the reverse DNS (PTR) record of your IP looks generic or dynamic. GMX expects a fixed IP with its own mail host name.GMX, WEB.DEPermanent
  6. 554No reverse DNS for your IP.GMX refused the connection because the IP address of your mail server has no PTR record, so it is not tied to any domain name in DNS.GMX, WEB.DEPermanent

Further reading

All 7 Yahoo codesEvery code in the wikiPaste your own bounce

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 33 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 33

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer