RFC 5598: Internet Mail Architecture

Over its thirty-five-year history, Internet Mail has changed significantly in scale and complexity, as it has become a global infrastructure service. These…

Read RFC 5598 on the RFC Editor

Outgoing relationships (60 related RFCs)

Showing 50 of 60 related RFCs.

Normative reference — RFC 1035: Domain names - implementation and specification
Normative reference — RFC 791: Internet Protocol
Normative reference — RFC 1034: Domain names - concepts and facilities
Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 2046: Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
Normative reference — RFC 5322: Internet Message Format
Normative reference — RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
Normative reference — RFC 5321: Simple Mail Transfer Protocol
Normative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
Normative reference — RFC 2181: Clarifications to the DNS Specification
Normative reference — RFC 4288: Media Type Specifications and Registration Procedures
Normative reference — RFC 3864: Registration Procedures for Message Header Fields
Normative reference — RFC 3461: Simple Mail Transfer Protocol (SMTP) Service Extension for Delivery Status Notifications (DSNs)
Normative reference — RFC 1939: Post Office Protocol - Version 3
Normative reference — RFC 2049: Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
Normative reference — RFC 5228: Sieve: An Email Filtering Language
Normative reference — RFC 3463: Enhanced Mail System Status Codes
Normative reference — RFC 3798: Message Disposition Notification
Normative reference — RFC 4409: Message Submission for Mail
Normative reference — RFC 3462: The Multipart/Report Content Type for the Reporting of Mail System Administrative Messages
Normative reference — RFC 3458: Message Context for Internet Mail
Normative reference — RFC 4289: Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
Normative reference — RFC 3192: Minimal FAX address format in Internet Mail
Normative reference — RFC 4021: Registration of Mail and MIME Header Fields
Normative reference — RFC 2369: The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields
Normative reference — RFC 2919: List-Id: A Structured Field and Namespace for the Identification of Mailing Lists
Normative reference — RFC 3297: Content Negotiation for Messaging Services based on Email
Normative reference — RFC 3834: Recommendations for Automatic Responses to Electronic Mail
Normative reference — RFC 5248: A Registry for SMTP Enhanced Mail System Status Codes
Normative reference — RFC 4550: Internet Email to Support Diverse Service Environments (Lemonade) Profile
Normative reference — RFC 2645: ON-DEMAND MAIL RELAY (ODMR) SMTP with Dynamic IP Addresses
Informative reference — RFC 822: STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES
Informative reference — RFC 2822: Internet Message Format
Informative reference — RFC 821: Simple Mail Transfer Protocol
Informative reference — RFC 3851: Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
Informative reference — RFC 2821: Simple Mail Transfer Protocol
Informative reference — RFC 3207: SMTP Service Extension for Secure SMTP over Transport Layer Security
Informative reference — RFC 3464: An Extensible Message Format for Delivery Status Notifications
Informative reference — RFC 4880: OpenPGP Message Format
Informative reference — RFC 733: Standard for the format of ARPA network text messages
Informative reference — RFC 3801: Voice Profile for Internet Mail - version 2 (VPIMv2)
Informative reference — RFC 1652: SMTP Service Extension for 8bit-MIMEtransport
Informative reference — RFC 2033: Local Mail Transfer Protocol
Informative reference — RFC 2142: Mailbox Names for Common Services, Roles and Functions
Informative reference — RFC 4954: SMTP Service Extension for Authentication
Informative reference — RFC 5335: Internationalized Email Headers
Informative reference — RFC 1985: SMTP Service Extension for Remote Message Queue Starting
Informative reference — RFC 3885: SMTP Service Extension for Message Tracking
Informative reference — RFC 5235: Sieve Email Filtering: Spamtest and Virustest Extensions
Informative reference — RFC 1733: Distributed Electronic Mail Models in IMAP4

Incoming relationships (29 related RFCs)

Normatively referenced by — RFC 6651: Extensions to DomainKeys Identified Mail (DKIM) for Failure Reporting
Normatively referenced by — RFC 7672: SMTP Security via Opportunistic DNS-Based Authentication of Named Entities (DANE) Transport Layer Security (TLS)
Normatively referenced by — RFC 6377: DomainKeys Identified Mail (DKIM) and Mailing Lists
Normatively referenced by — RFC 6650: Creation and Use of Email Feedback Reports: An Applicability Statement for the Abuse Reporting Format (ARF)
Normatively referenced by — RFC 7073: A Reputation Response Set for Email Identifiers
Normatively referenced by — RFC 7960: Interoperability Issues between Domain-based Message Authentication, Reporting, and Conformance (DMARC) and Indirect Email Flows
Normatively referenced by — RFC 6647: Email Greylisting: An Applicability Statement for SMTP
Normatively referenced by — RFC 9057: Email Author Header Field
Normatively referenced by — RFC 9078: Reaction: Indicating Summary Reaction to a Message
Normatively referenced by — RFC 9228: Delivered-To Email Header Field
Informatively referenced by — RFC 6120: Extensible Messaging and Presence Protocol (XMPP): Core
Informatively referenced by — RFC 7435: Opportunistic Security: Some Protection Most of the Time
Informatively referenced by — RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC)
Informatively referenced by — RFC 6531: SMTP Extension for Internationalized Email
Informatively referenced by — RFC 6591: Authentication Failure Reporting Using the Abuse Reporting Format
Informatively referenced by — RFC 6186: Use of SRV Records for Locating Email Submission/Access Services
Informatively referenced by — RFC 6652: Sender Policy Framework (SPF) Authentication Failure Reporting Using the Abuse Reporting Format
Informatively referenced by — RFC 7070: An Architecture for Reputation Reporting
Informatively referenced by — RFC 8689: SMTP Require TLS Option
Informatively referenced by — RFC 5550: The Internet Email to Support Diverse Service Environments (Lemonade) Profile
Informatively referenced by — RFC 6710: Simple Mail Transfer Protocol Extension for Message Transfer Priorities
Informatively referenced by — RFC 7293: The Require-Recipient-Valid-Since Header Field and SMTP Service Extension
Informatively referenced by — RFC 7505: A "Null MX" No Service Resource Record for Domains That Accept No Mail
Informatively referenced by — RFC 7601: Message Header Field for Indicating Message Authentication Status
Informatively referenced by — RFC 9091: Experimental Domain-Based Message Authentication, Reporting, and Conformance (DMARC) Extension for Public Suffix Domains
Informatively referenced by — RFC 7508: Securing Header Fields with S/MIME
Informatively referenced by — RFC 8098: Message Disposition Notification
Informatively referenced by — RFC 8904: DNS Whitelist (DNSWL) Email Authentication Method Extension
Informatively referenced by — RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC)