IMAP Access to IETF Email List Archives

The IETF makes heavy use of email lists to conduct its work. This often involves accessing the archived history of those email lists. Requirements for improved web-based browsing and searching of these archives are captured in . Participants would like to have the ability to browse and search those archives using standard IMAP clients. This memo captures the requirements for providing a service that would allow such browsing and searching. Discussion of this memo should take place on the ietf@ietf.org mailing list.

Many participants would prefer to access the list archives using IMAP . Providing this access while meeting the following requirements will likely require an IMAP server with specialized capabilities. The system should expose the archive using an IMAP interface, with each list represented as a mailbox. This interface must work with standard IMAP clients. The interface should allow users that have provided credentials to each have their own read/unread marks for messages. Allowing other annotation is desirable. The implementation should consider taking advantage of the IMAP extensions for ANNOTATE and METADATA . The interface must allow administrators to disable setting read/unread marks and other annotations, and delete any such marks or annotations on a per user basis. The interface must not allow users to modify the underlying message or metadata other than the read/unread marks and annotations described above. Specifically, users must not be able to delete or insert messages, or move them between mailboxes in the archive. (Clients will, of course, be able to make local copies of messages from the archive.) The interface must have server-side searching enabled, and should support multiple simultaneous extensive searches. The server should facilitate the enhanced search capabilities described in . The implementation should consider taking advantage of the extensions defined for IMAP SORT and THREAD , multimailbox search , and fuzzy search . When the system requires credentials, it must use the datatracker's authentication system While the vast majority of archived lists have an open access policy, some archived lists have restricted archives. The system must make it possible to limit access to a restricted archive based on login credentials. The system must not require credentials for accessing lists with open archives. (But it is acceptable for a user to access such archives while providing credentials). Specifically, the system will allow anonymous access using the SASL ANONYMOUS authentication mechanism or an LOGIN command with a special username (such as "anonymous") determined by the administrator .

Allowing IMAP as an interface for browsing and searching the archives of IETF email lists does not affect the security of the Internet in any significant fashion. Searching can be I/O and CPU intensive. Clients that make local copies all messages in a mailbox can also present an I/O burden, particularly when syncronizing for the first time. The implementors of this interface should consider the potential for maliciously crafted searches attempting to consume all available resources. The implementors should consider the potential for denial of service attacks through making many connections to the interface. The implementors should consider ways to rate limit I/O due to making local copies of messages. Storing read/unread marks and other annotations requires potentially unbounded storage space. The implementors of this interface should consider the potential for maliciously crafted annontations attempting to consume all storage space. The implementers should consider making it easy for the administrator to determine which users are consuming exceptional space.

This document has no actions for IANA.

This text was derived directly from an early version of the Internet Draft that became which incorporated text suggestions from Alexey Melnikov, Pete Resnick, and S. Moonesamy. Barry Leiba suggested several references to IMAP extensions for an implementation to consider.

Added a requirement making it explicit that this interface won't allow users to delete, insert, or move messages between archives. Clarified how the would allow access without credentials (at Alexey's suggestion). Pointed to potential resource abuse issues in the security considerations section.

Adapted text from RFC6778 to make it more clear that both authenticated and unauthenticated access should be supported.

Incorporated suggestions from Pete Resnick and Barry Leiba.

None - expiry refresh

Minor editorial changes

Added requirements to enable controlled access to restricted archives based on credentials Generalized the requirement to use the datatracker's credentials.

Split this set of requirements out from the mailarch doc so that this project could be pursued separately