Topic · Troubleshooting
SMTP 503 error
SMTP 503 indicates a bad sequence of SMTP commands in the current transaction.
How it works
Servers reject an operation that is not valid before completing required earlier protocol steps.
What can go wrong
Broken client state machines can make a functioning MX appear unavailable or incompatible.
What to check or do
Capture the entire SMTP command sequence and compare it with negotiated server extensions.
How to investigate SMTP 503 error
- Signal to investigate
- An application sends DATA before completing recipient acceptance and receives 503.
- Evidence to collect
- Capture the SMTP command sequence, server capabilities and the last accepted RCPT TO response.
- Common wrong conclusion
- An SMTP 503 bad sequence is not an issue with DNS, DKIM or the recipient address.
How to interpret the evidence
SMTP is stateful. Failed commands can require resetting the transaction rather than continuing blindly, especially with pipelined commands.
What to change and how to verify it
Correct the command order and use RSET or a clean new transaction when the server rejects sequence state.
Put this into practice
Run a focused check, then explore protection if your domain needs it.