metasystema.org
ObsoletedPROPOSED STANDARDLegacy stream

RFC 2060: Internet Message Access Protocol - Version 4rev1

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3501.

Current document in this lineage: RFC 2061 — IMAP4 Compatibility with IMAP2bis; RFC 9051 — Internet Message Access Protocol (IMAP) - Version 4rev2

In plain English — editorial summary, not part of the RFC

The Internet Message Access Protocol, Version 4rev1 (IMAP4rev1) allows a client to access and manipulate electronic mail messages on a server. [STANDARDS-TRACK]

Document record

Document ID
RFC2060
Published
December 1996
Authors
M. Crispin
Status
PROPOSED STANDARD
Stream
Legacy
Area
—
Pages
82
Also known as
—
Obsoletes:
RFC 1730
Obsoleted by:
RFC 3501

Topics

Standards lineage

This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.

  1. RFC 1730 (1994)
  2. RFC 2060 (1996)
  3. RFC 2061 (1996)
  4. RFC 3501 (2003)
  5. RFC 9051 (2021) ✓

Read the full history of Internet Message Access Protocol (IMAP) - Version 4rev2 →

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/2060-internet-message-access-protocol-version-4rev1