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


        RFC 1732:

        Title:      IMAP4 COMPATIBILITY WITH IMAP2 AND IMAP2BIS
        Author:     M. Crispin
        Mailbox:    MRC@CAC.Washington.EDU
        Pages:      5
        Characters: 9,276
        Updates/Obsoletes:  none

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


This RFC is a summary of hints and recommendations to enable an IMAP4
implementation to interoperate with implementations that conform to
earlier specifications.  None of these hints and recommendations are
required by the IMAP4 specification; implementors must decide for
themselves whether they want their implementation to fail if it
encounters old software.  IMAP4 has been designed to be upwards
compatible with earlier specifications.  For the most part, IMAP4
facilities that were not in earlier specifications should be invisible
to clients unless the client asks for the facility.  In some cases,
older servers may support some of the capabilities listed as being
"new in IMAP4" as experimental extensions to the IMAP2 protocol
described in RFC 1176.  This information may not be complete; it
reflects current knowledge of server and client implementations as
well as "folklore" acquired in the evolution of the protocol.  This
RFC is a product of the Internet Message Access Protocol Working Group
of the IETF.

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-REQUEST@NIC.DDN.MIL.

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
USC/Information Sciences Institute