The Lemonade Profile

In examples, "M:", "I:" and "S:" indicate lines sent by the client messaging user agent, IMAP e-mail server and SMTP submit server respectively. 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 . Other capitalised words are typically names of extensions or commands - these are uppercased for clarity only, and are case-insensitive. All examples in this document are optimized for Lemonade use and might not represent examples of proper protocol usage for a general use Submit/IMAP client. In particular, examples assume that Submit and IMAP servers support all Lemonade extensions described in this document, so they do not demonstrate fallbacks in the absence of an extension.

The Lemonade Profile, or simply Lemonade, provides enhancements to Internet email to support diverse service environments. Lemonade Mail Servers provide both a Lemonade Submission Server and a Lemonade Message Store, which are based on the existing and protocols respectively. They MAY also include a Lemonade Message Delivery Agent, which provides delivery-time filtering services based on . This document describes the Lemonade profile that includes: General common enhancements to Internet Mail, described in and . "Forward without download" that describes exchanges between Lemonade clients and servers to allow to submit new email messages incorporating content which resides on locations external to the client, described in . Quick mailbox resynchronization, described in . Extensions to support more precise, and broader, notifications from the store in support of notifications and view filters, described in and . Delivery-time filtering in support of typical mail management use-cases, as described in . It is intended that the Lemonade profile support realizations of the OMA's mobile email enabler (MEM) (see and ) using Internet Mail protocols defined by the IETF.

Lemonade Submission Servers MUST provide a service as described in , and MUST support the following. Note that the Lemonade Profile imposes further requirements for some cases, detailed in the sections cited. SMTP extension Reference Requirements PIPELINING DSN SIZE ENHANCEDSTATUSCODES STARTTLS BURL imap BINARYMIME CHUNKING 8BITMIME AUTH

Lemonade Message Stores MUST provide a service as described in , and MUST support the following. Note that the Lemonade Profile imposes further requirements for some cases, detailed in the sections cited. IMAP extension Reference Requirements NAMESPACE CONDSTORE STARTTLS- URLAUTH CATENATE URL-PARTIAL UIDPLUS LITERAL+ IDLE NOTIFY $Forwarded keyword- $SubmitPending keyword- $Submitted keyword- BINARY QRESYNC ENABLE ESEARCH CONTEXT=SEARCH SORT ESORT CONTEXT=SORT CONVERT COMPRESS=DEFLATE I18NLEVEL=1 SASL-IR In addition to this list, any Lemonade Message Stores MUST send the CAPABILITY response code (see Section 7.1 of ) in the initial server greeting and after the LOGIN/AUTHENTICATE commands.

Lemonade Message Delivery Agents MUST support Sieve mail filtering language as described in , and MUST support the following Sieve extensions. Note that the Lemonade Profile imposes further requirements for some cases, detailed in the sections cited. Sieve extension Reference Requirements VACATION ENOTIFY VARIABLES RELATIONAL IMAP4FLAGS comparator-i;unicode-casemap Lemonade Message Delivery Agents should also consider supporting a Sieve script management protocol, such as .

All Lemonade Submission Servers implement the Mail Submission protocol described in , which is in turn a specific profile of . Therefore any MUA designed to submit email via or will interoperate with Lemonade Submission Servers. In addition, Lemonade Submission Servers implement the following set of SMTP and Submission extensions to increase message submission efficiency.

In order to optimize network usage for the typical case where message content is copied to, or sourced from, the IMAP store, Lemonade provides support for a suite of extensions collectively known as Forward Without Download, discussed in detail in . Lemonade Submission Servers MUST support the BURL , 8BITMIME , BINARYMIME and CHUNKING . BURL MUST support URLAUTH type URLs , and thus MUST advertise the "imap" option following the BURL EHLO keyword (See for more details).

Some clients regularly use networks with a relatively high latency, such as Mobile or Satellite based networks. Avoidance of round-trips within a transaction has a great advantage for the reduction in both bandwidth and total transaction time. For this reason Lemonade compliant mail submission servers MUST support the SMTP Service Extensions for Command Pipelining .

Lemonade compliant mail submission servers MUST support SMTP service extensions for delivery status notifications .

There is a distinct advantage in detecting failure cases as early as possible in many cases, such as where the user is charged per-octet, or where bandwidth is low. This is especially true of large message sizes. Lemonade Submission Servers MUST support the SMTP Service Extension for Message Size Declaration . Lemonade Submission Servers MUST NOT consider a supplied message size to be acceptable without expanding all BURL parts. A Lemonade capable client SHOULD use message size declaration. In particular the client MUST NOT send a message to a mail submission server, if it knows that the message exceeds the maximal message size advertised by the submission server. When including a message size in the MAIL FROM command, the client MUST use a value that is at least as large as the size of the assembled message data after resolution of all BURL parts.

