RFC 8437 Proposed Standard Submission and access

IMAP UNAUTHENTICATE Extension for Connection Reuse

This specification extends the Internet Message Access Protocol (IMAP) to allow an administrative client to reuse the same IMAP connection on behalf of multiple IMAP user identities.

Status
Proposed Standard. On the standards track and stable enough to implement against. Most of the email stack stays at this level permanently.
Published
August 2018
Authors
C. Newman
Read it
rfc-editor.org · DOI

Normative requirements

Every sentence in this RFC carrying an RFC 2119 keyword, with the section it came from. 4 must, 0 should, 2 may.

3 UNAUTHENTICATE Command

  • MAYServers MAY close the connection with an untagged BYE response if this preferably rare situation occurs.
  • MAYServers MAY choose to advertise the UNAUTHENTICATE capability only after authentication has completed.

4.1 Stateful Extensions

  • MUSTThe connection state for the following list of IMAP extensions MUST be reset if both a) the specified extension is advertised and b) the UNAUTHENTICATE command is advertised and used.
  • MUSTo Cached identity information, such as group memberships, that are used to evaluate access control lists [RFC4314] MUST be reset.
  • MUSTo After an UNAUTHENTICATE command is issued, CONDSTORE servers [RFC7162] MUST behave as if no CONDSTORE-enabling command was issued.

8 Security Considerations

  • MUSTAs a result, IMAP server implementations of this extension MUST provide a way to disable it when it is not needed.

Every current email RFC