idnits 2.17.1 draft-crispin-imap-multiappend-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3502 5 Title: Internet Message Access Protocol (IMAP) - 6 MULTIAPPEND Extension 7 Author(s): M. Crispin 8 Status: Standards Track 9 Date: March 2003 10 Mailbox: MRC@CAC.Washington.EDU 11 Pages: 7 12 Characters: 13379 13 Updates/Obsoletes/SeeAlso: None 15 I-D Tag: draft-crispin-imap-multiappend-07.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3502.txt 19 This document describes the multiappending extension to the Internet 20 Message Access Protocol (IMAP) (RFC 3501). This extension 21 provides substantial performance improvements for IMAP clients which 22 upload multiple messages at a time to a mailbox on the server. 24 A server which supports this extension indicates this with a 25 capability name of "MULTIAPPEND". 27 This is now a Proposed Standard Protocol. 29 This document specifies an Internet standards track protocol for 30 the Internet community, and requests discussion and suggestions 31 for improvements. Please refer to the current edition of the 32 "Internet Official Protocol Standards" (STD 1) for the 33 standardization state and status of this protocol. Distribution 34 of this memo is unlimited. 36 This announcement is sent to the IETF list and the RFC-DIST list. 37 Requests to be added to or deleted from the IETF distribution list 38 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 39 added to or deleted from the RFC-DIST distribution list should 40 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 42 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 43 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 44 help: ways_to_get_rfcs. For example: 46 To: rfc-info@RFC-EDITOR.ORG 47 Subject: getting rfcs 49 help: ways_to_get_rfcs 51 Requests for special distribution should be addressed to either the 52 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 53 specifically noted otherwise on the RFC itself, all RFCs are for 54 unlimited distribution.echo 55 Submissions for Requests for Comments should be sent to 56 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 57 Authors, for further information.