Lemonade compliant mail submission servers MUST support SMTP Service Extension for Returning Enhanced Error Codes . These allow a client to determine the precise cause of failure.

Lemonade Compliant mail submission servers MUST support SMTP Service Extension for Secure SMTP over TLS . Support for the DEFLATE compression method, as described in , is RECOMMENDED.

All Lemonade Message Stores implement Internet Message Access Protocol, as defined in . Therefore any MUA written to access messages using the facilities described in will interoperate with a Lemonade Message Store. In addition, Lemonade Message Stores provide a set of extensions to address the limitations of some clients and networks.

Resynchronization is a costly part of an IMAP session, and mobile networks are generally more prone to unintended disconnection, which in turns makes this problem more acute. Therefore Lemonade Message Stores provide a suite of extensions to reduce the synchronization cost. Lemonade Compliant IMAP servers MUST support the CONDSTORE , the QRESYNC and the ENABLE extensions. These allow a client to quickly resynchronize any mailbox by asking the server to return all flag changes and expunges that have occurred since a previously recorded state. This can also speed up client reconnect in case the transport layer is cut, whether accidentally or as part of a change in network. details how clients perform efficient mailbox resynchronization.

The handling of message parts, especially attachments, represents a set of challenges to limited devices, both in terms of the bandwidth used, and the capability of the device. Lemonade Compliant IMAP servers MUST support the BINARY extension. This moves MIME body part decoding operations from the client to the server. The decoded data is always equal or less than the encoded representation, so this reduces bandwidth effectively. allows for servers to refuse to accept uploaded messages containing binary data, by not accepting the Binary content-transfer-encoding; however Lemonade Compliant IMAP servers SHALL always accept binary encoded MIME messages in APPEND commands for any folder. MUST also be supported by servers, which allows clients to request conversions between media types, and allows for scaling images, etc. This provides the ability to view attachments (and sometimes body parts) without the facility to cope with a wide range of media types, or to efficiently view attachments.

The IETF has for some time generally agreed that compression is best handled at as low a level as possible, therefore Lemonade Message Stores SHOULD support the Deflate compression algorithm for TLS, as defined in . However, the working group acknowledges that for many endpoints, this is a rarely deployed technology, and as such, Lemonade Message Stores MUST provide support for fallback application-level stream compression, where TLS is not actively providing compression.

The addition of Server-to-client notifications ransforms the LEMONADE profile into an event-based synchronization protocol. Whenever an event occurs that interests the MUA, a notification can be generated. If the MUA is connected to the IMAP server, inband notifications are generated using the facilities outlined in . When the MUA is not connected, the Notification filter generates a outband notification. The notification filter may be considered as acting on a PUSH repository. If the MUA is not connected, and outband notification is disabled, the client must perform a quick-sync on reconnect to determine mailbox changes, using the mechanisms outlined in .

Lemonade Message Stores MUST support the IDLE extension. The extension allows clients to receive unsolicited notifications about changes in the selected mailbox, without needing to poll for changes. The responses forming these notifications MUST be sent in a timely manner when such changes happen. Lemonade Message Stores also provide the NOTIFY extension described in , which allows clients to request specific event types to be sent immediately to the client, both for the currently selected folder and others. Such event types include message delivery, and mailbox renames.

Lemonade, and TCP, provide for long-lived idle connections between the client and mail store, allowing the server to push notifications within IMAP. Some mobile networks support dormancy, which shuts down the radio traffic channel during idle periods to conserve handset and network resources, while maintaining IP and TCP state. (See the document for more information.) However, there are environments where the email client cannot remain active indefinitely, or where it is not advisable (or even always possible) for TCP connections to the server to remain up while idle for extended periods. In these situations, a good user experience requires that when "interesting" events occur in the mail store, the client be informed so that it can connect and resynchronize. At an absolute minimum, this requires that at least the arrival of new mail generate some sort of wake-up to the email client. A number of vendors have implemented various solutions to this. As examples of what has been done, for many years (long pre-dating cellular handsets) the technique described in has been supported. Today, a number of email vendors include facilities to send SMS or other simple non-stream messages to clients on handsets when new mail arrives. OMA has published a mechanism that uses WAP PUSH to send a basic message containing a URL . The IETF is investigating ways to standardize enhanced functionality in this area. A "push email" user experience can be achieved using any number of techniques, ranging from always-on TCP connectivity to the server and the NOTIFY extension described above, to OMA EMN, or even a non-standard trigger message over SMS. In any technique, the client learns of the existence of new mail, and decides to fetch information about it, some part of it, or all of it, and then presents this to the user.

Lemonade Message Stores MUST support the ESEARCH extension. The extension allows clients to efficiently find the first or last messages, find a count of matching messages, and obtain a list of matching messages in a considerably more compact representation. Lemonade Message Stores also provide a mechanism for clients to avoid handling an entire mailbox, instead accessing a view of the mailbox. This technique, common in many desktop clients as a client-side capability, is useful for constrained clients to minimize the quantity of messages and notification data. Lemonade Message Stores therefore MUST implement the CONTEXT=SEARCH, ESORT and CONTEXT=SORT extensions defined in , as well as the SORT extension defined in .

