SMTP (Simple Mail Transfer Protocol)
What is SMTP (Simple Mail Transfer Protocol)?
SMTP (RFC 5321) is the store-and-forward protocol mail servers use to relay email from a sender's outgoing server to a recipient's incoming one, with no built-in encryption or sender authentication of its own. AdminKit's STARTTLS checker verifies whether a mail server enforces the encryption extension plain SMTP never included.
By AdminKit team, Netbase JSC · Updated
SMTP (RFC 5321) is the protocol mail servers use to relay email from a sender’s outgoing server to a recipient’s incoming server, normally on port 25, the port IANA registers as “Simple Mail Transfer” — and from a mail client to its own outgoing server before that. Every SMTP session opens with the client identifying itself via a HELO or EHLO command before any message data is sent. Servers that advertise the ENHANCEDSTATUSCODES keyword in that EHLO reply also attach an SMTP enhanced status code such as 5.1.1 to their 3-digit replies. It’s a store-and-forward protocol: a message can hop through several SMTP servers before reaching its final destination, each one accepting responsibility for onward delivery or returning a bounce if it can’t deliver — the store-and-forward relay model Cloudflare’s explainer on SMTP covers in describing how a message actually moves between mail servers. RFC 5321’s requirement that a compliant server queue and retry a temporary failure is also what greylisting deliberately exploits, rejecting an unfamiliar sender’s first attempt with a 4xx code just to see whether it retries. The Postfix Architecture Overview shows how one implementation does this: its queue manager keeps a separate deferred queue for mail that cannot be delivered yet, so a backlog of retries does not slow down normal deliveries. SMTP on its own has no built-in encryption or sender authentication — both were added later as extensions, STARTTLS (RFC 3207) for encrypting the connection, and SPF, DKIM and DMARC as separate DNS-based mechanisms for verifying who actually sent a message — which is why a server running plain SMTP alone cannot guarantee either privacy in transit or that a message’s claimed sender is genuine.
Browse the AdminKit glossary index for other related terms.
Frequently asked questions
Does SMTP encrypt email by default?
No -- plain SMTP has no built-in encryption or sender authentication. Encryption was added later as the STARTTLS extension (RFC 3207), and a server that doesn't enforce it can still fall back to sending a message in the clear.
What does "store-and-forward" mean for SMTP?
A message can hop through several SMTP servers before reaching its final destination, with each server accepting responsibility for onward delivery or returning a bounce if it can't deliver -- unlike a protocol that requires a single direct connection all the way to the recipient.
How does SMTP verify who actually sent a message?
It doesn't, on its own. SPF, DKIM and DMARC are separate DNS-based mechanisms layered on top of SMTP specifically to verify a message's claimed sender, since RFC 5321 itself defines no sender-authentication step.
Why does greylisting work against SMTP specifically?
RFC 5321 requires a compliant server to queue and retry a temporary failure rather than drop the message, and greylisting deliberately exploits that requirement -- it rejects an unfamiliar sender's first attempt with a 4xx code just to see whether the sending server retries, which most spam senders don't bother doing.