Re: [Extra] imap4rev2: STATUS DELETED

Michael Slusarz <michael.slusarz@open-xchange.com> Wed, 21 November 2018 18:24 UTC

Return-Path: <michael.slusarz@open-xchange.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A40E3130F3F for <extra@ietfa.amsl.com>; Wed, 21 Nov 2018 10:24:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=open-xchange.com
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 NIfOVU8eCAuP for <extra@ietfa.amsl.com>; Wed, 21 Nov 2018 10:24:45 -0800 (PST)
Received: from mx4.open-xchange.com (alcatraz.open-xchange.com [87.191.39.187]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC298130E14 for <extra@ietf.org>; Wed, 21 Nov 2018 10:24:44 -0800 (PST)
Received: from open-xchange.com (imap.open-xchange.com [10.20.30.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx4.open-xchange.com (Postfix) with ESMTPS id 3F1A56A272 for <extra@ietf.org>; Wed, 21 Nov 2018 19:24:43 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=open-xchange.com; s=201705; t=1542824683; bh=neR9/m30psrdwbbGhFxMI8BCG5/QPmIc+s1UBSrmZQU=; h=Date:From:To:In-Reply-To:References:Subject:From; b=0efN18H0opyBXU57zN+bo87SZluBPYHyuvtYA012lPaf3rIwO/fYx4vD/MR86LS/O D48fMKnSg6KfKn5T0T1W8xUrudboZZnskAp1kxkyTY261ZFGKleZ5Dp/nO8vB3oF+w OE+C2GsycQ0Dk1XHsjpdoB3q7nVzNJ7oaG/NYmnk5zf/6oIa+TvgILh4HXa7qLtNMQ mip5tj2XI8TfKBgcTUvhw+Sr7l/Ti2n0k78O6tY5jDI9uW29kaIbjfLEobp7pVuBWV bmepNdCt2rJjJ0O9MVKFct+kSFDXrMqobM+xgaMobcd1I2AD5iMVojroNrUzakHRfM sZUkMVRIcoi8g==
Received: from appsuite-gw1.open-xchange.com (appsuite-gw1.open-xchange.com [10.20.28.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by open-xchange.com (Postfix) with ESMTPSA id 384C33C06FD for <extra@ietf.org>; Wed, 21 Nov 2018 19:24:43 +0100 (CET)
Date: Wed, 21 Nov 2018 11:24:42 -0700 (MST)
From: Michael Slusarz <michael.slusarz@open-xchange.com>
To: extra@ietf.org
Message-ID: <2090524145.9759.1542824683173@appsuite.open-xchange.com>
In-Reply-To: <50B39537-6D3D-47CF-B1FC-1B592C66F69B@oracle.com>
References: <8fcce54e-4d33-4f2b-92b2-0a5ec8bfec5b@sloti7d1t02> <50B39537-6D3D-47CF-B1FC-1B592C66F69B@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Priority: 3
Importance: Medium
X-Mailer: Open-Xchange Mailer v7.10.0-Rev20
X-Originating-Client: open-xchange-appsuite
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/j7Fq_5Y2eVmWx1JUZwhEu56zdPQ>
Subject: Re: [Extra] imap4rev2: STATUS DELETED
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Nov 2018 18:24:55 -0000

> On November 20, 2018 at 2:19 PM Chris Newman <chris.newman@oracle.com>; wrote:
> 
> 
> On 8 Nov 2018, at 3:30, Bron Gondwana wrote:
> > This is one of the open issues from imap4rev2 - which extensions 
> > should be part of the mandatory baseline.
> >
> > This was a discussion about a way to easily see if there are messages 
> > with \Deleted in a mailbox, maybe to see how much quota can be freed 
> > up. General agreement in the room was "IMAP4rev2 is for a baseline of 
> > existing standards, maybe this should be a new document, but not part 
> > of IMAP4rev2"
> >
> > Discussion on whether we think the general concept is useful, and 
> > whether it's so useful we should make it part of IMAP4rev2 in response 
> > to this please.
> 
> We've implemented a custom 'status counts' extension that provides 
> counts based on each configured message type including:
>   * total, seen, deleted, seen-deleted
> the intention of this extension was to help support voicemail and 
> similar unified messaging features. We implemented quota & quota-usage 
> by message type via a quota root naming convention.
> 
> I don't think we should delay IMAP4rev2 to include something like this, 
> but I can see it being helpful for some use cases.

Not much support from us on this.  We question its usefulness, as proposed.

Timo pointed out this somewhat related former proposal: https://tools.ietf.org/html/draft-neystadt-imap-status-counters-01

Maybe this makes sense if status checking is more extensible, and not limited to a single attribute?  But it also seems that this kind of solution is not something to cram into rev2 at this stage.

michael