Lemonade Message Stores MUST support the NAMESPACE extension. The extension allows clients to discover shared mailboxes and mailboxes belonging to other users, and provide a normalized hierarchy view of the mailboxes available. Lemonade Message Stores MUST support the I18NLEVEL=<n> extension, with <n> having value 1 or 2. It adds support for non-English (internationalized) search and sort functions. (Note that I18NLEVEL=2 implies support for I18NLEVEL=1, so a Lemonade compliant client that make use of this extension MUST recognize either one.)

In order to optimize network usage for the typical case where message content is copied to, or sourced from, the IMAP store, Lemonade provides support for a suite of extensions collectively known as Forward Without Download, discussed in detail in . Lemonade Message Stores MUST support CATENATE , UIDPLUS and URLAUTH . Lemonade Message Stores MUST also support URL-PARTIAL .

introduced a new syntactic element for referencing a byte range of a message/body part. This is done using the ;PARTIAL= field. If an IMAP server supports PARTIAL in IMAP URL used in CATENATE and URLAUTH extensions, then it MUST advertise the URL-PARTIAL capability in the CAPABILITY response/response code.

Lemonade Message Stores MUST support the LITERAL+ extension. The extension allows clients to save a round trip each time a non-synchronizing literal is sent. Lemonade Message Stores MUST also implement the SASL-IR extension, which allows clients to save a round trip during authentication, potentially pipelining the entire authentication sequence. Lemonade Compliant IMAP servers MUST support IMAP over TLS as required by . As noted above in , servers SHOULD support the deflate compression algorithm for TLS, as specified in .

The $Forwarded IMAP keyword is used by several IMAP clients to specify that the marked message was forwarded to another email address, embedded within or attached to a new message. A mail client sets this keyword when it successfully forwards the message to another email address. Typical usage of this keyword is to show a different (or additional) icon for a message that has been forwarded. Once set the flag SHOULD NOT be cleared. Lemonade Message Stores MUST be able to store the $Forwarded keyword. They MUST preserve it on the COPY operation. The servers MUST support the SEARCH KEYWORD $Forwarded.

The $SubmitPending IMAP keyword designates the message as awaiting to be submitted. This keyword allows to store messages waiting to be submitted in the same mailbox where messages that were already submitted and/or being edited are stored. A mail client sets this keyword when it decides that the message needs to be sent out. When a client (it might be a different client from the one that decided that the message is pending submission) starts sending the message, it atomically (using "STORE (UNCHANGEDSINCE)") adds the $Submitted keyword. Once submission is successful, the $SubmitPending keyword is atomically cleared. The two keywords allow to distinguish messages being actively submitted (messages that have both $Submitted and $SubmitPending keywords set) from messages awaiting to be submitted, or from messages already submitted. They also allow to find all messages that were supposed to be submitted, if the client submitting them crashes or quits before submitting them. Lemonade Message Stores MUST be able to store the $SubmitPending and the $Submitted keyword. Lemonade Message Stores MUST preserve them on the COPY operation. The servers MUST support the SEARCH KEYWORD $SubmitPending and SEARCH KEYWORD $Submitted.

This section is non-normative. Server implementations targeting to fulfil OMA MEM requirements should consider implementing , which provides a way to persist definition of virtual mailboxes on the server. They should also consider implementing METADATA-SERVER extension, which provides a way of storing user-defined data associated with a user account.

Lemonade Message Delivery Agents MUST support the filtering language at the point of delivery, allowing the user to control which messages are accepted, and where they are filed. Lemonade Message Delivery Agents MUST support the Sieve Vacation extension , which allows the client to setup an auto-responder, typically to report being on vacation (thus the name of the Sieve extension). Lemonade Message Delivery Agents MUST support the Sieve Enotify extension , which allows a Sieve script to generate notifications (such as XMPP, SIP or email) about received messages. Lemonade Message Delivery Agents MUST support the Sieve Variables extension , which adds support for variables to the Sieve scripting language. This extension is typically used with Sieve Enotify or Vacation to customize responses/notifications. Lemonade Message Delivery Agents MUST support the Sieve Relational extension , which adds support for relational comparisons to the Sieve scripting language. This extension is typically used together with Sieve Enotify. Lemonade Message Delivery Agents MUST support the Sieve Imap4Flags extension , which allows a Sieve script to set IMAP flags/keywords when delivering a message to a mailbox. For example this can be used to automatically mark certain messages as interesting, urgent, etc. Lemonade Message Delivery Agents MUST support the i;unicode-casemap comparator in Sieve . The comparator allows for case-insensitive matching of Unicode characters. Lemonade Message Delivery Agents should consider supporting Sieve script management using the protocol. If they do, they MUST also advertise in all Sieve extensions listed in this section.

