RFC 2342: IMAP4 Namespace
In plain English — editorial summary, not part of the RFC
This document defines a NAMESPACE command that allows a client to discover the prefixes of namespaces used by a server for personal mailboxes, other users' mailboxes, and shared mailboxes. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2342
- Published
- May 1998
- Authors
- M. Gahrns; C. Newman
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
- Updated by:
- RFC 4466
Topics
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.
- RFC 2595Using TLS with IMAP, POP3 and ACAPUpdated
June 1999
- RFC 2971IMAP4 ID extensionCurrent
October 2000
- RFC 3503Message Disposition Notification (MDN) profile for Internet Message Access Protocol (IMAP)Current
March 2003
- RFC 3501INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1Obsoleted
March 2003
- RFC 3598Sieve Email Filtering -- Subaddress ExtensionObsoleted
September 2003
- RFC 3656The Mailbox Update (MUPDATE) Distributed Mailbox Database ProtocolUpdated
December 2003
- RFC 3691Internet Message Access Protocol (IMAP) UNSELECT commandCurrent
February 2004
- RFC 3741Exclusive XML Canonicalization, Version 1.0Current
March 2004
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?