Skip to content
Fastmail · permanent error

554: relay access denied

Fastmail refused to pass your message on because your mail program did not sign in to the outgoing server. Turn on authenticated SMTP.

Fastmail
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
554
Provider
Fastmail
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 the server says
554 Relay access denied

What it means

An outgoing mail server only relays mail to other domains for users who have signed in, otherwise anyone could send through it. When Fastmail answers with 554 Relay access denied, it usually means your mail program is not using authenticated SMTP. Fastmail points to its client setup instructions: check that the outgoing server in your mail program is set to sign in, with the details those instructions give. Once the program signs in, mail is accepted.

Common causes

  • The outgoing server settings in your mail program have authentication turned off.
  • The program is set to the wrong outgoing server or port.
  • A device or app was set up by hand and missed the authentication setting.

How to fix it

  1. 01Open the outgoing (SMTP) server settings of your mail program.
  2. 02Turn on authentication and enter the sign-in details from Fastmail setup instructions for your program.
  3. 03Compare server, port and encryption with Fastmail's setup instructions, then send again.

Sources

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

  1. 535 5.7.8Authentication failed for an external address.Fastmail could not sign in to the outgoing server of an external address you send from, most often because its stored password has changed.FastmailPermanent
  2. 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. 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
  2. 554Failed authentication.Yahoo or AOL refused the message because it failed the checks that confirm the sending domain, such as DKIM against the domain's policy. Yahoo lists this among its permanent 553 and 554 errors.YahooPermanent
  3. 554Recipient 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.YahooPermanent
  4. 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
  5. 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
  6. 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

All 4 Fastmail 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