Although all existing IMAP MUAs are Lemonade compliant in as much as all Lemonade services are based on the existing and protocols, client implementors are encouraged to take full advantage of the facilities provided by Lemonade Submission Servers and Lemonade Message Stores, as described in and respectively. Note that the explicit usage of means that when opening a connection to the submission server, clients MUST do so using port 587 unless explicitly configured to use an alternate port. If the TCP connection to the submission server fails to open using port 587, the client MAY then immediately retry using a different port, such as 25. See information on why using port 25 is likely to fail depending on the current location of the client, and may result in a failure code during the SMTP transaction. In addition, some specifications are useful to support interoperable messaging with an enhanced user experience. Lemonade capable clients SHOULD support the Format and DelSp parameters to the text/plain media type described in , and generate this format for messages. Lemonade capable clients SHOULD support, and use, the $Forwarded keyword described in .

The advent of client/server email using the and protocols changed what formerly were local disk operations to become repetitive network data transmissions. Lemonade "forward without download" makes use of the extension to enable access to external sources during the submission of a message. In combination with the extension, inclusion of message parts or even entire messages from the IMAP mail store is possible with a minimal trust relationship between the IMAP and SMTP SUBMIT servers. Lemonade "forward without download" has the advantage of maintaining one submission protocol, and thus avoids the risk of having multiple parallel and possibly divergent mechanisms for submission. The client can use extensions without these being added to IMAP. Furthermore, by keeping the details of message submission in the SMTP SUBMIT server, Lemonade "forward without download" can work with other message retrieval protocols such as POP, NNTP, or whatever else may be designed in the future.

The act of sending an email message can be thought of as involving multiple steps: initiation of a new draft, draft editing, message assembly, and message submission. Initiation of a new draft and draft editing takes place in the MUA. Frequently, users choose to save more complex messages on an server (via the APPEND command with the \Draft flag) for later recall by the MUA and resumption of the editing process. Message assembly is the process of producing a complete message from the final revision of the draft and external sources. At assembly time, external data is retrieved and inserted in the message. Message submission is the process of inserting the assembled message into the infrastructure, typically using the protocol.

Traditionally, messages are initiated, edited, and assembled entirely within an MUA, although drafts may be saved to an server and later retrieved from the server. The completed text is then transmitted to an MSA for delivery. There is often no clear boundary between the editing and assembly process. If a message is forwarded, its content is often retrieved immediately and inserted into the message text. Similarly, when external content is inserted or attached, the content is usually retrieved immediately and made part of the draft. As a consequence, each save of a draft and subsequent retrieve of the draft transmits that entire (possibly large) content, as does message submission. In the past, this was not much of a problem, because drafts, external data, and the message submission mechanism were typically located on the same system as the MUA. The most common problem was running out of disk quota.

The model distinguishes between a Messaging User Agent (MUA), an IMAPv4Rev1 Server () and a SMTP submit server (), as illustrated in Figure 1. +--------------------+ +--------------+ | | <------------ | | | MUA (M) | | IMAPv4Rev1 | | | | Server | | | ------------> | (Server I) | +--------------------+ +--------------+ ^ | ^ | | | | | | | | | | | | | | | | | | | | | | | | v | | +--------------+ | |----------------------> | SMTP | | | Submit | |-----------------------------| Server | | (Server S) | +--------------+ Figure 1: Lemonade "forward without download" Lemonade "forward without download" allows a Messaging User Agent to compose and forward an e-mail combining fragments that are located in an IMAP server, without having to download these fragments to the client. There are two ways to perform "forward without download" based on where the message assembly takes place. The first uses extended APPEND command to edit a draft message in the message store and cause the message assembly on the IMAP server. This is most often used when a copy of the message is to be retained on the IMAP server, as discussed in . The second uses a succession of BURL and BDAT commands to submit and assemble through concatenation, message data from the client and external data fetched from the provided URL. The two subsequent sections provide step-by-step instructions on how "forward without download" is achieved.

In the / variant of the Lemonade "forward without download" strategy, messages are initially composed and edited within an MUA. The extension to is then used to create the messages on the IMAP server by transmitting new text and assembling them. The UIDPLUS IMAP extension is used by the client in order to learn the UID of the created messages. Finally a format URL is given to a server for submission using the BURL extension. The flow involved to support such a use case consists of: M: {to I -- Optional} The client connects to the IMAP server, optionally starts TLS (if data confidentiality is required), authenticates, opens a mailbox ("INBOX" in the example below) and fetches body structures (See ).

