RFC 3516: IMAP4 Binary Content Extension

This memo defines the Binary extension to the Internet Message Access Protocol (IMAP4). It provides a mechanism for IMAP4 clients and servers to exchange…

Read RFC 3516 on the RFC Editor

Outgoing relationships (4 related RFCs)

Normative reference — RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
Normative reference — RFC 2234: Augmented BNF for Syntax Specifications: ABNF
Normative reference — RFC 3501: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
Normative reference — RFC 2047: MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text

Incoming relationships (9 related RFCs)

Updated by — RFC 4466: Collected Extensions to IMAP4 ABNF
Normatively referenced by — RFC 4005: Diameter Network Access Server Application
Normatively referenced by — RFC 5259: Internet Message Access Protocol - CONVERT Extension
Normatively referenced by — RFC 5524: Extended URLFETCH for Binary and Converted Parts
Normatively referenced by — RFC 5550: The Internet Email to Support Diverse Service Environments (Lemonade) Profile
Normatively referenced by — RFC 7155: Diameter Network Access Server Application
Normatively referenced by — RFC 7888: IMAP4 Non-synchronizing Literals
Informatively referenced by — RFC 4978: The IMAP COMPRESS Extension
Informatively referenced by — RFC 4416: Goals for Internet Messaging to Support Diverse Service Environments