database logo graphic

RFC 3516

"IMAP4 Binary Content Extension", April 2003

Canonical URL:
http://www.rfc-editor.org/rfc/rfc3516.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Updated by:
RFC 4466
Author:
L. Nerenberg
Stream:
INDEPENDENT

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.