Example: M: A0051 UID FETCH 25627 (UID BODYSTRUCTURE) I: * 161 FETCH (UID 25627 BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 1152 23)( "TEXT" "PLAIN" ("CHARSET" "US-ASCII" "NAME" "trip.txt") "<960723163407.20117h@washington.example.com>" "Your trip details" "BASE64" 4554 73) "MIXED")) I: A0051 OK completed M: {to I} The client invokes CATENATE (See for details of the semantics and steps) -- this allows the MUA to create messages on the IMAP server using new data combined with one or more message parts already present on the IMAP server. Note that the example for this step doesn't use the LITERAL+ extension. Without LITERAL+ the new message is constructed using 3 round-trips. If LITERAL+ is used, the new message can be constructed using one round-trip.

M: A0052 APPEND Sent FLAGS (\Draft \Seen $MDNSent) CATENATE (TEXT {475} I: + Ready for literal data M: Message-ID: <419399E1.6000505@caernarfon.example.org> M: Date: Thu, 12 Nov 2004 16:57:05 +0000 M: From: Bob Ar <bar@example.org> M: MIME-Version: 1.0 M: To: foo@example.net M: Subject: About our holiday trip M: Content-Type: multipart/mixed; M: boundary="------------030308070208000400050907" M: M: --------------030308070208000400050907 M: Content-Type: text/plain; format=flowed M: M: Our travel agent has sent the updated schedule. M: M: Cheers, M: Bob M: --------------030308070208000400050907 M: URL "/INBOX;UIDVALIDITY=385759045/; UID=25627/;Section=2.MIME" URL "/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2" TEXT {44} I: + Ready for literal data M: M: --------------030308070208000400050907-- M: ) I: A0052 OK [APPENDUID 387899045 45] CATENATE Completed M: {to I} The client uses GENURLAUTH command to request a URLAUTH URL (See ). I: {to M} The IMAP server returns a URLAUTH URL suitable for later retrieval with URLFETCH (See for details of the semantics and steps).

M: A0054 GENURLAUTH "imap://bob.ar@example.org/Sent; UIDVALIDITY=387899045/;uid=45;expire=2005-10- 28T23:59:59Z;urlauth=submit+bob.ar" INTERNAL I: * GENURLAUTH "imap://bob.ar@example.org/Sent; UIDVALIDITY=387899045/;uid=45;expire= 2005-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:91354a473744909de610943775f92038" I: A0054 OK GENURLAUTH completed M: {to S} The client connects to the mail submission server and starts a new mail transaction. It uses BURL to let the SMTP submit server fetch the content of the message from the IMAP server (See for details of the semantics and steps -- this allows the MUA to authorize the SMTP submit server to access the message composed as a result of the CATENATE step). Note that the second EHLO command is required after a successful STARTTLS command. Also note that there might be a third required EHLO command if the second EHLO response doesn't list any BURL options. demonstrates this.

S: 220 owlry.example.org ESMTP M: EHLO potter.example.org S: 250-owlry.example.com S: 250-8BITMIME S: 250-BINARYMIME S: 250-PIPELINING S: 250-BURL imap S: 250-CHUNKING S: 250-AUTH PLAIN S: 250-DSN S: 250-SIZE 10240000 S: 250-STARTTLS S: 250 ENHANCEDSTATUSCODES M: STARTTLS S: 220 Ready to start TLS ...TLS negotiation, subsequent data is encrypted... M: EHLO potter.example.org S: 250-owlry.example.com S: 250-8BITMIME S: 250-BINARYMIME S: 250-PIPELINING S: 250-BURL imap S: 250-CHUNKING S: 250-AUTH PLAIN S: 250-DSN S: 250-SIZE 10240000 S: 250 ENHANCEDSTATUSCODES M: AUTH PLAIN aGFycnkAaGFycnkAYWNjaW8= S: 235 2.7.0 PLAIN authentication successful. M: MAIL FROM:<bob.ar@example.org> S: 250 2.5.0 Address Ok. M: RCPT TO:<foo@example.net> S: 250 2.1.5 foo@example.net OK. M: BURL imap://bob.ar@example.org/Sent;UIDVALIDITY=387899045/; uid=45/;urlauth=submit+bar:internal: 91354a473744909de610943775f92038 LAST S: {to I} The mail submission server uses URLFETCH to fetch the message to be sent (See for details of the semantics and steps. The so-called "pawn-ticket" authorization mechanism uses a URI which contains its own authorization credentials.). I: {to S} Provides the message composed as a result of the CATENATE step).

