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