draft-ietf-lemonade-imap-notify-04.txt   draft-ietf-lemonade-imap-notify-05.txt 
Network Working Group Curtis King Network Working Group Alexey Melnikov
Internet-Draft Alexey Melnikov Internet-Draft Isode Ltd.
Intended Status: Proposed Standard Isode Ltd. Intended Status: Proposed Standard Arnt Gulbrandsen
Arnt Gulbrandsen
Oryx Mail Systems GmbH Oryx Mail Systems GmbH
February 25, 2008 Curtis King
Isode Ltd.
March 24, 2008
The IMAP NOTIFY Extension The IMAP NOTIFY Extension
draft-ietf-lemonade-imap-notify-04.txt draft-ietf-lemonade-imap-notify-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six
and may be updated, replaced, or obsoleted by other documents at any months and may be updated, replaced, or obsoleted by other documents
time. It is inappropriate to use Internet-Drafts as reference at any time. It is inappropriate to use Internet-Drafts as
material or to cite them other than as "work in progress." reference material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet- http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-
Draft Shadow Directories can be accessed at Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft expires in July 2008. This Internet-Draft expires in September 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2008). Copyright (C) The IETF Trust (2008).
Abstract Abstract
This document defines an IMAP extension which allows a client to This document defines an IMAP extension which allows a client to
request specific kinds of unsolicited notifications for specified request specific kinds of unsolicited notifications for specified
mailboxes, such as messages being added to or deleted from mailboxes. mailboxes, such as messages being added to or deleted from
mailboxes.
Internet-draft February 2008
[[Add Updates: RFC-CONTEXT to the headers]] [[Add Updates: RFC-CONTEXT to the headers]]
1. Conventions Used in This Document 1. Conventions Used in This Document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Formal syntax is defined by [RFC5234] as extended by [RFC3501] and Formal syntax is defined by [RFC5234] as extended by [RFC3501] and
[RFC4466]. [RFC4466].
The acronym MSN stands for Message Sequence Numbers (see Section The acronym MSN stands for Message Sequence Numbers (see Section
2.3.1.2 of [RFC3501]). 2.3.1.2 of [RFC3501]).
Example lines prefaced by "C:" are sent by the client and ones Example lines prefaced by "C:" are sent by the client and ones
prefaced by "S:" by the server. "[...]" means elision. prefaced by "S:" by the server. "[...]" means elision.
2. Overview and rationale 2. Overview and rationale
The IDLE command (defined in [RFC2177]) provides a way for the client The IDLE command (defined in [RFC2177]) provides a way for the
to go into a mode where the IMAP server pushes notifications about client to go into a mode where the IMAP server pushes notifications
IMAP mailstore events for the selected mailbox. However, the IDLE about IMAP mailstore events for the selected mailbox. However, the
extension doesn't restrict or control which server events can be IDLE extension doesn't restrict or control which server events can
sent, or what information the server sends in response to each event. be sent, or what information the server sends in response to each
Also, IDLE only applies to the selected mailbox, thus requiring an event. Also, IDLE only applies to the selected mailbox, thus
additional TCP connection per mailbox. requiring an additional TCP connection per mailbox.
This document defines an IMAP extension that allows clients to This document defines an IMAP extension that allows clients to
express their preferences about unsolicited events generated by the express their preferences about unsolicited events generated by the
server. The extension allows clients to only receive events they are server. The extension allows clients to only receive events they
interested in, while servers know that they don't need to go into are interested in, while servers know that they don't need to go
effort of generating certain types of untagged responses. into effort of generating certain types of untagged responses.
Without the NOTIFY command defined in this document, and IMAP server Without the NOTIFY command defined in this document, an IMAP server
will only send information about mailstore changes to the client in will only send information about mailstore changes to the client in
the following cases: the following cases:
- as the result of a client command (e.g. FETCH responses to - as the result of a client command (e.g. FETCH responses to
a FETCH or STORE command), a FETCH or STORE command),
- unsolicited responses sent just before the end of a command - unsolicited responses sent just before the end of a command
(e.g. EXISTS or EXPUNGE) as the result of changes in other (e.g. EXISTS or EXPUNGE) as the result of changes in other
sessions, and sessions, and
- during an IDLE command. - during an IDLE command.
The NOTIFY command extends what information may be returned in those The NOTIFY command extends what information may be returned in those
last two cases, and also permits and requires the server to send last two cases, and also permits and requires the server to send
information about updates between command. The NOTIFY command also information about updates between command. The NOTIFY command also
Internet-draft February 2008
allows for the client to extend what information is sent unsolicited allows for the client to extend what information is sent unsolicited
about the selected mailbox, and to request some update information to about the selected mailbox, and to request some update information
be sent regarding other mailboxes. to be sent regarding other mailboxes.
For the new messages delivered to or appended to the selected For the new messages delivered to or appended to the selected
mailbox, the NOTIFY command can be used to request that a set of mailbox, the NOTIFY command can be used to request that a set of
attributes be sent to the client in an unsolicited FETCH response. attributes be sent to the client in an unsolicited FETCH response.
This allows a client to be passive recipient of events and new mail, This allows a client to be passive recipient of events and new mail,
and be able to maintain full synchronisation without having to issue and be able to maintain full synchronisation without having to issue
any subsequent commands except to modify the state of the mailbox on any subsequent commands except to modify the state of the mailbox on
the server. the server.
Some mobile clients, however, may want mail "pushed" only for mail Some mobile clients, however, may want mail "pushed" only for mail
that matches a SEARCH pattern. To meet that need [CONTEXT] is that matches a SEARCH pattern. To meet that need [CONTEXT] is
augmented by this document to extend the UPDATE return option to augmented by this document to extend the UPDATE return option to
specify a list of fetch-atts to be returned when a new message is specify a list of fetch-atts to be returned when a new message is
delivered or appended in another session. delivered or appended in another session.
[[Should the following be a normative subsection?]] IMAP servers [[RFC-Editor: Please delete the following before publication:
which support this extension advertise the X-DRAFT-W04-NOTIFY Comments regarding this draft may be sent either to the
extension. lemonade@ietf.org mailing list or to the authors.]]
3. The NOTIFY extension
IMAP servers which support this extension advertise the X-DRAFT-
W05-NOTIFY capability. This extension adds the NOTIFY command as
defined in Section 5.1.
A server implementing this extension is not required to implement A server implementing this extension is not required to implement
LIST-EXTENDED [LISTEXT], even though a NOTIFY compliant server must LIST-EXTENDED [LISTEXT], even though a NOTIFY compliant server must
be able to return extended LIST responses defined in [LISTEXT]. be able to return extended LIST responses defined in [LISTEXT].
[[RFC-Editor: Please delete the following before publication: [[RFC-Editor: Should QRESYNC be a required dependency for this
Comments regarding this draft may be sent either to the extension?]]
lemonade@ietf.org mailing list or to the authors.]]
3. The NOTIFY Command 3.1. The NOTIFY Command
Arguments: "SET" Arguments: "SET"
optional STATUS indicator optional STATUS indicator
Mailboxes to be watched Mailboxes to be watched
Events about which to notify the client Events about which to notify the client
Or Or
Arguments: "NONE" Arguments: "NONE"
Responses: Possibly untagged STATUS responses (for SET) Responses: Possibly untagged STATUS responses (for SET)
Result: OK - The server will notify the client as requested. Result: OK - The server will notify the client as requested.
NO - Unsupported notify event, NOTIFY too complex or NO - Unsupported notify event, NOTIFY too complex or
expensive, etc. expensive, etc.
BAD - Command unknown, invalid, unsupported or unknown BAD - Command unknown, invalid, unsupported or unknown
Internet-draft February 2008
arguments. arguments.
The NOTIFY command informs the server that the client listens for The NOTIFY command informs the server that the client listens for
event notifications all the time (even when no command is in event notifications all the time (even when no command is in
progress) and requests the server to notify it about the specified progress) and requests the server to notify it about the specified
set of events. The NOTIFY command has two forms. NOTIFY NONE set of events. The NOTIFY command has two forms. NOTIFY NONE
specifies that the client is not interested in any kind of event specifies that the client is not interested in any kind of event
happening on the server. NOTIFY SET replaces the current list of happening on the server. NOTIFY SET replaces the current list of
interesting events with a new list of events. interesting events with a new list of events.
Until the NOTIFY command is used for the first time, the server only Until the NOTIFY command is used for the first time, the server only
sends notifications while a command is being processed, and notifies sends notifications while a command is being processed, and notifies
the client about these events on the selected mailbox: (see section 5 the client about these events on the selected mailbox: (see section
for definitions): MessageNew, MessageExpunge, FlagChange. It does not 5 for definitions): MessageNew, MessageExpunge, FlagChange. It does
notify the client about any events on other mailboxes. not notify the client about any events on other mailboxes.
The effect of a successful NOTIFY command lasts until the next NOTIFY The effect of a successful NOTIFY command lasts until the next
command, or until the IMAP connection is closed. NOTIFY command, or until the IMAP connection is closed.
A successful NOTIFY SET command MUST cause the server to immediately A successful NOTIFY SET command MUST cause the server to immediately
return any accumulated changes to the mailbox (if any), such as flag return any accumulated changes to the currently selected mailbox (if
changes, new or expunged messages. This is equivalent to NOOP command any), such as flag changes, new or expunged messages. This is
being issued by the client just before the NOTIFY SET command. equivalent to NOOP command being issued by the client just before
the NOTIFY SET command.
The NOTIFY SET command can request notifications of changes to the
selected mailbox, whatever it may be at the time the notifications
are being generated. This is done by specifying the SELECTED mailbox
selector (see Section 6.1) in the NOTIFY SET command. The client
can also request notifications on other mailboxes by name or by a
limited mailbox pattern match. The notifications returned for the
currently selected mailbox will be those specified by the SELECTED
mailbox specifier, even if the selected mailbox also appears by name
in the command.
If the NOTIFY command enables MessageNew, MessageExpunge, If the NOTIFY command enables MessageNew, MessageExpunge,
AnnotationChange or FlagChange notification for a mailbox, and the AnnotationChange or FlagChange notification for a mailbox other than
client has specified the STATUS indicator parameter, then the server SELECTED, and the client has specified the STATUS indicator
MUST send a STATUS response for that mailbox before NOTIFY's tagged parameter, then the server MUST send a STATUS response for that
OK. If MessageNew is enabled, the STATUS response MUST contain mailbox before NOTIFY's tagged OK. If MessageNew is enabled, the
MESSAGES, UIDNEXT and UIDVALIDITY. If MessageExpunge is enabled, the STATUS response MUST contain MESSAGES, UIDNEXT and UIDVALIDITY. If
STATUS response MUST contain MESSAGES. If either AnnotationChange or MessageExpunge is enabled, the STATUS response MUST contain
FlagChange are included, the STATUS response MUST contain UIDVALIDITY MESSAGES. If either AnnotationChange or FlagChange are included and
the server also supports CONDSTORE [RFC4551] and/or QRESYNC
[QRESYNC] extension, the STATUS response MUST contain UIDVALIDITY
and HIGHESTMODSEQ. Absence of the STATUS indicator parameter allows and HIGHESTMODSEQ. Absence of the STATUS indicator parameter allows
the client to avoid the additional STATUS responses. This might be the client to avoid the additional STATUS responses. This might be
useful if the client has already retrieved this information before useful if the client has already retrieved this information before
issuing the NOTIFY command. issuing the NOTIFY command.
Clients are advised to limit the number of mailboxes used with Clients are advised to limit the number of mailboxes used with
NOTIFY. Particularly, if a client asks for events for all accessible NOTIFY. Particularly, if a client asks for events for all accessible
mailboxes, the server may swamp the client with updates about shared mailboxes, the server may swamp the client with updates about shared
mailboxes. This wastes both server and network resources. For mailboxes. This wastes both server and network resources. For
each mailbox specified, the server verifies that the client has each mailbox specified, the server verifies that the client has
access using the following test: access using the following test:
- If the name does not refer to an existing mailbox, the server MUST - If the name does not refer to an existing mailbox, the server MUST
ignore it. ignore it.
- If the name refers to a mailbox which the client can't LIST, the - If the name refers to a mailbox which the client can't LIST, the
Internet-draft February 2008
server MUST ignore it. For a server that implements [RFC4314] this server MUST ignore it. For a server that implements [RFC4314] this
means that if the client that doesn't have the 'l' (lookup) right means that if the client that doesn't have the 'l' (lookup) right
for the name, then the server MUST ignore the mailbox. This for the name, then the server MUST ignore the mailbox. This
behavior prevents dislosure on potentially confidential information behavior prevents dislosure on potentially confidential
to clients which don't have rights to know it. information to clients which don't have rights to know it.
- If the name refers to a mailbox which the client can LIST (e.g. it - If the name refers to a mailbox which the client can LIST (e.g. it
has the 'l' right from [RFC4314]), but misses another right has the 'l' right from [RFC4314]), but doesn't have another right
required for processing of the specified event(s), then the server required for processing of the specified event(s), then the server
MUST respond with an untagged extended LIST response containing the MUST respond with an untagged extended LIST response containing
\NoAccess name attribute. [[Alexey: Note, the newly defined the \NoAccess name attribute.
\NoAccess doesn't mean that the client doesn't have any rights
other than 'l'. The \NoAccess is only meaningful in the context of
the specified NOTIFY command.]]
The server SHOULD return the tagged OK response if the client has The server SHOULD return the tagged OK response if the client has
access to at least one of the mailboxes specified in the current list access to at least one of the mailboxes specified in the current
of interesting events. The server MAY return the tagged NO response list of interesting events. The server MAY return the tagged NO
if the client has no access to any of the specified mailboxes and no response if the client has no access to any of the specified
access can ever be granted in the future (e.g. the client specified mailboxes and no access can ever be granted in the future (e.g. the
an event for 'Subtree Bar/Foo', 'Bar/Foo' doesn't exist and LIST client specified an event for 'Subtree Bar/Foo', 'Bar/Foo' doesn't
returns \Noinferiors for the parent 'Bar'). exist and LIST returns \Noinferiors for the parent 'Bar').
If the notification would be prohibitively expensive for the server If the notification would be prohibitively expensive for the server
(e.g. "notify me of all flag changes in all mailboxes"), the server (e.g. "notify me of all flag changes in all mailboxes"), the server
MAY refuse the command with a tagged NO [NOTIFICATIONOVERFLOW] MAY refuse the command with a tagged NO [NOTIFICATIONOVERFLOW]
response. response.
If the client requests information for events of an unsupported type, If the client requests information for events of an unsupported
the server MUST refuse the command with a tagged NO response (not a type, the server MUST refuse the command with a tagged NO response
BAD). This response SHOULD contain the BADEVENT response code, which (not a BAD). This response SHOULD contain the BADEVENT response
MUST list names of all events supported by the server. code, which MUST list names of all events supported by the server.
Here's an example: Here's an example:
S: * OK [CAPABILITY IMAP4REV1 NOTIFY] S: * OK [CAPABILITY IMAP4REV1 NOTIFY]
C: a login bob alice C: a login bob alice
S: a OK Password matched S: a OK Password matched
C: b notify set status (selected MessageNew (uid C: b notify set status (selected MessageNew (uid
body.peek[header.fields (from to subject)]) MessageExpunge) body.peek[header.fields (from to subject)]) MessageExpunge)
(subtree Lists MessageNew) (subtree Lists MessageNew)
S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 9999 MESSAGES S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 9999 MESSAGES
500) 500)
S: [...] S: [...]
S: * STATUS Lists/Im2000 (UIDVALIDITY 901 UIDNEXT 1 MESSAGES 0) S: * STATUS Lists/Im2000 (UIDVALIDITY 901 UIDNEXT 1 MESSAGES 0)
S: b OK done S: b OK done
C: c select inbox C: c select inbox
S: [...] (the usual 7-8 responses to SELECT) S: [...] (the usual 7-8 responses to SELECT)
Internet-draft February 2008
S: c OK INBOX selected S: c OK INBOX selected
(Time passes. A new message is delivered to mailbox (Time passes. A new message is delivered to mailbox
Lists/Lemonade.) Lists/Lemonade.)
S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 10000 MESSAGES S: * STATUS Lists/Lemonade (UIDVALIDITY 4 UIDNEXT 10000
501) MESSAGES 501)
(Time passes. A new message is delivered to inbox.) (Time passes. A new message is delivered to inbox.)
S: * 127 FETCH (UID 127001 BODY[HEADER.FIELDS (From To Subject)] S: * 127 FETCH (UID 127001 BODY[HEADER.FIELDS (From To
{75} Subject)] {75}
S: Subject: Re: good morning S: Subject: Re: good morning
S: From: alice@example.org S: From: alice@example.org
S: To: bob@example.org S: To: bob@example.org
S: S:
S: ) S: )
(Time passes. The client decides it wants to know about (Time passes. The client decides it wants to know about
one more mailbox.) one more mailbox. As the client already knows
C: d notify set status (selected MessageNew (uid necessary STATUS information for all mailboxes below
the Lists mailbox and because "notify set status" would
cause STATUS responses for *all* mailboxes specified in
the NOTIFY command, including the ones for which the
client already knows STATUS information, the client
issues explicit STATUS request for the mailbox to be
added to the watch list, followed by the NOTIFY SET
without the STATUS parameter.)
C: d STATUS misc (UIDVALIDITY UIDNEXT MESSAGES)
S: * STATUS misc (UIDVALIDITY 1 UIDNEXT 999)
S: d STATUS completed
C: e notify set (selected MessageNew (uid
body.peek[header.fields (from to subject)]) MessageExpunge) body.peek[header.fields (from to subject)]) MessageExpunge)
(subtree Lists MessageNew) (mailboxes misc MessageNew) (subtree Lists MessageNew) (mailboxes misc MessageNew)
S: * STATUS misc (UIDVALIDITY 1 UIDNEXT 999) S: e OK done
(This command enables notification on one mailbox and
otherwise changes nothing, so one STATUS response is
sent.[[AM: This is no longer correct.]])
S: d OK done
4. Interaction with the IDLE Command 4. Interaction with the IDLE Command
If IDLE (as well as this extension) is supported, while processing If IDLE (as well as this extension) is supported, while processing
IDLE the server MUST send the same events as instructed by the client IDLE the server MUST send the same events as instructed by the
using the NOTIFY command. client using the NOTIFY command.
NOTIFY makes IDLE unnecessary for some clients. If a client does not NOTIFY makes IDLE unnecessary for some clients. If a client does not
use MSNs and '*' in commands, it can request MessageExpunge and use MSNs and '*' in commands, it can request MessageExpunge and
MessageNew for the selected mailbox using the NOTIFY command instead MessageNew for the selected mailbox using the NOTIFY command instead
of entering IDLE mode. of entering the IDLE mode.
5. Event Types 5. Event Types
Only some of the events in [MSGEVENT] can be expressed in IMAP, and Only some of the events in [MSGEVENT] can be expressed in IMAP, and
for some of them there are several possible ways to express the for some of them there are several possible ways to express the
event. event.
This section specifies the events which an IMAP server can notify an This section specifies the events which an IMAP server can notify an
IMAP client, and how. IMAP client, and how.
The server SHOULD omit notifying the client if the event is caused by The server SHOULD omit notifying the client if the event is caused
this client. For example, if the client issues CREATE and has by this client. For example, if the client issues CREATE and has
Internet-draft February 2008
requested MailboxName event that would cover the newly created requested MailboxName event that would cover the newly created
mailbox, the server SHOULD NOT notify the client of the MailboxName mailbox, the server SHOULD NOT notify the client of the MailboxName
change. change.
All event types described in this document require the 'l' and 'r' All event types described in this document require the 'l' and 'r'
rights (see [RFC4314]) on all observed mailboxes. Servers that don't rights (see [RFC4314]) on all observed mailboxes. Servers that
implement [RFC4314] should map the above rights to their access don't implement [RFC4314] should map the above rights to their
control model. access control model.
Note that MessageNew and MessageExpunge must be specified together. If FlagChange event is specified, MessageNew and MessageExpunge MUST
It is not possible to specify one, but not the other. also be specified by the client. Otherwise the server MUST respond
with the tagged BAD response.
If one of MessageNew or MessageExpunge is specified, the both events
MUST be specified. Otherwise the server MUST respond with the
tagged BAD response.
If the client instructs the server not to send MessageNew and If the client instructs the server not to send MessageNew and
MessageExpunge for the selected mailbox, the server MUST still send MessageExpunge for the selected mailbox, the server MUST still send
EXISTS and EXPUNGE responses as required by IMAP (see [RFC3501] EXISTS and EXPUNGE responses as required by IMAP (see [RFC3501]
section 7). In other words, MessageExpunge instructs the server to section 7). In other words, MessageExpunge instructs the server to
notify the client immediately, and the lack of MessageExpunge notify the client immediately, and the lack of MessageExpunge
instructs the server to notify the client during execution of the instructs the server to notify the client during execution of the
next command as specified in [RFC3501]. MessageNew is handled next command as specified in [RFC3501]. MessageNew is handled
similarly by the server. similarly by the server.
5.1. FlagChange and AnnotationChange 5.1. FlagChange and AnnotationChange
If the flag/annotation change happens in the selected mailbox, the If the flag and/or message annotation change happens in the selected
server MUST notify the client by sending an unsolicited FETCH mailbox, the server MUST notify the client by sending an unsolicited
response, which MUST include UID and FLAGS/ANNOTATION FETCH data FETCH response, which MUST include UID and FLAGS/ANNOTATION FETCH
items. It MAY also send new FLAGS and/or OK [PERMANENTFLAGS ...] data items. It MAY also send new FLAGS and/or OK [PERMANENTFLAGS
responses. ...] responses.
If a search context is in effect as specified in [CONTEXT], an If a search context is in effect as specified in [CONTEXT], an
ESEARCH ADDTO or ESEARCH REMOVEFROM will also be generated, if ESEARCH ADDTO or ESEARCH REMOVEFROM will also be generated, if
appropriate. [[Alexey: I don't think this is needed: In this case, appropriate. In this case, the FETCH response MUST precede the
the FETCH response MUST precede the ESEARCH response.]] ESEARCH response.
If the change happens in another mailbox, then the response depends If the change happens in another mailbox, then the response depends
on whether CONDSTORE [RFC4551] is being used. If so, the server sends on whether CONDSTORE [RFC4551] and/or QRESYNC [QRESYNC] is being
a STATUS (HIGHESTMODSEQ) response. Note that whenever mailbox used. If so, the server sends a STATUS (HIGHESTMODSEQ) response.
UIDVALIDITY changes, the server MUST also include UIDVALIDITY in the Note that whenever mailbox UIDVALIDITY changes, the server MUST also
STATUS response. If CONDSTORE is not used, the server does not include UIDVALIDITY in the STATUS response. If the number of
notify the client. messages with \Seen flag changes, the server MAY also include the
UNSEEN in the STATUS response. If CONDSTORE/QRESYNC is not used and
the server choses not to include the UNSEEN, the server does not
notify the client. [[Open Issue: should there be a way to require
the server to return UNSEEN?]]
FlagChange covers the MessageRead, MessageTrash, FlagsSet and FlagChange covers the MessageRead, MessageTrash, FlagsSet and
FlagsClear events in [MSGEVENT]. FlagsClear events in [MSGEVENT].
[[Open Issue: Filip Navara requested for STATUS (UNSEEN) to be sent
for MessageRead. Arnt considers that unsound, since it involves
processing all messages in a mailbox after an event affecting only
Internet-draft February 2008
one message, and since it's not reliable anyway.]]
Example in the selected mailbox: Example in the selected mailbox:
S: * 99 FETCH (UID 9999 FLAGS ($Junk)) S: * 99 FETCH (UID 9999 FLAGS ($Junk))
And in another, with CONDSTORE in use: And in another, with CONDSTORE in use:
S: * STATUS Lists/Lemonade (HIGHESTMODSEQ 65666665) S: * STATUS Lists/Lemonade (HIGHESTMODSEQ 65666665)
5.2. MessageNew 5.2. MessageNew
This covers both MessageNew and MessageAppend in [MSGEVENT]. This covers both MessageNew and MessageAppend in [MSGEVENT].
If the new/appended message is in the selected mailbox, the server If the new/appended message is in the selected mailbox, the server
notifies the client by sending an unsolicited EXISTS response, notifies the client by sending an unsolicited EXISTS response,
followed by an unsolicited FETCH response containing the information followed by an unsolicited FETCH response containing the information
requested by the client. A FETCH response SHOULD NOT be generated for requested by the client. A FETCH response SHOULD NOT be generated
a new message created by the client on this particular connection, for a new message created by the client on this particular
for instance as the result of an APPEND or COPY command to the connection, for instance as the result of an APPEND or COPY command
selected mailbox performed by the client itself. The server MAY also to the selected mailbox performed by the client itself. The server
send a RECENT response, if the server marks the message as \Recent. MAY also send a RECENT response, if the server marks the message as
\Recent.
Note that a single EXISTS response can be returned for multiple Note that a single EXISTS response can be returned for multiple
MessageAppend/MessageNew events. MessageAppend/MessageNew events.
If a search context is in effect as specified in [CONTEXT], an If a search context is in effect as specified in [CONTEXT], an
ESEARCH ADDTO will also be generated, if appropriate. In this case, ESEARCH ADDTO will also be generated, if appropriate. In this case,
the EXISTS response MUST precede the ESEARCH response. Both the the EXISTS response MUST precede the ESEARCH response. Both the
NOTIFY command and the SEARCH and SORT commands (see Section 7) can NOTIFY command and the SEARCH and SORT commands (see Section 7) can
specify attributes to be returned for new messages. These attributes specify attributes to be returned for new messages. These
SHOULD be combined into a single FETCH response. The server SHOULD attributes SHOULD be combined into a single FETCH response. The
avoid sending duplicate data. The FETCH response(s) MUST follow any server SHOULD avoid sending duplicate data. The FETCH response(s)
ESEARCH ADDTO responses. MUST follow any ESEARCH ADDTO responses.
If the new/appended message is in another mailbox, the server sends If the new/appended message is in another mailbox, the server sends
an unsolicited STATUS (UIDNEXT MESSAGES) response for the relevant an unsolicited STATUS (UIDNEXT MESSAGES) response for the relevant
mailbox. If CONDSTORE (defined in [RFC4551]) is in use, the mailbox. If CONDSTORE (defined in [RFC4551]) is in use, the
HIGHESTMODSEQ status data item MUST be included in the STATUS HIGHESTMODSEQ status data item MUST be included in the STATUS
response. response.
The client SHOULD NOT use FETCH attributes that implicitly set the The client SHOULD NOT use FETCH attributes that implicitly set the
\seen flag, or that presuppose the existence of a given bodypart. \seen flag, or that presuppose the existence of a given bodypart.
UID, MODSEQ, FLAGS, ENVELOPE, BODY.PEEK[HEADER.FIELDS... and UID, MODSEQ, FLAGS, ENVELOPE, BODY.PEEK[HEADER.FIELDS... and
BODY/BODYSTRUCTURE may be the most useful attributes. BODY/BODYSTRUCTURE may be the most useful attributes.
Note that if a client asks to be notified of MessageNew events, the Note that if a client asks to be notified of MessageNew events, the
number of messages can increase at any time, and therefore the client number of messages can increase at any time, and therefore the
cannot refer to a specific message using the MSN/UID '*'. client cannot refer to a specific message using the MSN/UID '*'.
Internet-draft February 2008
Example in the selected mailbox: Example in the selected mailbox:
S: * 444 EXISTS S: * 444 EXISTS
S: * 444 FETCH (UID 9999) S: * 444 FETCH (UID 9999)
And in another, without CONDSTORE: And in another, without CONDSTORE:
S: * STATUS Lists/Lemonade (UIDNEXT 10002 MESSAGES 503) S: * STATUS Lists/Lemonade (UIDNEXT 10002 MESSAGES 503)
5.3. MessageExpunge 5.3. MessageExpunge
If the expunged message(s) is/are in the selected mailbox, the server If the expunged message(s) is/are in the selected mailbox, the
notifies the client using EXPUNGE (or VANISHED, if [QRESYNC] is being server notifies the client using EXPUNGE (or VANISHED, if [QRESYNC]
used). is supported by the server and enabled by the client).
If a search context is in effect as specified in [CONTEXT], an If a search context is in effect as specified in [CONTEXT], an
ESEARCH REMOVEFROM will also be generated, if appropriate. ESEARCH REMOVEFROM will also be generated, if appropriate.
If the expunged message(s) is/are in another mailbox, the server If the expunged message(s) is/are in another mailbox, the server
sends an unsolicited STATUS (UIDNEXT MESSAGES) response for the sends an unsolicited STATUS (UIDNEXT MESSAGES) response for the
relevant mailbox. If CONDSTORE is being used, HIGHESTMODSEQ MUST be relevant mailbox. If CONDSTORE is being used, HIGHESTMODSEQ MUST be
included in the STATUS response. included in the STATUS response.
Note that if a client requests MessageExpunge, the meaning of a MSN Note that if a client requests MessageExpunge, the meaning of a MSN
skipping to change at page 9, line 48 skipping to change at page 10, line 30
Example in the selected mailbox, without QRESYNC: Example in the selected mailbox, without QRESYNC:
S: * 444 EXPUNGE S: * 444 EXPUNGE
The same example in the selected mailbox, with QRESYNC: The same example in the selected mailbox, with QRESYNC:
S: * VANISHED 5444 S: * VANISHED 5444
And in another: And in another:
S: * STATUS misc (UIDNEXT 999 MESSAGES 554) S: * STATUS misc (UIDNEXT 999 MESSAGES 554)
5.4. MailboxName 5.4. MailboxName
These notifications are sent if an affected mailbox name was created These notifications are sent if an affected mailbox name was created
(with CREATE), deleted (with DELETE) or renamed (with RENAME). If a (with CREATE), deleted (with DELETE) or renamed (with RENAME). For
mailbox is created or deleted, the mailbox itself and its parent are a server that implements [RFC4314] granting or revocation of the 'l'
considered to be affected. right to the current user on the affected mailbox MUST be considered
mailbox creation/deletion respectively. If a mailbox is created or
deleted, the mailbox itself and its parent are considered to be
affected.
The server notifies the client by sending an unsolicited LIST The server notifies the client by sending an unsolicited LIST
response for each affected mailbox name. If, after the event, the
mailbox name does not refer to a mailbox accessible to the client,
the \Nonexistent flag MUST be included.
Internet-draft February 2008 For each LISTable mailbox renamed, the server sends an extended LIST
response [LISTEXT] for the new mailbox name, containing the OLDNAME
response for each affected mailbox name. If the mailbox name does not extended data item with the old mailbox name. When a mailbox is
refer to a mailbox after the event, the \Nonexistent flag MUST be renamed, its children are renamed too. No additional MailboxName
included. events are sent for children in this case. When INBOX is renamed, a
new INBOX is assumed to be created. No MailboxName event must be
sent for INBOX in this case.
For each selectable [[Alexey: is "selectable" important?]] mailbox Example of a newly created mailbox (or granting of the 'l' right on
renamed, the server sends an extended LIST response [LISTEXT] for the the mailbox):
new mailbox name, containing the OLDNAME extended data item with the
old mailbox name. When a mailbox is renamed, its children are
renamed too. No additional MailboxName events are sent for children
in this case. When INBOX is renamed, a new INBOX is assumed to be
created. No MailboxName event must be sent for INBOX in this case.
Example of a newly created mailbox:
S: * LIST () "/" "NewMailbox" S: * LIST () "/" "NewMailbox"
And a deleted mailbox: And a deleted mailbox (or revocation of the 'l' right on the
S: * LIST (\NonExistent) "/" "INBOX.DeletedMailbox" mailbox):
S: * LIST (\NonExistent) "." "INBOX.DeletedMailbox"
Example of a renamed mailbox: Example of a renamed mailbox:
S: * LIST () "/" "NewMailbox" ("OLDNAME" ("OldMailbox")) S: * LIST () "/" "NewMailbox" ("OLDNAME" ("OldMailbox"))
5.5. SubscriptionChange 5.5. SubscriptionChange
The server notifies the client by sending an unsolicited LIST The server notifies the client by sending an unsolicited LIST
responses for each affected mailbox name. If and only if the mailbox responses for each affected mailbox name. If and only if the mailbox
is subscribed after the event, the \Subscribed attribute (see is subscribed after the event, the \Subscribed attribute (see
[LISTEXT]) is included. [LISTEXT]) is included.
skipping to change at page 11, line 4 skipping to change at page 11, line 38
metadata should be included, but if necessary, all metadata must be metadata should be included, but if necessary, all metadata must be
included. included.
Example: Example:
S: * LIST "/" "INBOX" (METADATA (/comment)) S: * LIST "/" "INBOX" (METADATA (/comment))
5.7. ServerMetadataChange 5.7. ServerMetadataChange
The server sends an unsolicited METADATA response (as per Section The server sends an unsolicited METADATA response (as per Section
4.5.2 of [METADATA]). Only the names of changed metadata entries 4.5.2 of [METADATA]). Only the names of changed metadata entries
Internet-draft February 2008
SHOULD be returned in such METADATA responses. SHOULD be returned in such METADATA responses.
Example: Example:
S: * METADATA (/comment) S: * METADATA (/comment)
5.8. Notification Overflow 5.8. Notification Overflow
If the server is unable or unwilling to deliver as many notifications If the server is unable or unwilling to deliver as many
as it is being asked to, it may disable notifications for some or all notifications as it is being asked to, it may disable notifications
clients. It MUST notify these clients by sending an untagged "OK for some or all clients. It MUST notify these clients by sending an
[NOTIFICATIONOVERFLOW]" response and behave as if a NOTIFY NONE untagged "OK [NOTIFICATIONOVERFLOW]" response and behave as if a
command had just been received. NOTIFY NONE command had just been received.
Example: Example:
S: * OK [NOTIFICATIONOVERFLOW] ...A comment can go here... S: * OK [NOTIFICATIONOVERFLOW] ...A comment can go here...
5.9. ACL Changes 5.9. ACL Changes
Even if NOTIFY succeeds, it is still possible to loose access to the Even if NOTIFY succeeds, it is still possible to lose access to the
mailboxes monitoried at a later time. If this happens, the server mailboxes monitoried at a later time. If this happens, the server
MUST silently stop monitoring these mailboxes. If access is later MUST stop monitoring these mailboxes. If access is later granted,
granted, the server MUST restart event monitoring. the server MUST restart event monitoring.
The server SHOULD return the LIST response with the \NoAccess name
attribute if and when the mailbox loses the 'l' right. Simalarly,
the server SHOULD return the LIST response with no \NoAccess name
attribute, if the mailbox was previously reported as having
\NoAccess, and later on the 'l' right is granted.
6. Mailbox Specification 6. Mailbox Specification
Mailboxes to be monitored can be specified in several different ways. Mailboxes to be monitored can be specified in several different
ways.
Only 'selected' matches the currently selected mailbox. If the client Only 'selected' (section 6.1) matches the currently selected
specifies monitoring of the same mailbox several times, the first mailbox. All other mailbox specifications affect other (non-
specification wins. A common example is asking for events on the selected) mailboxes.
selected mailbox and some named mailboxes.
In this example, the client asks for MessageExpunge events for all If for any given event type the client specifies monitoring of the
same mailbox several times (using the same or different mailbox
specifications), the first specification wins.
Note that for different event types different <event-group>s can
apply to the same mailbox. The following example demonstrates this.
In this example, MessageNew and MessageExpunge events are reported
for INBOX due to the first <event-group>. SubscriptionChange event
will also be reported for INBOX due to the second <event-group>.
C: a notify set (mailboxes INBOX (Messagenew messageExpunge))
(personal (SubscriptionChange))
A typical client that supports the NOTIFY extension would ask for
events on the selected mailbox and some named mailboxes.
In this example, the client asks for FlagChange events for all
personal mailboxes except the selected mailbox: personal mailboxes except the selected mailbox:
C: a notify set (selected (MessageNew (uid flags) flagchange)) C: a notify set (selected (Messagenew (uid flags)
(personal (MessageNew FlagChange MessageExpunge)) messageExpunge)) (personal (MessageNew FlagChange
MessageExpunge))
6.1. Selected 6.1. Selected
Selected refers to the mailbox selected using either SELECT or Selected refers to the mailbox selected using either SELECT or
EXAMINE (see [RFC3501] section 6.3.1 and 6.3.2). When the IMAP EXAMINE (see [RFC3501] section 6.3.1 and 6.3.2). When the IMAP
connection is not in selected state, selected does not refer to any connection is not in selected state, selected does not refer to any
Internet-draft February 2008
mailbox. mailbox.
6.2. Personal 6.2. Personal
Personal refers to all selectable mailboxes in the user's personal Personal refers to all selectable mailboxes in the user's personal
namespace(s). namespace(s).
6.3. Inboxes 6.3. Inboxes
Inboxes refers to all selectable mailboxes in the user's personal Inboxes refers to all selectable mailboxes in the user's personal
skipping to change at page 13, line 4 skipping to change at page 14, line 15
The server MUST NOT do wildcard expansion. This means there is no The server MUST NOT do wildcard expansion. This means there is no
special treatment for the LIST wildcard characters ('*' and '%') if special treatment for the LIST wildcard characters ('*' and '%') if
they are present in mailbox names. they are present in mailbox names.
7. Extension to SEARCH and SORT commands 7. Extension to SEARCH and SORT commands
If the server that support the NOTIFY extension also supports If the server that support the NOTIFY extension also supports
CONTEXT=SEARCH and/or CONTEXT=SORT as defined in [CONTEXT], the CONTEXT=SEARCH and/or CONTEXT=SORT as defined in [CONTEXT], the
UPDATE return option is extended so that a client can request that UPDATE return option is extended so that a client can request that
FETCH attributes be returned when a new message is added to the FETCH attributes be returned when a new message is added to the
Internet-draft February 2008
context result set. context result set.
For example: For example:
C: a00 SEARCH RETURN (COUNT UPDATE (UID BODY[HEADER.FIELDS (TO C: a00 SEARCH RETURN (COUNT UPDATE (UID BODY[HEADER.FIELDS (TO
FROM FROM
SUBJECT)])) FROM "boss" S: * ESEARCH (TAG "a00") (COUNT SUBJECT)])) FROM "boss" S: * ESEARCH (TAG "a00") (COUNT
17) S: a00 OK [...a new message is delivered...] S: * EXISTS 17) S: a00 OK [...a new message is delivered...] S: * EXISTS
93 S: * ESEARCH (TAG "a00") ADDTO (0 93) S: * 93 FETCH (UID 93 S: * 93 FETCH (UID 127001 BODY[HEADER.FIELDS (FROM TO
127001 BODY[HEADER.FIELDS (FROM TO SUBJECT)] {76} S: Subject: SUBJECT)] {76} S: Subject: Re: good morning S: From:
Re: good morning S: From: myboss@example.org S: To: myboss@example.org S: To: bob@example.org S: S: ) S: *
bob@example.org S: S: ) ESEARCH (TAG "a00") ADDTO (0 93)
Note that the EXISTS response MUST precede the ESEARCH response, and Note that the EXISTS response MUST precede any FETCH responses, and
the FETCH response MUST follow the ESEARCH response. together they MUST precede the ESEARCH response.
No untagged FETCH response SHOULD be returned if a message becomes a No untagged FETCH response SHOULD be returned if a message becomes a
member of UPDATE SEARCH due to flag or annotation changes. member of UPDATE SEARCH due to flag or annotation changes.
8. Formal Syntax 8. Formal Syntax
The following syntax specification uses the Augmented Backus-Naur The following syntax specification uses the Augmented Backus-Naur
Form (ABNF) notation as specified in [RFC5234]. [RFC3501] defines the Form (ABNF) notation as specified in [RFC5234]. [RFC3501] defines
non-terminals "capability", "command-auth", "mailbox", "mailbox- the non-terminals "capability", "command-auth", "mailbox", "mailbox-
data", "resp-text-code" and "search-key". The "modifier-update" non- data", "resp-text-code" and "search-key". The "modifier-update" non-
terminal is defined in [CONTEXT]. terminal is defined in [CONTEXT]. "mbx-list-oflag" is defined in
[RFC3501] and updated by [LISTEXT].
Except as noted otherwise, all alphabetic characters are case- Except as noted otherwise, all alphabetic characters are case-
insensitive. The use of upper or lower case characters to define insensitive. The use of upper or lower case characters to define
token strings is for editorial clarity only. Implementations MUST token strings is for editorial clarity only. Implementations MUST
accept these strings in a case-insensitive fashion. accept these strings in a case-insensitive fashion.
capability =/ "X-DRAFT-W03-NOTIFY" capability =/ "X-DRAFT-W05-NOTIFY"
;; [[Note to RFC Editor: change the capability ;; [[Note to RFC Editor: change the capability
;; name before publication]] ;; name before publication]]
command-auth =/ notify command-auth =/ notify
notify = "NOTIFY" SP notify = "NOTIFY" SP
(notify-set / notify-none) (notify-set / notify-none)
notify-set = "SET" [status-indicator] SP event-groups notify-set = "SET" [status-indicator] SP event-groups
; Replace registered notification events ; Replace registered notification events
; with the specified list of events [[Alexey: ; with the specified list of events
what about "most specific" event overriding a
pattern?]]
notify-none = "NONE" notify-none = "NONE"
Internet-draft February 2008
; Cancel all registered notification ; Cancel all registered notification
; events. The client is not interested ; events. The client is not interested
; in receiving any events. ; in receiving any events.
status-indicator = SP "STATUS" status-indicator = SP "STATUS"
one-or-more-mailbox = mailbox / many-mailboxes one-or-more-mailbox = mailbox / many-mailboxes
many-mailboxes = "(" mailbox *(SP mailbox) ")" many-mailboxes = "(" mailbox *(SP mailbox) ")"
skipping to change at page 14, line 39 skipping to change at page 15, line 46
;; to receive any events for the specified ;; to receive any events for the specified
;; mailboxes. ;; mailboxes.
event = message-event event = message-event
/ mailbox-event / user-event / event-ext / mailbox-event / user-event / event-ext
message-match-criteria = "(" search-key ")" message-match-criteria = "(" search-key ")"
message-event = ( "MessageNew" [SP message-event = ( "MessageNew" [SP
"(" fetch-att *(SP fetch-att) ")" ] ) "(" fetch-att *(SP fetch-att) ")" ] )
SP "MessageExpunge" / "MessageExpunge"
/ "FlagChange" SP message-match-criteria / "FlagChange" SP message-match-criteria
/ "AnnotationChange" SP message-match-criteria / "AnnotationChange" SP message-match-criteria
;; "MessageNew" includes "MessageAppend" from ;; "MessageNew" includes "MessageAppend" from
;; [MSGEVENT]. "FlagChange" is any of ;; [MSGEVENT]. "FlagChange" is any of
;; "MessageRead", "MessageTrash", "FlagsSet", ;; "MessageRead", "MessageTrash", "FlagsSet",
;; "FlagsClear" [MSGEVENT]. "MessageExpunge" ;; "FlagsClear" [MSGEVENT]. "MessageExpunge"
;; includes "MessageExpire" [MSGEVENT]. ;; includes "MessageExpire" [MSGEVENT].
;; MessageNew and MessageExpunge MUST always
;; be specified together. If FlagChange is
;; specified, then MessageNew and MessageExpunge
;; MUST be specified as well.
;; The fett-att list may only be present for the
;; SELECTED mailbox filter (<filter-mailboxes>).
mailbox-event = "MailboxName" / mailbox-event = "MailboxName" /
"SubscriptionChange" / "MailboxMetadataChange" "SubscriptionChange" / "MailboxMetadataChange"
; "SubscriptionChange" includes ; "SubscriptionChange" includes
; MailboxSubscribe and MailboxUnSubscribe. ; MailboxSubscribe and MailboxUnSubscribe.
; "MailboxName" includes MailboxCreate, ; "MailboxName" includes MailboxCreate,
; "MailboxDelete" and "MailboxRename". ; "MailboxDelete" and "MailboxRename".
Internet-draft February 2008
user-event = "ServerMetadataChange" user-event = "ServerMetadataChange"
event-ext = atom event-ext = atom
;; For future extensions ;; For future extensions
oldname-extended-item = "OLDNAME" SP "(" mailbox ")" oldname-extended-item = "OLDNAME" SP "(" mailbox ")"
;; Extended data item (mbox-list-extended-item) ;; Extended data item (mbox-list-extended-item)
;; returned in a LIST response when a mailbox is ;; returned in a LIST response when a mailbox is
;; renamed. ;; renamed.
;; Note 1: the OLDNAME tag can be returned ;; Note 1: the OLDNAME tag can be returned
skipping to change at page 15, line 36 skipping to change at page 16, line 49
event-name = message-event-name / mailbox-event / event-name = message-event-name / mailbox-event /
user-event user-event
unsupported-events-code = "BADEVENT" unsupported-events-code = "BADEVENT"
SP "(" event-name *(SP event-name) ")" SP "(" event-name *(SP event-name) ")"
modifier-update = "UPDATE" modifier-update = "UPDATE"
[ "(" fetch-att *(SP fetch-att) ")" ] [ "(" fetch-att *(SP fetch-att) ")" ]
mbx-list-oflag =/ "\NoAccess"
9. Security considerations 9. Security considerations
It is very easy for a client to deny itself service using NOTIFY: It is very easy for a client to deny itself service using NOTIFY:
Asking for all events on all mailboxes may work on a small server, Asking for all events on all mailboxes may work on a small server,
but with a big server can swamp the client's network connection or but with a big server can swamp the client's network connection or
processing capability. In the worst case, the server's processing processing capability. In the worst case, the server's processing
could also degrade the service it offers to other clients. could also degrade the service it offers to other clients.
Server authors should be aware that if a client issues requests and Server authors should be aware that if a client issues requests and
does not listen to the resulting responses, the TCP window can easily does not listen to the resulting responses, the TCP window can
fill up, and a careless server might block. This problem exists in easily fill up, and a careless server might block. This problem
plain IMAP, however this extension magnifies the problem. exists in plain IMAP, however this extension magnifies the problem.
This extensions makes it possible to retrieve messages immediately This extensions makes it possible to retrieve messages immediately
when they are added to the mailbox. This makes it wholly impractical when they are added to the mailbox. This makes it wholly impractical
to delete sensitive messages using programs like imapfilter. Using to delete sensitive messages using programs like imapfilter. Using
[SIEVE] or similar is much better. [SIEVE] or similar is much better.
Internet-draft February 2008
10. IANA considerations 10. IANA considerations
The IANA is requested to add NOTIFY to the list of IMAP extensions, The IANA is requested to add NOTIFY to the list of IMAP extensions,
http://www.iana.org/assignments/imap4-capabilities. http://www.iana.org/assignments/imap4-capabilities.
10.1. Initial LIST-EXTENDED extended data item registrations 10.1. Initial LIST-EXTENDED extended data item registrations
It is requested that the following entry be added to the LIST- It is requested that the following entry be added to the LIST-
EXTENDED extended data item registry [LISTEXT]: EXTENDED extended data item registry [LISTEXT]:
skipping to change at page 16, line 36 skipping to change at page 18, line 4
Which LIST-EXTENDED option(s) (and their types) causes this extended Which LIST-EXTENDED option(s) (and their types) causes this extended
data item to be returned (if any): none data item to be returned (if any): none
Published specification : RFC XXXX, Section 5.4. Published specification : RFC XXXX, Section 5.4.
Security considerations: none Security considerations: none
Intended usage: COMMON Intended usage: COMMON
Person and email address to contact for further information: Person and email address to contact for further information:
Alexey Melnikov <Alexey.Melnikov@isode.com> Alexey Melnikov <Alexey.Melnikov@isode.com>
Owner/Change controller: iesg@ietf.org Owner/Change controller: iesg@ietf.org
11. Acknowedgements 11. Acknowedgements
The authors gratefully acknowledge the help of Peter Coates, Dave The authors gratefully acknowledge the help of Peter Coates, Dave
Cridland, Mark Crispin, Cyrus Daboo, Abhijit Menon-Sen and Eric Cridland, Mark Crispin, Cyrus Daboo, Abhijit Menon-Sen, Timo
Burger. In particular, Peter Coates contributed lots of text and Sirainen and Eric Burger. In particular, Peter Coates contributed
useful suggestions to this document. lots of text and useful suggestions to this document.
Various examples are copied from other RFCs. Various examples are copied from other RFCs.
This document builds on one published and two unpublished drafts by This document builds on one published and two unpublished drafts by
the same authors. the same authors.
12. Normative References 12. Normative References
Internet-draft February 2008
[RFC2119] Bradner, "Key words for use in RFCs to Indicate [RFC2119] Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, Harvard University, March Requirement Levels", RFC 2119, Harvard University, March
1997. 1997.
[RFC2177] Leiba, "IMAP4 IDLE Command", RFC 2177, IBM, June 1997. [RFC2177] Leiba, "IMAP4 IDLE Command", RFC 2177, IBM, June 1997.
[RFC3501] Crispin, "Internet Message Access Protocol - Version [RFC3501] Crispin, "Internet Message Access Protocol - Version
4rev1", RFC 3501, University of Washington, June 2003. 4rev1", RFC 3501, University of Washington, June 2003.
[RFC5234] Crocker, Overell, "Augmented BNF for Syntax [RFC5234] Crocker, Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 5234, Brandenburg Specifications: ABNF", RFC 5234, Brandenburg
Internetworking, THUS plc, January 2008. Internetworking, THUS plc, January 2008.
[RFC4314] Melnikov, "IMAP4 Access Control List (ACL) Extension", RFC [RFC4314] Melnikov, "IMAP4 Access Control List (ACL) Extension",
4314, December 2005. RFC 4314, December 2005.
[RFC4466] Melnikov, Daboo, "Collected Extensions to IMAP4 ABNF", RFC [RFC4466] Melnikov, Daboo, "Collected Extensions to IMAP4 ABNF",
4466, Isode Ltd., April 2006. RFC 4466, Isode Ltd., April 2006.
[RFC4551] Melnikov, Hole, "IMAP Extension for Conditional STORE [RFC4551] Melnikov, Hole, "IMAP Extension for Conditional STORE
Operation or Quick Flag Changes Resynchronization", RFC Operation or Quick Flag Changes Resynchronization", RFC
4551, Isode Ltd., June 2006. 4551, Isode Ltd., June 2006.
[LISTEXT] Leiba, Melnikov, "IMAP4 List Command Extensions", draft- [LISTEXT] Leiba, Melnikov, "IMAP4 List Command Extensions", draft-
ietf-imapext-list-extensions-18 (work in progress), IBM, ietf-imapext-list-extensions-18 (work in progress), IBM,
September 2006. September 2006.
[METADATA] Daboo, "IMAP METADATA Extension", draft-daboo-imap- [METADATA] Daboo, "IMAP METADATA Extension", draft-daboo-imap-
annotatemore-12 (work in progress), Apple Computer, Inc., annotatemore-12 (work in progress), Apple Computer, Inc.,
December 2007. December 2007.
[MSGEVENT] Newman, C. and R. Gellens, "Internet Message Store [MSGEVENT] Newman, C. and R. Gellens, "Internet Message Store
Events", draft-ietf-lemonade-msgevent-05.txt (work in Events", draft-ietf-lemonade-msgevent-05.txt (work in
progress), Sun, January 2008. progress), January 2008.
[CONTEXT] Cridland, D. and C. King, "Contexts for IMAP4", work in [CONTEXT] Cridland, D. and C. King, "Contexts for IMAP4", work in
progress, draft-cridland-imap-context-03.txt, Isode, June progress, draft-cridland-imap-context-03.txt, Isode, June
2007. 2007.
13. Informative References 13. Informative References
[SIEVE] Guenther, P. and T. Showalter, "Sieve: A Mail Filtering [SIEVE] Guenther, P. and T. Showalter, "Sieve: A Mail Filtering
Language", RFC 5228, January 2008. Language", RFC 5228, January 2008.
[QRESYNC] Melnikov, Cridland, Wilson, "IMAP4 Extensions for Quick [QRESYNC] Melnikov, A., Cridland, D. and C. Wilson, "IMAP4
Mailbox Resynchronization", draft-ietf-lemonade-reconnect- Extensions for Quick Mailbox Resynchronization", RFC
client-06.txt (work in progress), September 2007. 5162, March 2008.
Internet-draft February 2008
[EMAIL-ARCH] Crocker, "Internet Mail Architecture", draft-crocker- [EMAIL-ARCH] Crocker, "Internet Mail Architecture", draft-crocker-
email-arch-10 (work in progress), February 2008. email-arch-10 (work in progress), February 2008.
14. Authors' Addresses 14. Authors' Addresses
Curtis King Curtis King
Isode Ltd Isode Ltd
5 Castle Business Village 5 Castle Business Village
36 Station Road 36 Station Road
skipping to change at page 18, line 29 skipping to change at page 20, line 4
Email: Curtis.King@isode.com Email: Curtis.King@isode.com
Alexey Melnikov Alexey Melnikov
Isode Ltd Isode Ltd
5 Castle Business Village 5 Castle Business Village
36 Station Road 36 Station Road
Hampton, Middlesex TW12 2BX Hampton, Middlesex TW12 2BX
UK UK
Email: Alexey.Melnikov@isode.com Email: Alexey.Melnikov@isode.com
Arnt Gulbrandsen Arnt Gulbrandsen
Oryx Mail Systems GmbH Oryx Mail Systems GmbH
Schweppermannstr. 8 Schweppermannstr. 8
D-81671 Muenchen D-81671 Muenchen
Germany Germany
Email: arnt@oryx.com Email: arnt@oryx.com
Internet-draft February 2008
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed
pertain to the implementation or use of the technology described in to pertain to the implementation or use of the technology described
this document or the extent to which any license under such rights in this document or the extent to which any license under such
might or might not be available; nor does it represent that it has rights might or might not be available; nor does it represent that
made any independent effort to identify any such rights. Information it has made any independent effort to identify any such rights.
on the procedures with respect to rights in RFC documents can be Information on the procedures with respect to rights in RFC
found in BCP 78 and BCP 79. documents can be found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of attempt made to obtain a general license or permission for the use
such proprietary rights by implementers or users of this of such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository
http://www.ietf.org/ipr. at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Full Copyright Statement Full Copyright Statement
Copyright (C) The IETF Trust (2008). This document is subject to the Copyright (C) The IETF Trust (2008). This document is subject to
rights, licenses and restrictions contained in BCP 78, and except as the rights, licenses and restrictions contained in BCP 78, and
set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 87 change blocks. 
247 lines changed or deleted 264 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/