A new Request for Comments is now available in online RFC libraries.


        RFC 2060:

        Title:      INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
        Author:     M. Crispin
        Date:       December 1996
        Mailbox:    MRC@CAC.Washington.EDU
        Pages:      82
        Characters: 166,513
        Obsoletes:  1730

        URL:        ftp://ds.internic.net/rfc/rfc2060.txt


The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows
a client to access and manipulate electronic mail messages on a
server.  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
RFC 2062.  Other compatibility issues with IMAP2bis, the most common
variant of the earlier protocol, are discussed in RFC 2061.  A full
discussion of compatibility issues with rare (and presumed extinct)
variants of IMAP2 is in RFC 1732; this document is primarily of
historical interest.

This is now a Proposed Standard Protocol.

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.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@CNRI.RESTON.VA.US.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@ISI.EDU.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@ISI.EDU with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@ISI.EDU
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to admin@DS.INTERNIC.NET.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR@ISI.EDU.  Please consult RFC 1543, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Mary Kennedy
USC/Information Sciences Institute