</>
ProtocolCodes
503
SMTP

503 Bad Sequence

The commands were sent in the wrong order. SMTP requires a specific command sequence (EHLO, MAIL FROM, RCPT TO, DATA) and this error indicates a step was skipped or repeated.

On this page

When You See This Code

When sending DATA before RCPT TO, or MAIL FROM before EHLO. The server enforces the correct SMTP command sequence and you have sent a command out of order.

How to Fix

Follow the proper SMTP command sequence: EHLO/HELO first, then MAIL FROM, then RCPT TO (one or more), then DATA. Reset with RSET if you need to start over.

Specification

View RFC / Specification →

Compare With

211 System Status 214 Help Message 220 Service Ready 221 Closing Connection 235 Authentication Successful 250 OK 251 User Not Local 252 Cannot Verify User 334 Server Challenge 354 Start Mail Input 421 Service Not Available 450 Mailbox Unavailable

Guides

Debugging SMTP Delivery Failures: 4xx Temporary vs 5xx Permanent Debugging & Troubleshooting
SMTP Reply Codes: What Your Email Server Is Telling You Email Delivery
Improving Email Deliverability: SPF, DKIM, and DMARC Setup Email Delivery
Diagnosing Email Bounces: Soft (4xx) vs Hard (5xx) Email Delivery
SMTP Authentication Methods Explained Email Delivery
Email Header Analysis: Tracing Delivery Path Email Delivery
Bulk Email Delivery: Avoiding the Spam Folder Email Delivery
DMARC Reporting: Analyzing Aggregate and Forensic Reports Email Delivery
IP Warming for Email: Building Sender Reputation from Scratch Email Delivery
Email Feedback Loops (FBL): Processing Spam Complaints Email Delivery
Transactional Email Best Practices: Receipts, Alerts, and Password Resets Email Delivery
DNS Record Types Explained: A, AAAA, CNAME, MX, TXT, and Beyond DNS & Networking
TCP Three-Way Handshake and Connection Lifecycle DNS & Networking
RFC 5321: SMTP Protocol Deep Dive Protocol Deep Dives
RFC 959: FTP Protocol Deep Dive Protocol Deep Dives
TLS 1.3: Faster, Simpler, More Secure Protocol Deep Dives

Debugging Scenarios

535 Authentication Failed — App Password Required Beginner
421 Service Unavailable — STARTTLS Required Beginner

Specifications

RFC 5321 Simple Mail Transfer Protocol

Glossary

Status Code Media Type (MIME Type) TLS Handshake TLS Certificate (SSL Certificate) Cipher Suite Authentication TCP/IP Three-Way Handshake Port Number Firewall IPv6 Exponential Backoff Error Code Mapping Poison Message Request-Response Model RFC (Request for Comments) IANA (Internet Assigned Numbers Authority) Message Framing Connection-Oriented Text vs Binary Protocol MX Record PTR Record SMTP Relay SPF, DKIM, and DMARC Bounce Rate (Email) Email Deliverability MTA (Mail Transfer Agent) SMTP Pipelining Greylisting Backscatter Envelope vs Header STARTTLS SMTP Authentication (SMTP AUTH) Open Relay Email Queue MIME Multipart ARC (Authenticated Received Chain) BIMI (Brand Indicators for Message Identification) DSN (Delivery Status Notification) Email Header Injection SMTP Enhanced Status Codes MDN (Message Disposition Notification) MIME Type TLS Versions TLS 1.3 Certificate Authority (CA) Forward Secrecy (PFS) SNI (Server Name Indication) TLS Session Resumption Key Exchange PKI (Public Key Infrastructure)

Frequently Asked Questions

What is SMTP 503 Bad Sequence?

The commands were sent in the wrong order. SMTP requires a specific command sequence (EHLO, MAIL FROM, RCPT TO, DATA) and this error indicates a step was skipped or repeated.

When do you see SMTP 503 Bad Sequence?

When sending DATA before RCPT TO, or MAIL FROM before EHLO. The server enforces the correct SMTP command sequence and you have sent a command out of order.

How to fix SMTP 503 Bad Sequence?

Follow the proper SMTP command sequence: EHLO/HELO first, then MAIL FROM, then RCPT TO (one or more), then DATA. Reset with RSET if you need to start over.