RFC 2221: IMAP4 Login Referrals
In plain English — editorial summary, not part of the RFC
When dealing with large amounts of users and many IMAP4 [RFC-2060] servers, it is often necessary to move users from one IMAP4 server to another. Login referrals allow clients to transparently connect to an alternate IMAP4 server, if their home IMAP4 server has changed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2221
- Published
- October 1997
- Authors
- M. Gahrns
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 5
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2180IMAP4 Multi-Accessed Mailbox PracticeCurrent
July 1997
- RFC 2195IMAP/POP AUTHorize Extension for Simple Challenge/ResponseCurrent
September 1997
- RFC 2192IMAP URL SchemeObsoleted
September 1997
- RFC 2095IMAP/POP AUTHorize Extension for Simple Challenge/ResponseObsoleted
January 1997
- RFC 2088IMAP4 non-synchronizing literalsObsoleted
January 1997
- RFC 2087IMAP4 QUOTA extensionObsoleted
January 1997
- RFC 2086IMAP4 ACL extensionObsoleted
January 1997
- RFC 2359IMAP4 UIDPLUS extensionObsoleted
June 1998
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?