RFC 3516 · PROPOSED STANDARD · 2003
WED · 29 JUL 2026
IMAP4 Binary Content Extension
Overview
RFC 3516, “IMAP4 Binary Content Extension”, is a Proposed Standard document published in April 2003 by L. Nerenberg. It has since been updated by RFC 4466. The canonical text is published by the RFC Editor.
Abstract
This memo defines the Binary extension to the Internet Message Access Protocol (IMAP4). It provides a mechanism for IMAP4 clients and servers to exchange message body data without using a MIME content-transfer- encoding. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
Read this RFC
The canonical text of RFC 3516 is hosted at rfc-editor.org. Available in TXT,HTML.
Relationships to other RFCs
Other RFCs from 2003
- RFC 3515 The Session Initiation Protocol Refer Method
- RFC 3517 A Conservative Selective Acknowledgment -based Loss Recovery Algorithm for TCP
- RFC 3514 The Security Flag in the IPv4 Header
- RFC 3518 Point-to-Point Protocol Bridging Control Protocol
- RFC 3513 Internet Protocol Version 6 Addressing Architecture
- RFC 3519 Mobile IP Traversal of Network Address Translation Devices
- RFC 3512 Configuring Networks and Devices with Simple Network Management Protocol
- RFC 3520 Session Authorization Policy Element