metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4469: Internet Message Access Protocol (IMAP) CATENATE Extension

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

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

The CATENATE extension to the Internet Message Access Protocol (IMAP) extends the APPEND command to allow clients to create messages on the IMAP server that may contain a combination of new data along with parts of (or entire) messages already on the server. Using this extension, the client can catenate parts of an already existing message onto a new message without having to first download the data and then upload it back to the server. [STANDARDS-TRACK]

Document record

Document ID
RFC4469
Published
April 2006
Authors
P. Resnick
Status
PROPOSED STANDARD
Stream
IETF
Area
app
Pages
13
Also known as
—
Updates:
RFC 3501, RFC 3502
Updated by:
RFC 5550

Topics

Referenced by

One later RFC formally updates or obsoletes 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/4469-internet-message-access-protocol-imap-catenate-extension