SMTP Error 503: Bad Sequence of Commands

Permanent failure High severity Protocol RFC 5321

What it means

SMTP Error 503 means “Bad Sequence of Commands.” SMTP commands were sent in the wrong order. The SMTP protocol requires commands in a specific sequence: HELO/EHLO, then MAIL FROM, then RCPT TO, then DATA. Sending commands out of order triggers this error.

At a glance

Code503

Bounce typeHard (permanent)

SeverityHigh

CategoryProtocol

What to doSuppress the address; do not retry

StandardRFC 5321

What it looks like in your mail logs

503 5.5.1 Error: need RCPT command

What does 503 mean?

SMTP code 503 indicates that your sending server issued commands in an incorrect order. The SMTP protocol requires a specific sequence: first EHLO/HELO to identify your server, then MAIL FROM to specify the sender, then one or more RCPT TO for recipients, and finally DATA to transmit the message content.

This error can also occur if a command is issued before the required authentication step. For example, attempting MAIL FROM before AUTH on a server that requires authentication will return 503. Similarly, sending DATA before any RCPT TO commands, or issuing MAIL FROM twice without completing the first transaction, will trigger this error.

How 503 plays out

Your server attempts delivery

The recipient server returns a permanent 503 rejection

This is a hard bounce: the message will not be accepted as sent

Suppress the address and fix the root cause before resending

Where 503 sits: soft vs hard bounce

	Soft bounce (4xx)	Hard bounce (5xx)
Nature	Temporary	Permanent
SMTP class	`4xx`	`5xx`
What to do	Let it retry	Suppress the address
Recoverable?	Often	No
503 is		✓ this code

Common causes of 503

Sending DATA before completing MAIL FROM and RCPT TO
Issuing MAIL FROM before HELO/EHLO
Attempting to send without required authentication (AUTH)
Sending duplicate commands without completing the transaction
Software bug in the sending MTA causing out-of-order commands

How to fix 503

Review your MTA configuration to ensure proper SMTP command sequencing
Ensure authentication (AUTH) is completed before MAIL FROM if required
Check for bugs or misconfiguration in your sending software
Test the SMTP conversation manually using telnet or openssl to identify the sequence issue

Frequently asked questions

What does SMTP error 503 "Bad sequence of commands" mean?

SMTP error 503 means your email client sent an SMTP command out of the required order. The SMTP protocol requires commands in a specific sequence: EHLO, then AUTH (if required), then MAIL FROM, RCPT TO, and finally DATA. If any command is sent before its prerequisite, such as attempting to send data before specifying the recipient, the server rejects it with a 503 error.

How do I fix SMTP 503 error?

First, enable SMTP authentication in your email client settings by entering the correct username and password. Verify your SMTP server address and port number (typically 587 for TLS or 465 for SSL). Ensure the sender email address in the "From" field is valid and properly formatted. If using custom code, confirm commands follow the correct sequence: EHLO, AUTH, MAIL FROM, RCPT TO, DATA. Use EHLO instead of HELO to enable proper authentication support.

Does SMTP 503 mean my email server requires authentication?

In most cases, yes. The most common cause of SMTP 503 is a missing authentication step. Modern mail servers require valid credentials (username and password) before allowing you to send email. If your client attempts to issue MAIL FROM or RCPT TO commands without first authenticating via the AUTH command, the server responds with 503 "Bad sequence of commands." Enable the "My server requires authentication" option in your email client's outgoing server settings.

Related bounce codes

Sources & further reading

RFC 5321 · The standard that defines this reply code RFC 5321, Section 4.2.2 · Defines the 503 reply for a bad sequence of commands RFC 3463 · Enhanced Mail System Status Codes that pair with the 5xx reply

Reviewed by Jennifer Jackson, Email Deliverability Analyst · June 2026 ← All bounce codes