idnits 2.17.1 draft-crispin-imapv-20.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 3501 5 Title: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 6 Author(s): M. Crispin 7 Status: Standards Track 8 Date: March 2003 9 Mailbox: MRC@CAC.Washington.EDU 10 Pages: 108 11 Characters: 227640 12 Obsoletes: 2060 14 I-D Tag: draft-crispin-imapv-20.txt 16 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3501.txt 18 The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows 19 a client to access and manipulate electronic mail messages on a 20 server. IMAP4rev1 permits manipulation of mailboxes (remote message 21 folders) in a way that is functionally equivalent to local folders. 22 IMAP4rev1 also provides the capability for an offline client to 23 resynchronize with the server. 25 IMAP4rev1 includes operations for creating, deleting, and renaming 26 mailboxes, checking for new messages, permanently removing messages, 27 setting and clearing flags, RFC 2822 and RFC 2045 parsing, 28 searching, and selective fetching of message attributes, texts, and 29 portions thereof. Messages in IMAP4rev1 are accessed by the use of 30 numbers. These numbers are either message sequence numbers or unique 31 identifiers. 33 IMAP4rev1 supports a single server. A mechanism for accessing 34 configuration information to support multiple IMAP4rev1 servers is 35 discussed in RFC 2244. 37 IMAP4rev1 does not specify a means of posting mail; this function is 38 handled by a mail transfer protocol such as RFC 2821. 40 This is now a Proposed Standard Protocol. 42 This document specifies an Internet standards track protocol for 43 the Internet community, and requests discussion and suggestions 44 for improvements. Please refer to the current edition of the 45 "Internet Official Protocol Standards" (STD 1) for the 46 standardization state and status of this protocol. Distribution 47 of this memo is unlimited. 49 This announcement is sent to the IETF list and the RFC-DIST list. 50 Requests to be added to or deleted from the IETF distribution list 51 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 52 added to or deleted from the RFC-DIST distribution list should 53 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 55 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 56 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 57 help: ways_to_get_rfcs. For example: 59 To: rfc-info@RFC-EDITOR.ORG 60 Subject: getting rfcs 62 help: ways_to_get_rfcs 64 Requests for special distribution should be addressed to either the 65 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 66 specifically noted otherwise on the RFC itself, all RFCs are for 67 unlimited distribution.echo 68 Submissions for Requests for Comments should be sent to 69 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 70 Authors, for further information.