Mail submission server opens IMAP connection to the IMAP server: I: * OK [CAPABILITY IMAP4REV1 STARTTLS NAMESPACE LITERAL+ CATENATE URLAUTH UIDPLUS CONDSTORE IDLE] imap.example.com IMAP server ready S: a000 STARTTLS I: a000 Start TLS negotiation now ...TLS negotiation, if successful - subsequent data is encrypted... S: a001 LOGIN submitserver secret I: a001 OK submitserver logged in S: a002 URLFETCH "imap://bob.ar@example.org/Sent; UIDVALIDITY=387899045/;uid=45/;urlauth=submit+bob.ar: internal:91354a473744909de610943775f92038" I: * URLFETCH "imap://bob.ar@example.org/Sent; UIDVALIDITY=387899045/;uid=45/;urlauth=submit+bob.ar: internal:91354a473744909de610943775f92038" {15065} ...message body follows... S: a002 OK URLFETCH completed I: a003 LOGOUT S: * BYE See you later S: a003 OK Logout successful Note that if the IMAP server doesn't send CAPABILITY response code in the greeting, the mail submission server must issue the CAPABILITY command to learn about supported IMAP extensions as described in . Also, if data confidentiality is not required the mail submission server may omit the STARTTLS command before issuing the LOGIN command.

S: {to M} Submission server assembles the complete message and if the assembly succeeds it returns OK to the MUA: S: 250 2.5.0 Ok.

M: {to I} The client marks the message containing the forwarded attachment on the IMAP server. M: A0053 UID STORE 25627 +FLAGS.SILENT ($Forwarded) I: * 215 FETCH (UID 25627 MODSEQ (12121231000)) I: A0053 OK STORE completed Note: the UID STORE command shown above will only work if the marked message is in the currently selected mailbox; otherwise, it requires a SELECT. This command can be omitted, as it simply changes non-operational metadata not essential to client operations or interoperability. The untagged FETCH response is due to . The $Forwarded IMAP keyword is described in .

In the / variant of the Lemonade "forward without download" strategy, messages are initially composed and edited within an MUA. During submission , BURL and BDAT commands are used to create the messages from multiple parts. New body parts are supplied using BDAT commands, while existing body parts are referenced using format URLs in BURL commands. The flow involved to support such a use case consists of: M: {to I -- Optional} The client connects to the IMAP server, optionally starts TLS (if data confidentiality is required), authenticates, opens a mailbox ("INBOX" in the example below) and fetches body structures (See ).

Example: M: A0051 UID FETCH 25627 (UID BODYSTRUCTURE) I: * 161 FETCH (UID 25627 BODYSTRUCTURE (("TEXT" "PLAIN" ("CHARSET" "US-ASCII") NIL NIL "7BIT" 1152 23)( "TEXT" "PLAIN" ("CHARSET" "US-ASCII" "NAME" "trip.txt") "<960723163407.20117h@washington.example.com>" "Your trip details" "BASE64" 4554 73) "MIXED")) I: A0051 OK completed M: {to I} The client uses GENURLAUTH command to request URLAUTH URLs (See ) referencing pieces of the message to be assembled. I: {to M} The IMAP server returns URLAUTH URLs suitable for later retrieval with URLFETCH (See for details of the semantics and steps).

M: A0054 GENURLAUTH "imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2.MIME; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar" INTERNAL "imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar" INTERNAL I: * GENURLAUTH "imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2.MIME; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:A0DEAD473744909de610943775f9BEEF" "imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:BEEFA0DEAD473744909de610943775f9" I: A0054 OK GENURLAUTH completed M: {to S} The client connects to the mail submission server and starts a new mail transaction. It uses BURL to instruct the SMTP submit server to fetch from the IMAP server pieces of the message to be sent (See for details of the semantics and steps). Note that the second EHLO command is required after a successful STARTTLS command. The third EHLO command is required if and only if the second EHLO response doesn't list any BURL options. See for an example of submission where the third EHLO command/response is not present.

S: 220 owlry.example.org ESMTP M: EHLO potter.example.org S: 250-owlry.example.com S: 250-8BITMIME S: 250-BINARYMIME S: 250-PIPELINING S: 250-BURL S: 250-CHUNKING S: 250-AUTH DIGEST-MD5 S: 250-DSN S: 250-SIZE 10240000 S: 250-STARTTLS S: 250 ENHANCEDSTATUSCODES M: STARTTLS S: 220 Ready to start TLS ...TLS negotiation, subsequent data is encrypted... M: EHLO potter.example.org S: 250-owlry.example.com S: 250-8BITMIME S: 250-BINARYMIME S: 250-PIPELINING S: 250-BURL S: 250-CHUNKING S: 250-AUTH DIGEST-MD5 CRAM-MD5 PLAIN EXTERNAL S: 250-DSN S: 250-SIZE 10240000 S: 250 ENHANCEDSTATUSCODES M: AUTH PLAIN aGFycnkAaGFycnkAYWNjaW8= S: 235 2.7.0 PLAIN authentication successful. M: EHLO potter.example.org S: 250-owlry.example.com S: 250-8BITMIME S: 250-BINARYMIME S: 250-PIPELINING S: 250-BURL imap imap://imap.example.org S: 250-CHUNKING S: 250-AUTH DIGEST-MD5 CRAM-MD5 PLAIN EXTERNAL S: 250-DSN S: 250-SIZE 10240000 S: 250 ENHANCEDSTATUSCODES M: MAIL FROM:<bob.ar@example.org> BODY=BINARY S: 250 2.5.0 Address Ok. M: RCPT TO:<foo@example.net> S: 250 2.1.5 foo@example.net OK. M: BDAT 475 M: Message-ID: <419399E1.6000505@caernarfon.example.org> M: Date: Thu, 12 Nov 2004 16:57:05 +0000 M: From: Bob Ar <bar@example.org> M: MIME-Version: 1.0 M: To: foo@example.net M: Subject: About our holiday trip M: Content-Type: multipart/mixed; M: boundary="------------030308070208000400050907" M: M: --------------030308070208000400050907 M: Content-Type: text/plain; format=flowed M: M: Our travel agent has sent the updated schedule. M: M: Cheers, M: Bob M: --------------030308070208000400050907 S: 250 2.5.0 OK M: BURL imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2.MIME; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:A0DEAD473744909de610943775f9BEEF S: 250 2.5.0 OK M: BURL imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:BEEFA0DEAD473744909de610943775f9 S: 250 2.5.0 OK M: BDAT 44 LAST M: M: --------------030308070208000400050907-- S: {to I} The mail submission server uses URLFETCH to fetch the pieces of the message to be sent (See for details of the semantics and steps. The so-called "pawn-ticket" authorization mechanism uses a URI which contains its own authorization credentials.). I: {to S} Returns the requested body parts.

