LAST CALL: I-D ACTION:draft-crispin-imapv-09.txt (fwd)

[Mark Crispin <[e-mail]>]

I would like to make a last call on the IMAPV document, which is
essentially a bugfix update to RFC 2060.  Please read and review it, since
I would like to submit it as an RFC as the new standards-track bas IMAP
specification.


---------- Forwarded message ----------
Date: Thu, 17 Feb 2000 06:27:25 -0500
From: [e-mail]
To: IETF-Announce:  ;
Subject: I-D ACTION:draft-crispin-imapv-09.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.


	Title		: INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
	Author(s)	: M. Crispin
	Filename	: draft-crispin-imapv-09.txt
	Pages		: 93
	Date		: 16-Feb-00
	
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 (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
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 can 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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-crispin-imapv-09.txt

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-crispin-imapv-09.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	[e-mail].
In the body type:
	"FILE /internet-drafts/draft-crispin-imapv-09.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

ftp://ftp.ietf.org/internet-drafts/draft-crispin-imapv-09.txt"><ftp://ftp.ietf.org/internet-drafts/draft-crispin-imapv-09.txt>