503 means a valid command came at the wrong time: MAIL before EHLO, RCPT before MAIL, DATA with no accepted recipient. A 503 to DATA usually follows earlier refusals — look at the replies before it for the real reason.
| Code | 503 |
| Meaning | Bad sequence of commands |
| Kind | Permanent failure — the sender gives up |
| Sent in reply to | MAIL, RCPT, DATA, AUTH |
| What the sender does | Depends on the earlier replies; the message does not go in this session |
| Defined in | RFC 5321, sections 3.1, 4.1.4 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
- Every recipient was refused, so there is nothing to send when DATA arrives.
- A client that skips EHLO, or authenticates twice.
- A server that greeted with 554 answers every command but QUIT with 503.
What to do
- Look at the replies before the 503: the refusal that caused it is there.
- Fix the client’s command order.
What each provider means by it
| Who | What they say |
|---|---|
| Gmail | 503 5.5.1 “Bad sequence of commands”, “EHLO/HELO first”, “RCPT first”, “No DATA after BDAT”; 503 5.7.0 “No identity changes permitted”. |
| Exchange Server | Reports “send hello first” as 5.5.2. |
| Exim | Refuses MAIL before EHLO or HELO with 503, for hosts it verifies. |
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
- 14. Main configuration — exim.org