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


        RFC 2061:

        Title:      IMAP4 COMPATIBILITY WITH IMAP2BIS
        Author:     M. Crispin
        Date:       December 1996
        Mailbox:    MRC@CAC.Washington.EDU
        Pages:      3
        Characters: 5,867
        Updates/Obsoletes:  none

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


The Internet Message Access Protocol (IMAP) has been through several
revisions and variants in its 10-year history.  Many of these are
either extinct or extremely rare; in particular, several undocumented
variants and the variants described in RFC 1064, RFC 1176, and RFC
1203 fall into this category.  One variant, IMAP2bis, is at the time
of this writing very common and has been widely distributed with the
Pine mailer.  Unfortunately, there is no definite document describing
IMAP2bis.  This document is intended to be read along with RFC 1176
and the most recent IMAP4 specification (RFC 2060) to assist
implementors in creating an IMAP4 implementation to interoperate with
implementations that conform to earlier specifications.  Nothing in
this document is required by the IMAP4 specification; implementors
must decide for themselves whether they want their implementation to
fail if it encounters old software.  At the time of this writing,
IMAP4 has been updated from the version described in RFC 1730.  An
implementor who wishes to interoperate with both RFC 1730 and RFC 2060
should refer to both documents.

This memo provides information for the Internet community.  This memo
does not specify an Internet standard of any kind.  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