Permanent failure — do not retry
SMTP 503
bad sequence of commands
SMTP 503 means a command was sent in the wrong order. RFC 5321 defines it as "bad sequence of commands": for example RCPT TO before MAIL FROM, or DATA before any accepted recipient. In practice it often follows an earlier rejection, or means the server wanted authentication first.
How it appears
503 Bad sequence of commands
503 5.5.1 Error: need MAIL command
503 5.5.1 Error: need RCPT command
What causes it
- The client skipped a step, such as sending MAIL FROM before EHLO.
- Every recipient was rejected, so the following DATA command was out of sequence.
- The server requires AUTH before it will accept MAIL FROM, and the client did not authenticate.
- A pipelining client sent commands ahead of a server that rejected an earlier one.
How to fix it
In order — try the first one first.
- Read the replies before the 503. The real error is usually the command that failed just before it.
- If the text mentions authentication, turn on SMTP AUTH in your client with the account's credentials.
- If every RCPT TO was rejected, fix those addresses and the 503 on DATA goes away.
Common questions
- What does SMTP 503 mean?
- SMTP 503 means a command was sent in the wrong order. RFC 5321 defines it as "bad sequence of commands": for example RCPT TO before MAIL FROM, or DATA before any accepted recipient. In practice it often follows an earlier rejection, or means the server wanted authentication first.
- Should I retry a 503 error?
- No. 503 is a permanent failure, so the message will never be delivered no matter how many times you try. Remove the address — repeated sends to permanent failures are one of the main signals mailbox providers use to throttle a sender.
- How do I fix SMTP 503?
- Read the replies before the 503. The real error is usually the command that failed just before it.
Specific 503 replies
Last reviewed 2026-09-11