Skip to content
Standard SMTP codes · permanent error

504: command parameter not implemented

The server implements the command, but not the particular parameter or option the client asked for with it.

Standard
Provider
Permanent (5xx)
Class
Sources checked
Author

At a glance

Code
504
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
504 Command parameter not implemented

What it means

RFC 5321 describes 504 as a refinement of 502: the command exists, but a parameter requested with it is not implemented. The common case is AUTH with a mechanism the server does not support; RFC 4954 prescribes 504, with enhanced code 5.5.4, for an authentication mechanism that is unsupported or needs encryption first. The registry also pairs 504 with 5.7.4 for unsupported security features. It is permanent for that command, and choosing an option the server does offer fixes it.

Common causes

  • AUTH with a mechanism the server does not offer.
  • A command option that this server does not implement.

How to fix it

  1. 01Read the server's EHLO reply for the AUTH mechanisms and extensions it supports.
  2. 02Configure the client to use one of those.
  3. 03Update the client if it picks mechanisms on its own and chooses one the server lacks.

Sources

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

  1. 502Command not implemented.The server recognises the command but does not implement it, so it will not carry that command out in this session.StandardPermanent
  2. 5.5.4Invalid command arguments.A valid SMTP command was sent with an argument the server does not accept, because the value was out of range or named a feature it does not know.StandardPermanent
  3. 5.7.4Security feature not supported.The message or session asked for a security feature, such as a form of secure authentication, that the delivery protocol here cannot support.StandardPermanent

All 105 standard 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