/ Glossary — Infrastructure
What is SMTP?
Simple Mail Transfer Protocol — the standard language mail servers use to transfer email. The foundation everything else sits on, from authentication to encryption. Here's how it works.
/ Definition
SMTP, or Simple Mail Transfer Protocol, is the standard protocol used to transfer email across the internet — both between mail servers and from a client or application to a server for sending. It defines the conversation two servers have to hand off a message: who it's from, who it's for, and the message itself. Nearly all outbound email travels over SMTP at some point.
SMTP is the foundation the rest of the stack builds on. An MTA speaks SMTP to deliver mail; SPF, DKIM, and DMARC authenticate the mail it carries; and MTA-STS enforces encryption on the SMTP connection itself. Understanding SMTP is understanding the layer all of those operate on.
/ In practice
How SMTP works
An SMTP transaction is a short, structured conversation. The sending server connects, identifies itself, and states the envelope sender — the Return-Path — and the recipient. The receiving server accepts or rejects each, and if it accepts, the sender transmits the message headers and body. The receiver responds with a status code: a 2xx code means accepted, a 4xx code means a temporary failure that should be retried (a soft bounce), and a 5xx code means a permanent failure (a hard bounce). Those codes are the raw signal behind everything from bounce handling to throttling.
Ports and encryption
SMTP uses a few standard ports, and the distinction matters for security. Port 25 is the classic server-to-server port. Port 587 is the modern submission port for clients and applications sending mail, and it expects authentication and encryption via STARTTLS. Port 465 is used for implicit TLS submission. Opportunistic TLS — encryption when both sides support it — is the default, but it can be downgraded by an attacker, which is the gap MTA-STS closes by requiring authenticated TLS for inbound mail.
SMTP and deliverability
Although SMTP is just the transport, the way it's used shapes deliverability. The status codes receivers return during the SMTP transaction are the primary feedback channel — a 4xx deferral often signals throttling because of reputation or rate, while a 5xx rejection can carry a block message naming a blocklist or policy reason. A well-operated MTA reads these codes and adjusts: slowing down when a provider defers, retrying intelligently, and surfacing the rejection reasons that tell you what to fix. So while SMTP itself is simple, using it well — honoring the signals it carries rather than pushing blindly through them — is a core part of the operational craft of high-volume delivery.
/ SMTP in practice
Authentication on submission
When an application sends mail through SMTP, it almost always authenticates first — proving it's allowed to send through that server with a username and password or an API credential, over an encrypted connection on the submission port. This is distinct from the email authentication that proves the message is from your domain; SMTP authentication just controls who may use the server to send. The two are often confused because both involve the word authentication, but they operate at different layers — one secures the connection to your sending infrastructure, the other vouches for the message's origin to the world. A complete setup needs both: authenticated submission so only you can send through your infrastructure, and DMARC-aligned authentication so receivers trust the mail once it's sent.
Why SMTP knowledge still matters
It's tempting to treat SMTP as a solved, invisible layer, and at low volume it is. But when mail starts failing, the SMTP transaction is where the truth lives — the exact status code and message a receiver returned tells you precisely why a message was deferred or rejected, often naming a blocklist, a rate limit, or an authentication failure. Reading those responses is how a deliverability problem goes from mysterious to diagnosable. This is also why the email header analyzer is so useful: the headers preserve the trace of the SMTP conversation that delivered a message, including the authentication results recorded along the way. The practical lesson is that SMTP rewards being understood: senders who can read a status code and trace a header diagnose problems quickly, while those who treat the protocol as a black box are left guessing.
/ Related terms
SMTP is the foundation. We operate every layer above it.
From the SMTP relay to authentication to encryption, we run the full stack so your mail transfers reliably and securely. Bring us your sending setup.
Book infrastructure reviewRelated capabilities