| 1 |
<pre>Network Working Group A. Melnikov |
| 2 |
Request for Comments: 5466 C. King |
| 3 |
Category: Standards Track Isode Ltd |
| 4 |
February 2009 |
| 5 |
|
| 6 |
|
| 7 |
<span class="h1">IMAP4 Extension for Named Searches (Filters)</span> |
| 8 |
|
| 9 |
Status of This Memo |
| 10 |
|
| 11 |
This document specifies an Internet standards track protocol for the |
| 12 |
Internet community, and requests discussion and suggestions for |
| 13 |
improvements. Please refer to the current edition of the "Internet |
| 14 |
Official Protocol Standards" (STD 1) for the standardization state |
| 15 |
and status of this protocol. Distribution of this memo is unlimited. |
| 16 |
|
| 17 |
Copyright Notice |
| 18 |
|
| 19 |
Copyright (c) 2009 IETF Trust and the persons identified as the |
| 20 |
document authors. All rights reserved. |
| 21 |
|
| 22 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 23 |
Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/</a> |
| 24 |
<a href="http://trustee.ietf.org/license-info">license-info</a>) in effect on the date of publication of this document. |
| 25 |
Please review these documents carefully, as they describe your rights |
| 26 |
and restrictions with respect to this document. |
| 27 |
|
| 28 |
Abstract |
| 29 |
|
| 30 |
The document defines a way to persistently store named IMAP (<a href="./rfc3501">RFC</a> |
| 31 |
<a href="./rfc3501">3501</a>) searches on the server. Such named searches can be |
| 32 |
subsequently referenced in a SEARCH or any other command that accepts |
| 33 |
a search criterion as a parameter. |
| 34 |
|
| 35 |
Table of Contents |
| 36 |
|
| 37 |
<a href="#section-1">1</a>. Introduction and Overview . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 38 |
<a href="#section-2">2</a>. Conventions Used in This Document . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 39 |
<a href="#section-3">3</a>. IMAP Protocol Changes . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 40 |
<a href="#section-3.1">3.1</a>. FILTER SEARCH Criterion . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a> |
| 41 |
<a href="#section-3.2">3.2</a>. Managing Filters Using SETMETADATA/GETMETADATA Commands . . <a href="#page-4">4</a> |
| 42 |
<a href="#section-4">4</a>. Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 43 |
<a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 44 |
<a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 45 |
<a href="#section-7">7</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 46 |
<a href="#section-8">8</a>. Normative References . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Melnikov & King Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction and Overview</span> |
| 58 |
|
| 59 |
Persistent named searches described in this document allow clients to |
| 60 |
save favorite searches on the server. Such saved searches can save |
| 61 |
bandwidth for clients that need to regularly repeat them. |
| 62 |
|
| 63 |
The FILTERS IMAP extension adds a new FILTER search criterion for |
| 64 |
referencing persistent named searches (a.k.a. "filters"), as well as |
| 65 |
reuses GETMETADATA/SETMETADATA commands [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>] for listing/ |
| 66 |
creating/updating/deleting such filters. |
| 67 |
|
| 68 |
A filter can be private (only accessible to the logged-in user) or |
| 69 |
public (accessible to all logged-in users). Both a private and a |
| 70 |
public filter with the same name can exist at the same time. If both |
| 71 |
filter types with the same name exist, the FILTER SEARCH criterion |
| 72 |
(see <a href="#section-3.1">Section 3.1</a>) MUST use the value of the private filter; |
| 73 |
otherwise, it MUST use the value of the filter that exists. |
| 74 |
|
| 75 |
Let us call a pair of filter name and filter type a "typed filter". |
| 76 |
Each typed filter can have a value (which is a valid IMAP SEARCH |
| 77 |
criteria conforming to ABNF for the "search-criteria" non-terminal) |
| 78 |
and an optional human-readable description. The SETMETADATA command |
| 79 |
creates or updates the value and/or the description of a typed |
| 80 |
filter. |
| 81 |
|
| 82 |
Values of all search keys stored in a filter MUST be encoded in |
| 83 |
UTF-8. |
| 84 |
|
| 85 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Conventions Used in This Document</span> |
| 86 |
|
| 87 |
In examples, "C:" and "S:" indicate lines sent by the client and |
| 88 |
server, respectively. If a single "C:" or "S:" label applies to |
| 89 |
multiple lines, then the line breaks between those lines are for |
| 90 |
editorial clarity only and are not part of the actual protocol |
| 91 |
exchange. |
| 92 |
|
| 93 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 94 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 95 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 96 |
|
| 97 |
Basic familiarity with the METADATA-SERVER extension [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>] and |
| 98 |
terms defined therein is required to understand this document. |
| 99 |
|
| 100 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. IMAP Protocol Changes</span> |
| 101 |
|
| 102 |
The IMAP extension for persistent named searches is present in any |
| 103 |
IMAP4 implementation that advertises "FILTERS" as one of the |
| 104 |
supported capabilities in the CAPABILITY response or response code. |
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Melnikov & King Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. FILTER SEARCH Criterion</span> |
| 114 |
|
| 115 |
The FILTER criterion for the SEARCH command allows a client to |
| 116 |
reference by name a filter stored on the server. Such filter was |
| 117 |
created by setting the server annotation named "/private/filters/ |
| 118 |
values/<filter_name>" (or the server annotation "/shared/filters/ |
| 119 |
values/<filter_name>", if "/private/filters/values/<filter_name>" |
| 120 |
doesn't exist) using the SETMETADATA command as described in |
| 121 |
<a href="#section-3.2">Section 3.2</a>. |
| 122 |
|
| 123 |
Syntax: FILTER <filter_name> |
| 124 |
|
| 125 |
When the named filter exists, its search criterion (i.e., the |
| 126 |
associated entry value) is inserted verbatim instead of the FILTER |
| 127 |
search-key. For example, the following SEARCH command |
| 128 |
|
| 129 |
C: a SEARCH UID 300:900 FILTER on-the-road SINCE "3-Dec-2002" |
| 130 |
|
| 131 |
would be equivalent to the following |
| 132 |
|
| 133 |
C: a SEARCH UID 300:900 OR SMALLER 5000 FROM "[email protected]" |
| 134 |
SINCE "3-Dec-2002" |
| 135 |
|
| 136 |
assuming the filter "on-the-road" exists and contains the value 'OR |
| 137 |
SMALLER 5000 FROM "[email protected]"'. |
| 138 |
|
| 139 |
A reference to a nonexistent or unaccessible (e.g., due to access |
| 140 |
control restrictions) filter MUST cause failure of the SEARCH command |
| 141 |
with the tagged NO response that includes the UNDEFINED-FILTER |
| 142 |
response code followed by the name of the nonexistent/unaccessible |
| 143 |
filter. |
| 144 |
|
| 145 |
Note the server SHOULD verify that each search criterion referenced |
| 146 |
by the FILTER search key is a full and correct search criterion. For |
| 147 |
example, the server should fail the SEARCH command if its SEARCH |
| 148 |
criterion references a filter containing "OR SMALLER" search |
| 149 |
criterion, because this value is lacking one parameter and thus is |
| 150 |
not a fully specified search criterion. |
| 151 |
|
| 152 |
Note that a named filter itself can reference another filter using |
| 153 |
the FILTER search-key. Implementations MUST be able to perform at |
| 154 |
least 3 substitution passes on the SEARCH command criterion. If an |
| 155 |
implementation allows for more passes, it MUST implement some kind of |
| 156 |
loop detection. If an implementation detects a loop or still sees a |
| 157 |
FILTER search-key after performing at least 3 substitutions, it MUST |
| 158 |
behave as if the specified filter doesn't exist (as described above). |
| 159 |
|
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Melnikov & King Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 167 |
|
| 168 |
|
| 169 |
Note that use of the FILTER search key implies the CHARSET "UTF-8" |
| 170 |
parameter to the SEARCH/UID SEARCH command. If the SEARCH/UID SEARCH |
| 171 |
command includes the explicit CHARSET parameter with the value other |
| 172 |
than "UTF-8" or "US-ASCII", then such command MUST result in the |
| 173 |
tagged BAD response from the server. Such tagged response MUST |
| 174 |
contain the BADCHARSET response code (see [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>]). |
| 175 |
|
| 176 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Managing Filters Using SETMETADATA/GETMETADATA Commands</span> |
| 177 |
|
| 178 |
Any server compliant with this document MUST either implement the |
| 179 |
METADATA-SERVER (or METADATA) [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>] extension, or implement |
| 180 |
SETMETADATA/GETMETADATA commands described in [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>] so that they |
| 181 |
work for the case of empty mailbox name (i.e., for managing server |
| 182 |
annotations) and for the entries specified in this section. |
| 183 |
|
| 184 |
This document reserves two hierarchies of per-server entries under |
| 185 |
the "/private/filters/values" and "/shared/filters/values" roots (see |
| 186 |
[<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>]) for storing filter values. The value of a "/private/ |
| 187 |
filters/values/<filter_name>" or a "/shared/filters/values/ |
| 188 |
<filter_name>" server annotation is an IMAP SEARCH criteria, |
| 189 |
conforming to ABNF for the "search-criteria" non-terminal. A name of |
| 190 |
a filter is governed by the ABNF for the "filter-name" non-terminal. |
| 191 |
|
| 192 |
Note that values of all search keys stored in these entries MUST be |
| 193 |
encoded in UTF-8. |
| 194 |
|
| 195 |
A new filter named "<filter_name>" can be created (or an existing |
| 196 |
filter can be modified) by storing a non-NIL value in the "/private/ |
| 197 |
filters/values/<filter_name>" server entry (or in the "/shared/ |
| 198 |
filters/values/<filter_name>") using the SETMETADATA [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>] |
| 199 |
command. The server SHOULD verify that each search criterion stored |
| 200 |
in such a server entry is a full and correct search criterion. |
| 201 |
|
| 202 |
A filter can be deleted by storing the NIL value in both the |
| 203 |
"/private/filters/values/<filter_name>" and the "/shared/filters/ |
| 204 |
values/<filter_name>" entries. |
| 205 |
|
| 206 |
A filter can be renamed by first creating a filter with the new name |
| 207 |
(that has the same value as the old one) and then deleting the filter |
| 208 |
with the old one. |
| 209 |
|
| 210 |
If both "/private/filters/values/<filter_name>" and "/shared/filters/ |
| 211 |
values/<filter_name>" server annotations exist, then the value of the |
| 212 |
"/private/filters/values/<filter_name>" is used when evaluating the |
| 213 |
corresponding FILTER SEARCH key (see <a href="#section-3.1">Section 3.1</a>). Otherwise the |
| 214 |
non-NIL (existent) value is used. |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Melnikov & King Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 223 |
|
| 224 |
|
| 225 |
If the server is unable to create a new typed filter because the |
| 226 |
maximum number of allowed filters has already been reached, the |
| 227 |
server MUST return a tagged NO response with a "[METADATA TOOMANY]" |
| 228 |
response code, as defined in [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>]. |
| 229 |
|
| 230 |
C: a007 SETMETADATA "" ("/private/filters/values/on-the-road" |
| 231 |
"OR SMALLER 5000 FROM \"[email protected]\"") |
| 232 |
S: a007 OK SETMETADATA complete |
| 233 |
|
| 234 |
Client implementation note: As multiple clients might read and write |
| 235 |
filter values, it is possible that one client will use a SEARCH key |
| 236 |
that might not be recognized by another client that tries to present |
| 237 |
a user interface for editing a filter value. In order to help other |
| 238 |
clients to (partially) parse filter values for editing purposes, a |
| 239 |
client storing a filter value SHOULD use () around any SEARCH key not |
| 240 |
defined in [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>]. For example, if there is an IMAP extension |
| 241 |
that defines a new x-dsfa SEARCH key that takes 2 parameters, then |
| 242 |
the following SEARCH criterion 'from "@example.com>" x-dsfa from 5' |
| 243 |
should be stored as 'from "@example.com>" (x-dsfa from 5)'. |
| 244 |
|
| 245 |
Note that filter names are restricted to a subset of US-ASCII, as |
| 246 |
described in <a href="#section-4">Section 4</a>. So they might not always be meaningful to |
| 247 |
users and thus not necessarily suitable for display purposes. In |
| 248 |
order to help with storing human-readable descriptions of filters, |
| 249 |
this document also reserves two hierarchies of server entries under |
| 250 |
the "/private/filters/descriptions" and "/shared/filters/ |
| 251 |
descriptions" roots. The value of a "/private/filters/descriptions/ |
| 252 |
<filter_name>" or a "/shared/filters/descriptions/<filter_name>" |
| 253 |
server annotation is a human-readable description for the |
| 254 |
<filter_name> filter, encoded in UTF-8 [<a href="#ref-UTF-8" title=""UTF-8, a transformation format of ISO 10646"">UTF-8</a>]. If the "/private/ |
| 255 |
filters/descriptions/<filter_name>" server annotation exists, its |
| 256 |
value is used by the client as the filter description. Otherwise, |
| 257 |
the value of the "/shared/filters/descriptions/<filter_name>" server |
| 258 |
annotation is used as the filter description. In the absence of both |
| 259 |
the "/private/filters/descriptions/<filter_name>" and the "/shared/ |
| 260 |
filters/descriptions/<filter_name>" entries, the client MAY display |
| 261 |
the name of the filter as its description. |
| 262 |
|
| 263 |
The description string SHOULD be annotated with one or more language |
| 264 |
tags [<a href="./rfc4646" title=""Tags for Identifying Languages"">RFC4646</a>] as specified in Chapter 16.9 of [<a href="#ref-Unicode" title=""The Unicode Standard 5.0"">Unicode</a>]. In the |
| 265 |
absence of any language tag, the "i-default" [<a href="./rfc2277" title=""IETF Policy on Character Sets and Languages"">RFC2277</a>] language |
| 266 |
SHOULD be assumed. Description in multiple languages MAY be present |
| 267 |
in a single description string. This is done by concatenating |
| 268 |
descriptions in multiple languages into a single string, each |
| 269 |
description prefixed with its language tag, for example |
| 270 |
"<ru><...description in Russian...><fr-ca><...description in |
| 271 |
French...>". Note that here <ru> is a language tag consisting of 3 |
| 272 |
Unicode characters: <U+E0001>, <U+E0072>, <U+E0075>; and <fr-ca> is a |
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Melnikov & King Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 279 |
|
| 280 |
|
| 281 |
language tag consisting of 6 Unicode characters: <U+E0001>, |
| 282 |
<U+E0066>, <U+E0072>, <U+E002D>, <U+E0063>, <U+E0061>. |
| 283 |
|
| 284 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Formal Syntax</span> |
| 285 |
|
| 286 |
The following syntax specification uses the Augmented Backus-Naur |
| 287 |
Form (ABNF) notation as specified in [<a href="#ref-ABNF" title=""Augmented BNF for Syntax Specifications: ABNF"">ABNF</a>]. |
| 288 |
|
| 289 |
Non-terminals referenced but not defined below are as defined by |
| 290 |
[<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>] or [<a href="#ref-IMAPABNF" title=""Collected Extensions to IMAP4 ABNF"">IMAPABNF</a>]. |
| 291 |
|
| 292 |
Except as noted otherwise, all alphabetic characters are case- |
| 293 |
insensitive. The use of upper or lower case characters to define |
| 294 |
token strings is for editorial clarity only. Implementations MUST |
| 295 |
accept these strings in a case-insensitive fashion. |
| 296 |
|
| 297 |
capability =/ "FILTERS" |
| 298 |
|
| 299 |
search-criteria = search-key *(SP search-key) |
| 300 |
|
| 301 |
search-key =/ "FILTER" SP filter-name |
| 302 |
;; New SEARCH criterion for referencing filters |
| 303 |
|
| 304 |
filter-name = 1*<any ATOM-CHAR except "/"> |
| 305 |
;; Note that filter-name disallows UTF-8 or |
| 306 |
;; the following characters: "(", ")", "{", |
| 307 |
;; " ", "%", "*", "]". See definition of |
| 308 |
;; ATOM-CHAR [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>]. |
| 309 |
|
| 310 |
resp-text-code =/ "UNDEFINED-FILTER" SP filter-name |
| 311 |
|
| 312 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span> |
| 313 |
|
| 314 |
General issues relevant to [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>] (in particular to the SEARCH |
| 315 |
command) and METADATA-SERVER extension [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>] are also relevant |
| 316 |
to this document. |
| 317 |
|
| 318 |
Note that excessive use of filters can potentially simplify denial- |
| 319 |
of-service attacks, especially if combined with poor implementations |
| 320 |
and lack of loop detection (i.e., detection of filters referencing |
| 321 |
each other to create a loop). Servers that allow for anonymous |
| 322 |
access SHOULD NOT allow anonymous users to create/edit/delete |
| 323 |
filters. |
| 324 |
|
| 325 |
Also note that stored filters can potentially disclose personal |
| 326 |
information about users. When confidentiality of such information is |
| 327 |
important, clients MUST use TLS and/or SASL security layer (or |
| 328 |
similar) as recommended in [<a href="./rfc3501" title=""INTERNET MESSAGE ACCESS PROTOCOL - VERSION 4rev1"">RFC3501</a>]. Also, clients should use |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Melnikov & King Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 335 |
|
| 336 |
|
| 337 |
private filters instead of public, unless they desire to share such |
| 338 |
information with other users. |
| 339 |
|
| 340 |
As always, it is important to thoroughly test clients and servers |
| 341 |
when implementing this extension. |
| 342 |
|
| 343 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span> |
| 344 |
|
| 345 |
IMAP4 capabilities are registered by publishing a Standards Track or |
| 346 |
IESG-approved Experimental RFC. The IMAP4 capabilities registry is |
| 347 |
available from <a href="http://www.iana.org">http://www.iana.org</a>. |
| 348 |
|
| 349 |
This document defines the FILTERS IMAP capability. IANA has added it |
| 350 |
to the registry. |
| 351 |
|
| 352 |
IANA has added the following 4 entries to the [<a href="#ref-METADATA" title=""The IMAP METADATA Extension"">METADATA</a>] registry: |
| 353 |
|
| 354 |
To: [email protected] |
| 355 |
Subject: IMAP METADATA Entry Registration |
| 356 |
Type: Server |
| 357 |
Name: /private/filters/values/<filter_name> |
| 358 |
Description: Contains an IMAP SEARCH criteria. Defined in <a href="./rfc5466">RFC 5466</a>. |
| 359 |
Content-type: text/plain; charset=utf-8 |
| 360 |
Contact person: Alexey Melnikov |
| 361 |
Email: [email protected] |
| 362 |
|
| 363 |
To: [email protected] |
| 364 |
Subject: IMAP METADATA Entry Registration |
| 365 |
Type: Server |
| 366 |
Name: /shared/filters/values/<filter_name> |
| 367 |
Description: Contains an IMAP SEARCH criterion. Defined in <a href="./rfc5466">RFC</a> |
| 368 |
<a href="./rfc5466">5466</a>. |
| 369 |
Content-type: text/plain; charset=utf-8 |
| 370 |
Contact person: Alexey Melnikov |
| 371 |
Email: [email protected] |
| 372 |
|
| 373 |
To: [email protected] |
| 374 |
Subject: IMAP METADATA Entry Registration |
| 375 |
Type: Server |
| 376 |
Name: /private/filters/descriptions/<filter_name> |
| 377 |
Description: Contains a user-specific human-readable description of |
| 378 |
a named SEARCH criterion stored in the /private/filters/values/ |
| 379 |
<filter_name> or /shared/filters/values/<filter_name> annotation. |
| 380 |
The value is in UTF-8. Defined in <a href="./rfc5466">RFC 5466</a>. |
| 381 |
Content-type: text/plain; charset=utf-8 |
| 382 |
Contact person: Alexey Melnikov |
| 383 |
Email: [email protected] |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Melnikov & King Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 391 |
|
| 392 |
|
| 393 |
To: [email protected] |
| 394 |
Subject: IMAP METADATA Entry Registration |
| 395 |
Type: Server |
| 396 |
Name: /shared/filters/descriptions/<filter_name> |
| 397 |
Description: Contains a global (shared among all users) human- |
| 398 |
readable description of a named SEARCH criterion stored in the |
| 399 |
/private/filters/values/<filter_name> or /shared/filters/values/ |
| 400 |
<filter_name> annotation. The value is in UTF-8. Defined in <a href="./rfc5466">RFC</a> |
| 401 |
<a href="./rfc5466">5466</a>. |
| 402 |
Content-type: text/plain; charset=utf-8 |
| 403 |
Contact person: Alexey Melnikov |
| 404 |
Email: [email protected] |
| 405 |
|
| 406 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span> |
| 407 |
|
| 408 |
Thanks to David Cridland, Arnt Gulbrandsen, Chris Newman, and Timo |
| 409 |
Sirainen for comments and suggestions on this document. Special |
| 410 |
thank you to Brian E. Carpenter for the GenArt review. |
| 411 |
|
| 412 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Normative References</span> |
| 413 |
|
| 414 |
[<a id="ref-ABNF">ABNF</a>] Crocker, D., Ed. and P. Overell, Ed., "Augmented BNF for |
| 415 |
Syntax Specifications: ABNF", STD 68, <a href="./rfc5234">RFC 5234</a>, |
| 416 |
January 2008. |
| 417 |
|
| 418 |
[<a id="ref-IMAPABNF">IMAPABNF</a>] Melnikov, A. and C. Daboo, "Collected Extensions to IMAP4 |
| 419 |
ABNF", <a href="./rfc4466">RFC 4466</a>, April 2006. |
| 420 |
|
| 421 |
[<a id="ref-METADATA">METADATA</a>] Daboo, C., "The IMAP METADATA Extension", <a href="./rfc5464">RFC 5464</a>, |
| 422 |
February 2009. |
| 423 |
|
| 424 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 425 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 426 |
|
| 427 |
[<a id="ref-RFC2277">RFC2277</a>] Alvestrand, H., "IETF Policy on Character Sets and |
| 428 |
Languages", <a href="https://www.rfc-editor.org/bcp/bcp18">BCP 18</a>, <a href="./rfc2277">RFC 2277</a>, January 1998. |
| 429 |
|
| 430 |
[<a id="ref-RFC3501">RFC3501</a>] Crispin, M., "INTERNET MESSAGE ACCESS PROTOCOL - VERSION |
| 431 |
4rev1", <a href="./rfc3501">RFC 3501</a>, March 2003. |
| 432 |
|
| 433 |
[<a id="ref-RFC4646">RFC4646</a>] Phillips, A. and M. Davis, "Tags for Identifying |
| 434 |
Languages", <a href="https://www.rfc-editor.org/bcp/bcp47">BCP 47</a>, <a href="./rfc4646">RFC 4646</a>, September 2006. |
| 435 |
|
| 436 |
[<a id="ref-UTF-8">UTF-8</a>] Yergeau, F., "UTF-8, a transformation format of ISO |
| 437 |
10646", STD 63, <a href="./rfc3629">RFC 3629</a>, November 2003. |
| 438 |
|
| 439 |
[<a id="ref-Unicode">Unicode</a>] "The Unicode Standard 5.0", Unicode 5.0, 2007, |
| 440 |
<<a href="http://www.unicode.org/versions/Unicode5.0.0/">http://www.unicode.org/versions/Unicode5.0.0/</a>>. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Melnikov & King Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc5466">RFC 5466</a> IMAP Filters February 2009</span> |
| 447 |
|
| 448 |
|
| 449 |
Authors' Addresses |
| 450 |
|
| 451 |
Alexey Melnikov |
| 452 |
Isode Ltd |
| 453 |
5 Castle Business Village |
| 454 |
36 Station Road |
| 455 |
Hampton, Middlesex TW12 2BX |
| 456 |
UK |
| 457 |
|
| 458 |
EMail: [email protected] |
| 459 |
|
| 460 |
|
| 461 |
Curtis King |
| 462 |
Isode Ltd |
| 463 |
5 Castle Business Village |
| 464 |
36 Station Road |
| 465 |
Hampton, Middlesex TW12 2BX |
| 466 |
UK |
| 467 |
|
| 468 |
EMail: [email protected] |
| 469 |
|
| 470 |
|
| 471 |
|
| 472 |
|
| 473 |
|
| 474 |
|
| 475 |
|
| 476 |
|
| 477 |
|
| 478 |
|
| 479 |
|
| 480 |
|
| 481 |
|
| 482 |
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 |
|
| 487 |
|
| 488 |
|
| 489 |
|
| 490 |
|
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
Melnikov & King Standards Track [Page 9] |
| 501 |
</pre> |