IETF Logo Mail Archive

Re: draft-melnikov-imap-search-res

Alexey Melnikov <Alexey.Melnikov@isode.com> Tue, 19 October 2004 16:18 UTC

Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9JGIYtC094784; Tue, 19 Oct 2004 09:18:34 -0700 (PDT) (envelope-from owner-ietf-imapext@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i9JGIYKs094783; Tue, 19 Oct 2004 09:18:34 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-imapext@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i9JGIXCk094777 for <ietf-imapext@imc.org>; Tue, 19 Oct 2004 09:18:33 -0700 (PDT) (envelope-from Alexey.Melnikov@isode.com)
Received: from [172.16.0.116] (shiny.isode.com [62.3.217.250]) by rufus.isode.com via TCP (internal) with ESMTPA; Tue, 19 Oct 2004 17:18:32 +0100
Message-ID: <41753E57.7020902@isode.com>
Date: Tue, 19 Oct 2004 17:18:31 +0100
From: Alexey Melnikov <Alexey.Melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
To: Mark Crispin <mrc@CAC.Washington.EDU>
CC: ietf-imapext@imc.org
Subject: Re: draft-melnikov-imap-search-res
References: <7yoPjUFDAsyLma6mHUEDow.md5@libertango.oryx.com> <4174F9C2.40304@isode.com> <Pine.LNX.4.62.0410190837000.19325@shiva0.cac.washington.edu> <4175371A.7030707@isode.com> <Pine.LNX.4.62.0410190903210.21925@shiva0.cac.washington.edu>
In-Reply-To: <Pine.LNX.4.62.0410190903210.21925@shiva0.cac.washington.edu>
MIME-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-transfer-encoding: 7bit
Sender: owner-ietf-imapext@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-imapext/mail-archive/>
List-ID: <ietf-imapext.imc.org>
List-Unsubscribe: <mailto:ietf-imapext-request@imc.org?body=unsubscribe>

Mark Crispin wrote:

> On Tue, 19 Oct 2004, Alexey Melnikov wrote:
>
>> One can also OR it, e.g.
>> a SEARCH <<,90:120
>
>
> Ugh!  This is something that few implementors will get right!
>
> I don't think that we should allow $ in sequences; $ should be a 
> complete sequence by itself.  If the client really wants an OR, it can do
>     tag SEARCH OR $ 90:120

That is fine with me.

v2.23.0 | Report a Bug | By Email