RFC 1731: IMAP4 Authentication Mechanisms
In plain English — editorial summary, not part of the RFC
The Internet Message Access Protocol, Version 4 [IMAP4] contains the AUTHENTICATE command, for identifying and authenticating a user to an IMAP4 server and for optionally negotiating a protection mechanism for subsequent protocol interactions. This document describes several authentication mechanisms for use by the IMAP4 AUTHENTICATE command. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1731
- Published
- December 1994
- Authors
- J. Myers
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1732IMAP4 Compatibility with IMAP2 and IMAP2bisCurrent
December 1994
- RFC 1733Distributed Electronic Mail Models in IMAP4Current
December 1994
- RFC 5092IMAP URL SchemeUpdated
November 2007
- RFC 2060Internet Message Access Protocol - Version 4rev1Obsoleted
December 1996
- RFC 2061IMAP4 Compatibility with IMAP2bisCurrent
December 1996
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 1997
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?