RFCs conformed
JMAP
- RFC 8620 - The JSON Meta Application Protocol (JMAP)
- RFC 8621 - The JSON Meta Application Protocol (JMAP) for Mail
- RFC 8887 - A JSON Meta Application Protocol (JMAP) Subprotocol for WebSocket
WebSocket
- RFC 6455 - The WebSocket Protocol
- RFC 8307 - Well-Known URIs for the WebSocket Protocol
- RFC 8441 - Bootstrapping WebSockets with HTTP/2
HTTP Push
- RFC 5116 - An Interface and Algorithms for Authenticated Encryption (AEAD_AES_128_GCM)
- RFC 8030 - Generic Event Delivery Using HTTP Push
- RFC 8188 - Encrypted Content-Encoding for HTTP
- RFC 8291 - Message Encryption for Web Push
OAuth
- RFC 6749 - The OAuth 2.0 Authorization Framework
- RFC 6750 - The OAuth 2.0 Authorization Framework: Bearer Token Usage
- RFC 8414 - OAuth 2.0 Authorization Server Metadata
- RFC 8628 - OAuth 2.0 Device Authorization Grant
DKIM
LMTP/SMTP
- RFC 821 - Simple Mail Transfer Protocol
- RFC 2033 - Local Mail Transfer Protocol
- RFC 2821 - Simple Mail Transfer Protocol (updates RFC821)
- RFC 5321 - Simple Mail Transfer Protocol (updates RFC2821)
- RFC 1870 - SMTP Service Extension for Message Size Declaration
- RFC 2034 - SMTP Service Extension for Returning Enhanced Error Codes
- RFC 2195 - AUTHorize Extension for Simple Challenge/Response
- RFC 2831 - Using Digest Authentication as a SASL Mechanism
- RFC 2920 - SMTP Service Extension for Command Pipelining
- RFC 3030 - SMTP Service Extensions for Transmission of Large and Binary MIME Messages
- RFC 3207 - SMTP Service Extension for Secure SMTP over Transport Layer Security
- RFC 6152 - SMTP Service Extension for 8-bit MIME Transport
- RFC 6532 - SMTP Extension for Internationalized Email
- RFC 4954 - SMTP Service Extension for Authentication
- RFC 822 - Standard for ARPA Internet Text Messages
- RFC 5322 - Internet Message Format
- RFC 2045 - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
- RFC 2046 - Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types
- RFC 2047 - MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text
- RFC 2048 - Multipurpose Internet Mail Extensions (MIME) Part Four: Registration Procedures
- RFC 2049 - Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
- RFC 2231 - MIME Parameter Value and Encoded Word Extensions: Character Sets, Languages, and Continuations
- RFC 2557 - MIME Encapsulation of Aggregate Documents, such as HTML (MHTML)
- RFC 2183 - Communicating Presentation Information in Internet Messages: The Content-Disposition Header Field
- RFC 2392 - Content-ID and Message-ID Uniform Resource Locators
- RFC 3282 - Content Language Headers
- RFC 6532 - Internationalized Email Headers
- RFC 2152 - UTF-7 - A Mail-Safe Transformation Format of Unicode
- RFC 2369 - The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields
- RFC 2919 - List-Id: A Structured Field and Namespace for the Identification of Mailing Lists
- RFC 3339 - Date and Time on the Internet: Timestamps