Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt
Aaron Stone <aaron@serendipity.cx> Thu, 13 September 2012 20:31 UTC
Return-Path: <aaron@serendipity.cx>
X-Original-To: sieve@ietfa.amsl.com
Delivered-To: sieve@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595E721F84F6 for <sieve@ietfa.amsl.com>; Thu, 13 Sep 2012 13:31:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.343
X-Spam-Level:
X-Spam-Status: No, score=-101.343 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_45=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JvXOYGO2Y+29 for <sieve@ietfa.amsl.com>; Thu, 13 Sep 2012 13:31:42 -0700 (PDT)
Received: from slice.serendipity.cx (slice.serendipity.cx [67.23.2.90]) by ietfa.amsl.com (Postfix) with ESMTP id EF29E21F84D1 for <sieve@ietf.org>; Thu, 13 Sep 2012 13:31:38 -0700 (PDT)
Received: from mail-pz0-f44.google.com (mail-pz0-f44.google.com [209.85.210.44]) by slice.serendipity.cx (Postfix) with ESMTPSA id 7977F94004 for <sieve@ietf.org>; Thu, 13 Sep 2012 13:27:58 -0700 (PDT)
Received: by dadf8 with SMTP id f8so1950054dad.31 for <sieve@ietf.org>; Thu, 13 Sep 2012 13:31:23 -0700 (PDT)
Received: by 10.68.200.8 with SMTP id jo8mr988749pbc.148.1347568283698; Thu, 13 Sep 2012 13:31:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.66.14.100 with HTTP; Thu, 13 Sep 2012 13:31:03 -0700 (PDT)
In-Reply-To: <CAC4RtVApjXKJbwCLBPryh1YeJ-BgWxOKNHAzo56HR4Lhc4O=gg@mail.gmail.com>
References: <20120910211613.16818.36778.idtracker@ietfa.amsl.com> <504EFB8F.7000806@rename-it.nl> <CAC4RtVApjXKJbwCLBPryh1YeJ-BgWxOKNHAzo56HR4Lhc4O=gg@mail.gmail.com>
From: Aaron Stone <aaron@serendipity.cx>
Date: Thu, 13 Sep 2012 13:31:03 -0700
Message-ID: <CAEdAYKXGrxzxM8bpVqVJBU=S4z0MWLBZQXH6G7eX4Ui_-2HpcQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: sieve@ietf.org
Subject: Re: [sieve] I-D Action: draft-ietf-sieve-imap-sieve-08.txt
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sieve>, <mailto:sieve-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sieve>
List-Post: <mailto:sieve@ietf.org>
List-Help: <mailto:sieve-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sieve>, <mailto:sieve-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Sep 2012 20:31:43 -0000
On Thu, Sep 13, 2012 at 12:05 PM, Barry Leiba <barryleiba@computer.org> wrote: > Oy. > These comments are VERY late, and the document has already gone > through IESG approval. I'll look at them and see what I think we can > address now. > > I also have a question for the working group: > In his IESG evaluation review, Robert Sparks has this comment: > > << The environment names live in a global space - other extensions might want to > put a cause into the environment. Would it be worth the pain to scope the name > _this_ extension is adding to this extension ("imapcause" or something like > that)? >> > > I think that's a reasonable change, and will change "cause" to > "imapcause", unless there's objection from the WG (and one or two > "That sounds fine." comments would be good). I don't think we're going to impact any existing implementations with this change, so it sounds fine to me. > On Tue, Sep 11, 2012 at 4:51 AM, Stephan Bosch <stephan@rename-it.nl> wrote: >> There is no changelog in the document, so I wondered what changed > > That's why &deity made diffs. When you go to the tools page: > http://tools.ietf.org/html/draft-ietf-sieve-imap-sieve > ...you can click on "Diff1" if you like strike-out diffs or "Diff2" if > you like side-by-side diffs. Tools are your friends. > >> #1) The final paragraph of Section 2.1 lists a few IMAP and Sieve >> capabilities for which support is required: IMAP "METADATA" and Sieve >> "environment". I would expect this Section to list all such dependencies, >> but apparently it does not. Section 3.8 adds the Sieve imap4flags extension >> as a requirement. Yet, section 4.5 suggests that it is optional again. So >> what is it? > > We made imap4flags required at a fairly late date, and I didn't get > everything changed consistently. I've fixed that for -09; thanks. > >> #2) Section 2.2.2 suggests that there is a MULTIAPPEND command for IMAP. >> There is no such thing: it is an IMAP capability that extends APPEND to >> accept multiple messages at once. I would merge this with the previous >> section: > > I have added this second paragraph to 2.2.1, eliminated 2.2.2, and > eliminated the other references to a MULTIAPPEND command: > > If the IMAP server also supports the IMAP MultiAppend extension > <xref target="RFC3502"/>, the APPEND command can create more > than one message at a time. > In that case, each message creation is considered a separate > event, and any applicable Sieve script is called once for each > message. > >> I also gave the issue of useless script triggers, i.e. events that are never >> of interest for the script involved, some more thought. For example, I would >> hate to have my Sieve script executed for each message that I read (added >> \Seen flag) while it doesn't do anything useful with that event. Wouldn't it >> be useful to have a `/shared/imapsieve/cause' Metadata item that indicates >> which causes (the items from Section 7.3.1 in a space-separated list) should >> trigger the Sieve script? More detailed control could be used to select >> specific flags that are relevant (e.g. in a '/share/imapsieve/changedflags' >> Metatada item). > > It might, and we considered this, but rejected the complexity. I > don't think this is the time to reconsider it. > > Barry > _______________________________________________ > sieve mailing list > sieve@ietf.org > https://www.ietf.org/mailman/listinfo/sieve
- [sieve] I-D Action: draft-ietf-sieve-imap-sieve-0… internet-drafts
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Stephan Bosch
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Barry Leiba
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Stephan Bosch
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Barry Leiba
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Aaron Stone
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… NED+mta-filters
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… NED+mta-filters
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Stephan Bosch
- Re: [sieve] I-D Action: draft-ietf-sieve-imap-sie… Barry Leiba