IETF Logo Mail Archive

[imapext] SEARCHRES RFC5182

Adrien de Croy <adrien@qbik.com> Tue, 09 March 2021 23:21 UTC

Return-Path: <adrien@qbik.com>
X-Original-To: imapext@ietfa.amsl.com
Delivered-To: imapext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2F5A3A0ED1 for <imapext@ietfa.amsl.com>; Tue, 9 Mar 2021 15:21:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, SUBJ_ALL_CAPS=0.5] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OJ-1se5T4900 for <imapext@ietfa.amsl.com>; Tue, 9 Mar 2021 15:21:35 -0800 (PST)
Received: from smtp.qbik.com (smtp.qbik.com [122.56.26.1]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4055A3A1115 for <imapext@ietf.org>; Tue, 9 Mar 2021 15:21:34 -0800 (PST)
Received: From [192.168.1.162] (unverified [192.168.1.162]) by SMTP Server [192.168.1.3] (WinGate SMTP Receiver v9.4.2 (Build 6000)) with SMTP id <0002429640@smtp.qbik.com>; Wed, 10 Mar 2021 12:21:30 +1300
From: Adrien de Croy <adrien@qbik.com>
To: "imapext@ietf.org" <imapext@ietf.org>
Date: Tue, 09 Mar 2021 23:21:32 +0000
Message-Id: <em68d5d29d-695c-4b42-be1c-4d99ee6bcf08@bombadil>
In-Reply-To: <3089d87b-5884-44bf-8eb9-ef5d34f16756@spark>
References: <CAO0d3bLXzYynT-9BxDy2DS4nHGzVM2hBTAQyyy2nhu-s1FmsNg@mail.gmail.com> <CAO0d3bJ_ma7R+0Xti0sO8fEL9g1qJWfs8F25O7GODT2r4eEzaQ@mail.gmail.com> <f53b4661-1d6c-4243-b76d-169ba1a33017@gulbrandsen.priv.no> <40f8d9ec-2387-4e38-819d-fdb4407c5709@spark> <e90008f2-fde5-4596-a1a9-4dc6d8ea9753@gulbrandsen.priv.no> <3089d87b-5884-44bf-8eb9-ef5d34f16756@spark>
Reply-To: Adrien de Croy <adrien@qbik.com>
User-Agent: eM_Client/8.1.1054.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MB38B368CF-6111-4487-B9F4-7BC34898F36B"
Archived-At: <https://mailarchive.ietf.org/arch/msg/imapext/Y7PSaSYUzeKLj-yCf4I7Su09VAI>
Subject: [imapext] SEARCHRES RFC5182
X-BeenThere: imapext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IMAP extensions <imapext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imapext>, <mailto:imapext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/imapext/>
List-Post: <mailto:imapext@ietf.org>
List-Help: <mailto:imapext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imapext>, <mailto:imapext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Mar 2021 23:21:37 -0000

Hi Everyone

I've been looking into this extension, but it has a number of problems 
and uncertainties in the spec especially:

* in relation to storing results of ESEARCH extensions, it refers to 
them as messages).
* in relation to reporting errors if the saved results are incompatible 
(e.g. stored SEQ but asked to use as UID or vice versa)
* dealing with expunging of messages.

So my first question relates to whether I'm even wasting my time.  The 
imapwiki shows very few servers support it, but are any clients known to 
support it?

Regards

Adrien

v2.23.0 | Report a Bug | By Email