Re: draft-melnikov-imap-search-res

[Alexey Melnikov <[e-mail]>]

Mark Crispin wrote:

> The problem is when the search result is long and sparse, meaning that 
> it can not be collapsed easily with range syntax.  With large enough 
> mailboxes, the result is a command which is larger than the maximum 
> command length, and thus the command needs to be broken up into 
> multiple commands (which in turn creates its own problems).

One thing I wanted to do but hasn't: add a SEARCH option to "suppress" 
untagged SEARCH responses. Something like

a SEARCH 1:10,20:30,47 (NORESULT)

I am not sure whether this should be a part of the SEARCHRES extension, 
or a more generic extension for SEARCH options. The latter might include 
other options like COUNT (return how many were found), MIN (minimal 
found message number/UID) & MAX.

Alexey