[JAMES-3754] Support IMAP4 Rev 2

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: IMAPServer
• Assignee: Unassigned
• Reporter: Benoit Tellier
• Created: 21/Apr/22 05:12
• Updated: 04/Nov/24 08:59

Description

Support IMAP 4 Rev 2 (RFC-9051).

A compatibility notice is available here: https://datatracker.ietf.org/doc/html/rfc9051#appendix-E

Here is a list of actions needed:

• Advertise IMAP4Rev2 capability and support enabling it.
• LIST-EXTENDED [RFC5258]
• LIST-STATUS [RFC5819]
• Response codes [RFC5530]
• FETCH side of the BINARY extension [RFC3516]
• List of new mailbox attributes from SPECIAL-USE [RFC6154]
• STATUS SIZE [RFC8438]
• STATUS DELETED cf https://datatracker.ietf.org/doc/html/rfc9051#section-6.3.11
• SELECT/EXAMINE are now required to return an untagged LIST response.
• Clarified that the server doesn't need to send a new PERMANENTFLAGS response code when a new keyword was successfully added and the server advertised * earlier for the same mailbox.
• Mailbox names and message headers now allow for UTF-8.
• All unsolicited FETCH updates are required to include UID.
• Required COPY/MOVE to return the TRYCREATE response code, if the target mailbox doesn't exist and can be created.

Open question: how to test inter operability / conformity?

• Use clients that are IMAP4Rev2 compliant?
• Find some IMAP4Rev2 test suite in the wild?

Issue Links

• links to: GitHub Pull Request #1329
• links to: GitHub Pull Request #1331
• links to: GitHub Pull Request #1338
• links to: GitHub Pull Request #1339
• links to: GitHub Pull Request #1342
• links to: GitHub Pull Request #1350
• links to: GitHub Pull Request #1353
• links to: GitHub Pull Request #1354
• links to: GitHub Pull Request #1360
• links to: GitHub Pull Request #1367
• links to: GitHub Pull Request #1439
• links to: GitHub Pull Request #2478

Sub-Tasks

• Support RFC-8438 IMAP STATUS=SIZE: Closed