INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev2
draft-melnikov-imap4rev2-04
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Alexey Melnikov | ||
| Last updated | 2016-04-20 (Latest revision 2015-10-18) | ||
| Replaced by | draft-ietf-extra-imap4rev2, draft-ietf-extra-imap4rev2, RFC 9051 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The Internet Message Access Protocol, Version 4rev2 (IMAP4rev2) allows a client to access and manipulate electronic mail messages on a server. IMAP4rev2 permits manipulation of mailboxes (remote message folders) in a way that is functionally equivalent to local folders. IMAP4rev2 also provides the capability for an offline client to resynchronize with the server. IMAP4rev2 includes operations for creating, deleting, and renaming mailboxes, checking for new messages, permanently removing messages, setting and clearing flags, RFC 5322 and RFC 2045 parsing, searching, and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4rev2 are accessed by the use of numbers. These numbers are either message sequence numbers or unique identifiers. IMAP4rev2 supports a single server. A mechanism for accessing configuration information to support multiple IMAP4rev2 servers is discussed in RFC 2244. IMAP4rev2 does not specify a means of posting mail; this function is handled by a mail submission protocol such as RFC 6409.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)