What does 503 mean?
Still have a question, spotted an error, or have a better explanation or a source we should cite?
You're looking at your SMTP logs and there it is: a 503 error. The message usually says something like "503 Bad sequence of commands" or "503 Need MAIL command." It sounds cryptic, but the fix is actually straightforward once you understand what SMTP expects.
A 503 error means your sending software sent a valid command at the wrong time. SMTP is a conversation with a strict order. The receiving server expected a different command next, and when it got something out of sequence, it threw a 503.
The required order looks like this:
- EHLO or HELO to introduce yourself
- MAIL FROM to declare the sender
- RCPT TO to declare the recipient
- DATA to send the message body
Skip a step, repeat a command in the middle of a transaction, or try to jump to DATA before RCPT TO, and you'll get a 503. It's almost always a bug in a custom SMTP integration or a misconfigured mail client, not a server-side issue on the receiving end.
Common examples you'll see in logs: "503 Bad sequence of commands", "503 Need MAIL command", "503 RCPT first". Each one is the server pointing to exactly which step went wrong, which makes debugging easier than most SMTP errors.
If you're hitting this in a custom integration, check which command your code sends right before the 503 appears. That's your culprit. If it's happening in a standard ESP or mail client, it could be a session timeout mid-transaction where the connection dropped and restarted mid-sequence without a fresh EHLO.
Not sure how to read SMTP logs or trace the sequence? The Email Header Analyzer can help you pull apart what actually happened during a send, or drop us a message on the SOS hotline if you're stuck on a live integration issue.
Contributors
Who worked on this answer
Every name links to their profile. Every company links to their site. Real people, real accountability.
