Browse Prior Art Database

Internet Message Access Protocol - Version 4rev1 (RFC2060)

IP.com Disclosure Number: IPCOM000002611D
Original Publication Date: 1996-Dec-01
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

M. Crispin: AUTHOR

Abstract

The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. IMAP4rev1 permits manipulation of remote message folders, called "mailboxes", in a way that is functionally equivalent to local mailboxes. IMAP4rev1 also provides the capability for an offline client to resynchronize with the server (see also [IMAP-DISC]).

This text was extracted from a ASCII document.
This is the abbreviated version, containing approximately 2% of the total text.

Network Working Group M. Crispin

Request for Comments: 2060 University of Washington

Obsoletes: 1730 December 1996

Category: Standards Track

INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1

Status of this Memo

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.

Abstract

The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1)

allows a client to access and manipulate electronic mail messages on

a server. IMAP4rev1 permits manipulation of remote message folders,

called "mailboxes", in a way that is functionally equivalent to local

mailboxes. IMAP4rev1 also provides the capability for an offline

client to resynchronize with the server (see also [IMAP-DISC]).

IMAP4rev1 includes operations for creating, deleting, and renaming

mailboxes; checking for new messages; permanently removing messages;

setting and clearing flags; [RFC-822] and [MIME-IMB] parsing;

searching; and selective fetching of message attributes, texts, and

portions thereof. Messages in IMAP4rev1 are accessed by the use of

numbers. These numbers are either message sequence numbers or unique

identifiers.

IMAP4rev1 supports a single server. A mechanism for accessing

configuration information to support multiple IMAP4rev1 servers is

discussed in [ACAP].

IMAP4rev1 does not specify a means of posting mail; this function is

handled by a mail transfer protocol such as [SMTP].

IMAP4rev1 is designed to be upwards compatible from the [IMAP2] and

unpublished IMAP2bis protocols. In the course of the evolution of

IMAP4rev1, some aspects in the earlier protocol have become obsolete.

Obsolete commands, responses, and data formats which an IMAP4rev1

implementation may encounter when used with an earlier implementation

are described in [IMAP-OBSOLETE].

Other compatibility issues with IMAP2bis, the most common variant of

the earlier protocol, are discussed in [IMAP-COMPAT]. A full

discussion of compatibility issues with rare (and presumed extinct)

variants of [IMAP2] is in [IMAP-HISTORICAL]; this document is

primarily of historical interest.

Table of Contents

IMAP4rev1 Protocol Specification .................................. 4

1. How to Read This Document ................................. 4