Internet Message Access Protocol (IMAP) - Version 4rev2
draft-ietf-extra-imap4rev2-30
- Versions
- 00
- 01
- 02
- 03
- 04
- 05
- 06
- 07
- 08
- 09
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
Document | Type | Active Internet-Draft (extra WG) | ||
---|---|---|---|---|
Authors | Alexey Melnikov , Barry Leiba | |||
Last updated | 2021-02-22 (latest revision 2021-02-16) | |||
Replaces | draft-melnikov-imap4rev2 | |||
Stream | Internent Engineering Task Force (IETF) | |||
Intended RFC status | Proposed Standard | |||
Formats | plain text xml pdf htmlized (tools) htmlized bibtex | |||
Reviews | ||||
Stream | WG state | Submitted to IESG for Publication (wg milestone: Nov 2020 - Submit "IMAP4rev2" t... ) | ||
On Agenda | extra at IETF-110 | |||
Document shepherd | Bron Gondwana | |||
Shepherd write-up | Show (last changed 2020-11-18) | |||
IESG | IESG state | RFC Ed Queue | ||
Action Holders |
(None)
|
|||
Consensus Boilerplate | Yes | |||
Telechat date | ||||
Responsible AD | Murray Kucherawy | |||
Send notices to | (None) | |||
IANA | IANA review state | IANA OK - Actions Needed | ||
IANA action state | Waiting on Authors | |||
RFC Editor | RFC Editor state | EDIT | ||
Details |
Network Working Group A. Melnikov, Ed. Internet-Draft Isode Ltd Obsoletes: 3501 (if approved) B. Leiba, Ed. Intended status: Standards Track Futurewei Technologies Expires: August 20, 2021 February 16, 2021 Internet Message Access Protocol (IMAP) - Version 4rev2 draft-ietf-extra-imap4rev2-30 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, RFC 2045 and RFC 2231 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 does not specify a means of posting mail; this function is handled by a mail submission protocol such as the one specified in RFC 6409. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on August 20, 2021. Melnikov & Leiba Expires August 20, 2021 [Page 1] Internet-Draft IMAP4rev2 February 2021 Copyright Notice Copyright (c) 2021 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. How to Read This Document . . . . . . . . . . . . . . . . . . 5 1.1. Organization of This Document . . . . . . . . . . . . . . 5 1.2. Conventions Used in This Document . . . . . . . . . . . . 5 1.3. Special Notes to Implementors . . . . . . . . . . . . . . 6 2. Protocol Overview . . . . . . . . . . . . . . . . . . . . . . 7 2.1. Link Level . . . . . . . . . . . . . . . . . . . . . . . 7 2.2. Commands and Responses . . . . . . . . . . . . . . . . . 7 2.2.1. Client Protocol Sender and Server Protocol Receiver . 8 2.2.2. Server Protocol Sender and Client Protocol Receiver . 8 2.3. Message Attributes . . . . . . . . . . . . . . . . . . . 9 2.3.1. Message Numbers . . . . . . . . . . . . . . . . . . . 9 2.3.2. Flags Message Attribute . . . . . . . . . . . . . . . 12 2.3.3. Internal Date Message Attribute . . . . . . . . . . . 14 2.3.4. [RFC-5322] Size Message Attribute . . . . . . . . . . 14 2.3.5. Envelope Structure Message Attribute . . . . . . . . 14 2.3.6. Body Structure Message Attribute . . . . . . . . . . 14 2.4. Message Texts . . . . . . . . . . . . . . . . . . . . . . 15Show full document text