500 means the server did not recognise the command — or the line was too long. The session carries on: a standard server answers 500 and waits for the next command. It points to a client that speaks something other than SMTP, or a bug.
| Code | 500 |
| Meaning | Syntax error, command unrecognized |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | Any command |
| What the sender does | Tries another command — EHLO falls back to HELO; otherwise the message does not go |
| Defined in | RFC 5321, sections 4.2 and 4.2.4 |
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
- A client sending commands the server does not know.
- An EHLO to a very old server, which knows only HELO.
- A command line longer than 512 characters.
What to do
- Check the client or script that sends the mail: it is not speaking SMTP as the server expects.
What each provider means by it
| Who | What they say |
|---|---|
| Gmail | Answers unrecognised commands with 502 5.5.1 rather than 500. |
| Exchange Server | Its 5.3.3 “Unrecognized command” usually means a Receive connector missing Exchange Server authentication. |
| Postfix | Disconnects a client after 20 such errors (smtpd_hard_error_limit). |
Worth knowing
500 is for a command not recognised at all; 502 for one recognised but not implemented.
A server must not advertise in EHLO an extension it would answer with 500.
Sources
Checked on 27 September 2026 against these official sources:
- RFC 5321: Simple Mail Transfer Protocol — rfc-editor.org
- RFC 4954: SMTP Service Extension for Authentication — rfc-editor.org
- Simple Mail Transfer Protocol (SMTP) Enhanced Status Codes Registry — iana.org
- Gmail SMTP errors and codes — knowledge.workspace.google.com
- DSNs and NDRs in Exchange Server — learn.microsoft.com
- Postfix Configuration Parameters — postfix.org