API Build-data JSON Resources
Theme

Choose how MSRBot.io looks on this device.

Auto (match system) Light mode Dark mode

Preference is stored in this browser only.

IETF RFC 3501
[SUPERSEDED]

INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1

Metadata

Publisher
IETF
Doc Type
Standard
Pages
108
Abstract
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. IMAP4rev1 includes operations for creating, deleting, and renaming mailboxes, checking for new messages, permanently removing messages, setting and clearing flags, RFC 2822 and RFC 2045 parsing, searching, and selective fetching of message attributes, texts, and portions thereof. Messages in IMAP4rev1 are accessed by the use of 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 RFC 2244. IMAP4rev1 does not specify a means of posting mail; this function is handled by a mail transfer protocol such as RFC 2821. [STANDARDS-TRACK]
Publication Date
2003-03-01
Status Note
Proposed Standard
DOI
10.17487/RFC3501
Link
https://doi.org/10.17487/RFC3501
Author(s)
Mark Crispin
Keyword(s)
IMAPV4, IMAP, IMAP4rev1
Latest version of IETF RFC 3501

Document Versions — IETF RFC 3501

  • ▶ IETF RFC 3501 (2003-03-01)
    THIS DOC [SUPERSEDED] [LATEST VERSION]

Superseded by:
  • RFC9051 NOT IN REGISTRY

Amended by:
  • RFC4466 NOT IN REGISTRY
  • RFC4469 NOT IN REGISTRY
  • RFC4551 NOT IN REGISTRY
  • RFC5032 NOT IN REGISTRY
  • RFC5182 NOT IN REGISTRY
  • RFC5738 — RFC5738 EXTERNAL
  • IETF RFC 6186 [Active*]
  • RFC6858 NOT IN REGISTRY
  • RFC7817 NOT IN REGISTRY
  • RFC8314 NOT IN REGISTRY
  • RFC8437 NOT IN REGISTRY
  • RFC8474 NOT IN REGISTRY
  • IETF RFC 8996 [Active*]
Source Data (JSON)

Full registry record with provenance metadata. Open directly: /api/doc/RFC3501.json

Reference Tree

Explore all references and references to this document, as a navigable tree.

Open Reference Tree
Reference this Doc

Plain text (ISO 690 compliant)

Preview:
IETF RFC 3501, INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1. Available at https://doi.org/10.17487/RFC3501
Snippet:
IETF RFC 3501, INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1. Available at https://doi.org/10.17487/RFC3501

HTML (ISO 690 compliant)

Preview:
IETF RFC 3501, INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1. Available at https://doi.org/10.17487/RFC3501
Snippet:
<span class="citation"><cite>IETF RFC 3501</cite>, INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1. Available at <a href="https://doi.org/10.17487/RFC3501" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3501</a></span>

SMPTE Icon SMPTE's HTML Pub

Preview:
IETF RFC 3501, INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
doi: 10.17487/RFC3501
url: https://doi.org/10.17487/RFC3501
Snippet:
<li>
<cite id="bib-rfc3501">IETF RFC 3501</cite>, INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1
<span class="doi">10.17487/RFC3501</span>
</li>

Referenced By