Internet Message Access Protocol (IMAP)

This document extends Internet Message Access Protocol (IMAP) with a new capability called "SAVEDATE". This capability adds a new IMAP message attribute called 'save date'. The save date is the date and time at which a message was saved in the mailbox it currently resides. The save date is similar to the existing internal date attribute in that it is set at the time of delivery. However, the internal date attribute can be set to an arbitrary value for messages delivered to the mailbox using the APPEND command and it is usually copied from the source message for messages delivered using the COPY command. In contrast, the save date attribute is always set to the current date and time at the moment the message is saved in the mailbox, irrespective of how the message is delivered and from where it originates. The save date message attribute is useful for implementing automated removal of messages from a mailbox after a configured amount of time. For that application, it is necessary to know when the message was saved in the mailbox, which cannot be reliably determined using the the internal date attribute. For example, a common client usage pattern is to move deleted messages to a Trash mailbox; these messages are considered "deleted" at the time they are moved to the Trash mailbox. In an effort to limit the size of the Trash mailbox, a client may subsequently desire to permanently remove (expunge) all messages in that Trash mailbox deleted before a certain time (e.g. a configurable expiration interval). In that case, the internal date attribute cannot be used, since it likely refers to the time at which the message was originally received. The proper time comparison attribute should instead be the time at which the message was saved to the Trash mailbox. Similar usage patterns can be observed for Archiving solutions. The SAVEDATE capability extends the FETCH command and response to allow retrieving the date and time at which a message was saved. Also, the SAVEDATE capability extends the SEARCH command to allow searching messages with criteria based on when it was saved in the mailbox.

In examples, "C:" indicates lines sent by a client that is connected to a server. "S:" indicates lines sent by the server to the client. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in .

The save date message attribute is the date and time at which the message was saved in the mailbox it is now located in. Unlike the internal date attribute defined by , this date and time value cannot be set arbitrarily when a message is delivered by the IMAP APPEND command. Also, when a message is delivered to the mailbox by the IMAP COPY command or the IMAP MOVE command, the save date attribute is not copied from the source message. Instead, the current date and time at which the message is delivered to a mailbox MUST be used to set the save date attribute. Once calculated, the save date attribute MUST NOT change as long as the message is contained within the same mailbox. This means that when the message is copied to another mailbox, the save date of the message in source mailbox remains unaffected; only the new copy of the message gets a new save date. Consequently, when the the message is moved to another mailbox, either using the MOVE command or a command sequence involving the COPY command , the message always gets a new save date in the destination mailbox. For some specific mailboxes, the underlying storage may not support the save date message attribute. The handling of this situation is described in detail in the next section for each involved IMAP command.

IMAP servers that support this extension MUST include "SAVEDATE" in the response list to the CAPABILITY command.

This extension defines one new data item for the FETCH command: The save date of the message. This extension defines one new data item for the FETCH response: A string representing the save date of the message. However, if the underlying mailbox storage does not support the save date message attribute, the value returned for the SAVEDATE item is always NIL, rather than a string. Example:

This extension defines four new search keys for the SEARCH command: Messages whose save date (disregarding time and timezone) is earlier than the specified date. Messages whose save date (disregarding time and timezone) is within the specified date. Messages whose save date (disregarding time and timezone) is within or later than the specified date. Matches all messages in the mailbox when the underlying storage of that mailbox supports the save date attribute. Conversely, it matches no messages in the mailbox when the save date attribute is not supported. When the underlying storage of a mailbox does not support the save date attribute, the SAVEDBEFORE, SAVEDON, and SAVEDSINCE search keys MUST use the internal date attribute instead. In the context of the IMAP Multimailbox SEARCH Extension, this fallback behavior MUST apply to each mailbox individually, meaning that only the mailboxes that lack support for the save date attribute use the internal date attribute instead. Example:

The following syntax specification augments the grammar specified in . It uses the Augmented Backus-Naur Form (ABNF) notation as specified in . Elements not defined here are taken from .

There are no known additional security issues with this extension beyond those described in the base protocol described in .

The IANA is requested to add "SAVEDATE" to the "IMAP Capabilities" registry located at <http://www.iana.org/assignments/imap-capabilities>.

Thanks to Bron Gondwana, Alexey Melnikov, Timo Sirainen, and Michael Slusarz for reviews and suggestions.