UpdatedPROPOSED STANDARDIETF stream

RFC 3516: IMAP4 Binary Content Extension

Still current, but amended. Parts of this document are changed or extended by RFC 4466. Read both.

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID: RFC3516
Published: April 2003
Authors: L. Nerenberg
Status: PROPOSED STANDARD
Stream: IETF
Area: —
Pages: 8
Also known as: —

Updated by:: RFC 4466

Topics

internet message acess procotol

Referenced by

One later RFC formally updates or obsoletes part of this document.

RFC 4466Collected Extensions to IMAP4 ABNFUpdated
April 2006

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on 23 August 2026. RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?