Mail submission server opens IMAP connection to the IMAP server: I: * OK [CAPABILITY IMAP4REV1 STARTTLS NAMESPACE LITERAL+ CATENATE URLAUTH UIDPLUS CONDSTORE IDLE] imap.example.com IMAP server ready S: a001 LOGIN submitserver secret I: a001 OK submitserver logged in S: a002 URLFETCH "imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2.MIME; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:A0DEAD473744909de610943775f9BEEF" "imap:// bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:BEEFA0DEAD473744909de610943775f9" I: * URLFETCH "imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2.MIME; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:A0DEAD473744909de610943775f9BEEF" {84} ...message section follows... "imap://bob.ar@example.org/INBOX; UIDVALIDITY=385759045/;UID=25627/;Section=2; expire=2006-10-28T23:59:59Z;urlauth=submit+bob.ar: internal:BEEFA0DEAD473744909de610943775f9" {15065} ...message section follows... S: a002 OK URLFETCH completed I: a003 LOGOUT S: * BYE See you later S: a003 OK Logout successful Note that if the IMAP server doesn't send CAPABILITY response code in the greeting, the mail submission server must issue the CAPABILITY command to learn about supported IMAP extensions as described in . Also, if data confidentiality is required the mail submission server should start TLS before issuing the LOGIN command.

S: {to M} Submission server assembles the complete message and if the assembly succeeds it acknowledges acceptance of the message by sending 250 response to the last BDAT command: S: 250 2.5.0 Ok, message accepted.

M: {to I} The client marks the message containing the forwarded attachment on the IMAP server. M: A0053 UID STORE 25627 +FLAGS.SILENT ($Forwarded) I: * 215 FETCH (UID 25627 MODSEQ (12121231000)) I: A0053 OK STORE completed Note: the UID STORE command shown above will only work if the marked message is in the currently selected mailbox; otherwise, it requires a SELECT. As in the previous example, this command is not critical, and can be omitted. The untagged FETCH response is due to . The $Forwarded IMAP keyword is described in .

The so-called "pawn-ticket" authorization mechanism uses a URI, which contains its own authorization credentials using . The advantage of this mechanism is that the SMTP submit server cannot access any data on the server without a "pawn- ticket" created by the client. The "pawn-ticket" grants access only to the specific data that the SMTP submit server is authorized to access, can be revoked by the client, and can have a time-limited validity.

The "fcc problem" refers to delivering a copy of a message to a mailbox, or "file carbon copy". By far, the most common case of fcc is a client leaving a copy of outgoing mail in a "Sent Mail" or "Outbox" mailbox. In the traditional strategy, the MUA duplicates the effort spent in transmitting to the MSA by writing the message to the fcc destination in a separate step. This may be a write to a local disk file or an APPEND to a mailbox on an IMAP server. The latter is one of the "repetitive network data transmissions" which represents the "problem" aspect of the "fcc problem". The BURL extension can be used to eliminate the additional transmission. The final message is uploaded to the mailbox designed for outgoing mail, by the APPEND command of . Note that APPEND, including when enhanced by , can only create a single copy of the message and this is only of use on the server which stages the outgoing message for submission. Additional copies of the message on the same server can be created by using one or more COPY commands.

Deployment considerations are discussed extensively in .

