All specs
RFC 5321RFCMust KnowBack Office2008

Simple Mail Transfer Protocol

Email·RFC Editor
WHY YOU NEED THIS

Every email your company sends or receives goes through SMTP. You need this to configure mail servers, debug delivery failures, and understand SPF/DKIM/DMARC.

What It Defines

Defines SMTP for mail submission and relay between servers: EHLO, MAIL FROM, RCPT TO, DATA commands, extensions model, and the DNS MX record lookup process.

Canonical (Normative)

Convenient (Practical)

smtpemailmailtransport
Standards Body
RFC Editor

The canonical publication point for finalized RFCs. If a protocol is standardized as an RFC, the RFC Editor text is the normative final reference. Published by the IETF, IRTF, IAB, and independent stream.

Visit

Related Specs

RFC 5322RFCMust Know

IMF

The structure of every email header you've ever seen is defined here. Essential for email deliverability debugging and understanding DKIM header signing.

Back OfficeEmail
Details
RFC 9051RFCMust Know

IMAP

Your email client (Outlook, Gmail app, Thunderbird, Apple Mail) uses IMAP or JMAP to read mail. Essential for mail server configuration and client integration.

Back OfficeEmail
Details
RFC 7208RFCMust Know

SPF

Without a correct SPF record, your domain's email will fail or be deferred by major receivers (Gmail, Outlook). Set correctly as part of basic email deliverability.

Back OfficeEmail
Details
RFC 6376RFCMust Know

DKIM

DKIM is required to pass DMARC. Without it, your email won't be trusted by major providers. Set up alongside SPF as part of any serious email configuration.

Back OfficeEmail
Details
RFC 7489RFCMust Know

DMARC

DMARC is the final layer of email authentication. Without it, your domain can be spoofed in phishing. Google and Yahoo require DMARC for bulk senders.

Back OfficeEmail
Details