Browse Prior Art Database

INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1 (RFC3501)

IP.com Disclosure Number: IPCOM000011810D
Original Publication Date: 2003-Mar-01
Included in the Prior Art Database: 2003-Mar-18

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 mailboxes (remote message folders) in a way that is functionally equivalent to local folders. IMAP4rev1 also provides the capability for an offline client to resynchronize with the server.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 1% of the total text.

Network Working Group                                         M. Crispin

Request for Comments: 3501                      University of Washington

Obsoletes: 2060                                               March 2003

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.

Copyright Notice

   Copyright (C) The Internet Society (2003).  All Rights Reserved.

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 mailboxes (remote

   message folders) in a way that is functionally equivalent to local

   folders.  IMAP4rev1 also provides the capability for an offline

   client to resynchronize with the server.

   IMAP4rev1 includes operations for creating, deleting, and renaming

   mailboxes, checking for new messages, permanently removing messages,

   setting and clearing flags, RFC 2822 and RFC 2045 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 RFC 2244.

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

   handled by a mail transfer protocol such as RFC 2821.

Crispin                     Standards Track                     [Page 1]

RFC 3501                         IMAPv4                       March 2003

Table of Contents

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

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

   1.1.    Organization of This Document ...........................  4

   1.2.    Conventions Used in This Document .......................  4

   1.3.    Special Notes to Implementors ...........................  5

   2.      Protocol Overview .......................................  6

   2.1.    Link Level ..............................................  6

   2.2.    Commands and Responses ..................................  6

   2.2.1.  Client Protocol Sender and Server Protocol Receiver .....  6

   2.2.2.  Server Protocol Sender and Client Protoco...