We won't be implementing IMAP UNAUTHENTICATE.

Doesn't seem like it's a common thing to do. And it's just a bit risky, it's
too easy to forget to clear some part of the authentication state on a
connection (especially future changes that forget to update clear a new field
during unauthenticate). If a strong use case ever pops up, we can reconsider.

Also update the roadmap a bit.
This commit is contained in:
Mechiel Lukkien
2025-03-12 10:01:00 +01:00
parent 60da7f34b8
commit 0cf0bfb8a6
2 changed files with 3 additions and 3 deletions

View File

@ -226,7 +226,7 @@ https://www.iana.org/assignments/message-headers/message-headers.xhtml
7377 Roadmap - IMAP4 Multimailbox SEARCH Extension
7888 Yes - IMAP4 Non-synchronizing Literals
7889 Yes - The IMAP APPENDLIMIT Extension
8437 Roadmap - IMAP UNAUTHENTICATE Extension for Connection Reuse
8437 No - IMAP UNAUTHENTICATE Extension for Connection Reuse
8438 Yes - IMAP Extension for STATUS=SIZE
8440 ? - IMAP4 Extension for Returning MYRIGHTS Information in Extended LIST
8457 No - IMAP "$Important" Keyword and "\Important" Special-Use Attribute