Implementors are advised to examine the Security Considerations of all the referenced documents. This section merely highlights these, and advises implementors on specific issues relating to the combination of extensions. Security considerations on Lemonade "forward without download" are discussed throughout . Additional security considerations can be found in and other documents describing other SMTP and IMAP extensions comprising the Lemonade Profile. Note that the mandatory-to-implement authentication mechanism for SMTP submission is described in . The mandatory-to-implement authentication mechanism for IMAP is described in .

When clients submit new messages, link protection such as TLS guards against an eavesdropper seeing the contents of the submitted message. It is worth noting, however, that even if TLS is not used, the security risks are no worse if BURL is used to reference the text than if the text is submitted directly. If BURL is not used, an eavesdropper gains access to the full text of the message. If BURL is used, the eavesdropper may or may not be able to gain such access, depending on the form of BURL used. For example, some forms restrict use of the URL to an entity authorized as a submission server or a specific user.

When Lemonade clients use the BURL extension to mail submission, an extension that requires sending a URLAUTH token to the mail submission server, such a token should be protected from interception to avoid a replay attack that may disclose the contents of the message to an attacker. TLS based encryption of the mail submission path will provide protection against this attack. Lemonade clients SHOULD use TLS-protected IMAP and mail submission channels when using BURL-based message submission to protect the URLAUTH token from interception. Lemonade compliant mail submission servers SHOULD use TLS-protected IMAP connections when fetching message content using the URLAUTH token provided by the Lemonade client. When a client uses SMTP STARTTLS to send a BURL command which references non-public information, there is a user expectation that the entire message content will be treated confidentially. To meet this expectation, the message submission server should use STARTTLS or a mechanism providing equivalent data confidentiality when fetching the content referenced by that URL.

This specification provides no additional security measures beyond those in the referenced Internet Mail and Lemonade documents. We note however the security risks associated to: Outband notifications Server configuration by client Client configuration by server Presence of proxy servers Presence of servers as intermediaries In general the deployment models considered by OMA MEM that are not conventional IETF deployment models. Measures to address a perceived need to traverse firewalls and mobile network intermediaries.

IMAP4 capabilities are registered by publishing a standards track or IESG approved experimental RFC. The registry is currently located at <http://www.iana.org/assignments/imap4-capabilities>. This document defines the URL-PARTIAL IMAP capability . IANA is requested to add this extension to the IANA IMAP Capability registry.

This section will be converted to the "Changes Since RFC 4550" section before publication. Version 11: Made ManageSieve reference Informative. Renamed $PendingSubmission to $SubmitPending, dropped $BeingSubmitted and added $Submitted IMAP keywords. Version 10: Added ManageSieve. Added a requirement to support i;unicode-casemap in Sieve (already required in IMAP). Added description of various Sieve extensions. Added definition of URL-PARTIAL IMAP extension. Added definition of $PendingSubmission and $BeingSubmitted IMAP keywords. Version 9: Updated references and removed extensions that there was an agreement to remove. Version 08: Removed LIST-EXTENDED, WITHIN and QUICKSTART. Updated names of required extensions when they were renamed (e.g. COMPARATOR ==> I18NLEVEL=1). Version 06: Updated references and added extensions agreed at the Lemonade interim in Spring 2007. Require any Lemonade compliant IMAP server to support CAPABILITY response code. Version 04: Major reorganization of text. Move checklist summary to beginning of document, collate Submission and Store server requirements. Version 03: Replaced RECONNECT (server side quick reconned) with QRESYNC (client side quick reconnect) Added WITHIN and LIST-EXTENDED. Moved IDLE extension to a separate section. Added requirement for clients to use Format=flowed. Version 02: Update of references and how they are displayed in the text (Comments from Randy Gellens) Update of list of extensions to support as MUST by the Lemonade Profile Bis Update of options for compression via placeholder imap-compression section describing compression requirements Update of support of TCP chalenged environments Update of support of object level encryption Clarified the use of $Forwarded in the examples, and demonstrated how to remove the \Draft flag from the sent message Clarified $Forwarded Added RECONNECT to imap-condstore section Add new section imap-bodypart, "Message part handling", describing BINARY and CONVERT requirements Added placeholder section for notifications Added various extensions to imap-other section, and added clarifying comments to IDLE, NAMESPACE, and a further references to TLS DEFLATE compression Added extension names to IMAP table Fixed all issues found with original Lemonade profile so far. Version 01: Lemonade profile has been introduced in-line, with some updates / corrections. Subsequent re-organization of the text Details of extensions proper to Lemonade Profile-bis have been updated to refer to the drafts newly accepted as WG IETF drafts. Addition of appendix on attachements streaming. Version 00: It evolved from a combination of the content of Lemonade profile and the OMA MEM realization internet draft.

The editors acknowledge and appreciate the work and comments of the IETF Lemonade working group and the OMA MEM working group. In particular, the editors would like to thank Eric Burger, Randall Gellens, Filip Navara, Zoltan Ordogh, Greg Vaudreuil, and Fan Xiaohui for their comments and reviews.