IETF Logo Mail Archive

Re: [Jmap] I-D Action: draft-ietf-jmap-sieve-02.txt

Ned Freed <ned.freed@mrochek.com> Thu, 19 November 2020 15:02 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73ACE3A0989 for <jmap@ietfa.amsl.com>; Thu, 19 Nov 2020 07:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.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 nrFgz3hhS-TK for <jmap@ietfa.amsl.com>; Thu, 19 Nov 2020 07:02:54 -0800 (PST)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (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 784883A09A4 for <jmap@ietf.org>; Thu, 19 Nov 2020 07:02:54 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RS6QFMDAPS009FEM@mauve.mrochek.com> for jmap@ietf.org; Thu, 19 Nov 2020 06:57:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712; t=1605797871; bh=W+YTH8xd5GePrASSARaUjLmRKvyQOGFY78Rfp22aNgE=; h=Cc:Date:From:Subject:In-reply-to:References:To:From; b=DnpEQ0+MQDvmjHw4cbBcyZqYGGOzI9m+yDYJNRho59CyQuMxygymqQ00i1tVjgIyS 7LI1mFoLJPWcMhZdXL3s4/3l37k0ro3/xnhM6suE81s2BsJp+eT/Pts1t/lxPdg/3M 6av8hV0UwNaqmmAbfe3fmykpSqXzrUcjKt2Fd5vY=
MIME-version: 1.0
Content-transfer-encoding: 8bit
Content-type: TEXT/PLAIN; charset="utf-8"; Format="flowed"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RS6Q9IGBAO0085YQ@mauve.mrochek.com>; Thu, 19 Nov 2020 06:57:49 -0800 (PST)
Cc: jmap@ietf.org
Message-id: <01RS6QFKSX1U0085YQ@mauve.mrochek.com>
Date: Thu, 19 Nov 2020 06:54:42 -0800
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Thu, 19 Nov 2020 09:26:37 -0500" <a044b1cb-97e0-a9da-4d6b-084f817d0c20@fastmail.com>
References: <160431690732.22434.10293492942158194310@ietfa.amsl.com> <36838c43-aefb-c7f9-d973-2e6f8df5e78f@open-xchange.com> <01RS6NIC0KZC005PTU@mauve.mrochek.com> <a044b1cb-97e0-a9da-4d6b-084f817d0c20@fastmail.com>
To: Ken Murchison <murch@fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/7gTMTObA2urnnfpx87h8vx6X3uY>
Subject: Re: [Jmap] I-D Action: draft-ietf-jmap-sieve-02.txt
X-BeenThere: jmap@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: JSON Message Access Protocol <jmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/jmap>, <mailto:jmap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap/>
List-Post: <mailto:jmap@ietf.org>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/jmap>, <mailto:jmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Nov 2020 15:02:55 -0000

> Don't we have the same single-script/multi-script client issue with
> managesieve?

Yes. That's kind of the point.

> Or perhaps I'm not fully understanding your concern.

> A separate question that comes to mind, is do we want JMAP Sieve servers
> to be able to only support a single script?  I guess in this case, the
> server could simply have a single script with id "singleton" which can
> only be updated and (de)activated.  Any attempt to create another script
> or destroy the existing one would fail with a "singleton" error.

Indeed. It seems like we're asking a lot of clients here. And if the past is
any indication, we're likely to be disappointed by what we get.

				Ned

v2.23.0 | Report a Bug | By Email