metasystema.org
UpdatedPROPOSED STANDARDLegacy stream

RFC 3502: Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension

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

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

This document describes the multiappending extension to the Internet Message Access Protocol (IMAP) (RFC 3501). This extension provides substantial performance improvements for IMAP clients which upload multiple messages at a time to a mailbox on the server. A server which supports this extension indicates this with a capability name of "MULTIAPPEND". [STANDARDS-TRACK]

Document record

Document ID
RFC3502
Published
March 2003
Authors
M. Crispin
Status
PROPOSED STANDARD
Stream
Legacy
Area
—
Pages
7
Also known as
—
Updated by:
RFC 4466, RFC 4469

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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 . RFCs are never revised after publication; changes are issued as new documents.

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

canonical URL: /rfc/3502-internet-message-access-protocol-imap-multiappend-extension