TechnicalReviewed by Deliverability Engineering4 min read

SMTP

Simple Mail Transfer Protocol (RFC 5321)

Definition:SMTP is the standard internet networking protocol used to transmit outgoing email transmissions across IP networks from mail clients to mail servers.

Deliverability Impact
Critical
Implementation Time
10 mins
Key Industry & Algorithm Benchmarks
Port 587 (Submission)
STARTTLS 1.3 Recommended
Standard for sequencer mailbox connections
Port 465 (SMTPS)
SSL/TLS Encrypted
Direct encrypted client submission
Port 25 (Relay)
Server-to-Server Only
Egress blocked by AWS EC2 and Google Cloud
Pro Tip from the Trenches

When configuring custom SMTP relays, always ensure the server's PTR reverse DNS record matches the hostname announced during the EHLO command to pass strict enterprise reverse-DNS anti-spam checks.

Standard SMTP Handshake Sequence
CLIENT: EHLO mail.yourdomain.com
SERVER: 250-smtp.google.com at your service, [IP]
CLIENT: MAIL FROM:<alex@yourdomain.com>
SERVER: 250 2.1.0 OK
CLIENT: RCPT TO:<john@prospectcompany.com>
SERVER: 250 2.1.5 OK
CLIENT: DATA
SERVER: 354 Go ahead
CLIENT: [Email Headers & Body Content]
CLIENT: .
SERVER: 250 2.0.0 OK: message queued 12345
CLIENT: QUIT

Frequently Asked Questions about SMTP

Use Port 587 with STARTTLS encryption. Port 465 (SSL) is also widely supported, while Port 25 is reserved for server-to-server relays and blocked by most cloud hosts.

Detailed Technical Breakdown

SMTP establishes a connection between the sending client and receiving mail transfer agent (MTA) over specific network ports: Port 587 (authenticated client submission with STARTTLS encryption), Port 465 (SMTPS SSL/TLS encryption), and Port 25 (server-to-server relay).

The protocol executes a command-response conversation: `EHLO` (client greeting), `MAIL FROM` (envelope sender), `RCPT TO` (recipient address), `DATA` (message payload), and `QUIT`.

Modern security gateways inspect the SMTP handshake in real time, checking reverse DNS (PTR) records, TLS cipher strength, and envelope authentication before accepting the message payload.

Why it matters for Cold Email & Deliverability

Flawless SMTP configuration is the technical foundation of all outbound email communication.

Misconfigurations in SMTP authentication or port selection result in immediate connection drop errors (550/554 rejections).

How to optimize SMTP

  1. Use Port 587 with STARTTLS encryption for connecting cold email sequencers to mail servers.
  2. Ensure the hostname announced in the SMTP `EHLO` handshake matches the sending server's reverse DNS PTR record.
  3. Monitor SMTP error response codes (e.g. 550 User Unknown, 421 Rate Limited) to detect deliverability bottlenecks.
  4. Deploy TLS 1.3 encryption across all outbound mail transmission channels.

Common SMTP Mistakes

  • Attempting to send outbound email directly over Port 25 from cloud providers (AWS, GCP) that block outbound Port 25 traffic.
  • Failing to enable TLS encryption on SMTP connections, causing receiving servers to flag messages as insecure.
  • Using mismatched hostnames in SMTP `EHLO` commands that fail reverse DNS lookups.