Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension
The information below is for an old version of the document that is already published as an RFC.
This is an older version of an Internet-Draft that was ultimately published as RFC 3502.
|Last updated||2013-03-02 (Latest revision 2002-09-27)|
|RFC stream||Legacy stream|
|RFC Editor Note||(None)|
|IESG||IESG state||RFC 3502 (Proposed Standard)|
|Responsible AD||Ned Freed|
|Send notices to||<firstname.lastname@example.org>|
A new Request for Comments is now available in online RFC libraries. RFC 3502 Title: Internet Message Access Protocol (IMAP) - MULTIAPPEND Extension Author(s): M. Crispin Status: Standards Track Date: March 2003 Mailbox: MRC@CAC.Washington.EDU Pages: 7 Characters: 13379 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-crispin-imap-multiappend-07.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3502.txt 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". This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information.