Re: [sieve] [draft-melnikov-sieve-external-lists] 2.2 Allow Extensions To Use List

Ned Freed <ned.freed@mrochek.com> Sun, 30 August 2009 17:23 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: sieve@core3.amsl.com
Delivered-To: sieve@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5A14E3A6B63 for <sieve@core3.amsl.com>; Sun, 30 Aug 2009 10:23:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.225
X-Spam-Level:
X-Spam-Status: No, score=-4.225 tagged_above=-999 required=5 tests=[AWL=1.821, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YjmrXJPYronA for <sieve@core3.amsl.com>; Sun, 30 Aug 2009 10:23:17 -0700 (PDT)
Received: from balder-227.proper.com (Balder-227.Proper.COM [192.245.12.227]) by core3.amsl.com (Postfix) with ESMTP id 9E8823A6AF4 for <sieve@ietf.org>; Sun, 30 Aug 2009 10:23:13 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n7UHNMQ9034322 for <ietf-mta-filters@imc.org>; Sun, 30 Aug 2009 10:23:22 -0700 (MST) (envelope-from ned.freed@mrochek.com)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01ND4P2ND84G005E4M@mauve.mrochek.com> for ietf-mta-filters@imc.org; Sun, 30 Aug 2009 10:23:18 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01ND3SUIAR4G001ML6@mauve.mrochek.com>; Sun, 30 Aug 2009 10:23:13 -0700 (PDT)
Date: Sun, 30 Aug 2009 10:21:30 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sun, 30 Aug 2009 16:33:17 +0100" <4A9A9BBD.20003@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
Message-id: <01ND4P2KMBSS001ML6@mauve.mrochek.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; format="flowed"
Content-transfer-encoding: 7bit
References: <f470f68e0907300524w6116f6aet4ce9b95546486862@mail.gmail.com> <01NBX999C2K200007A@mauve.mrochek.com> <4A9A9BBD.20003@isode.com>
Cc: MTA filtering mailing list <ietf-mta-filters@imc.org>, Ned Freed <ned.freed@mrochek.com>
Subject: Re: [sieve] [draft-melnikov-sieve-external-lists] 2.2 Allow Extensions To Use List
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIEVE Working Group <sieve.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 30 Aug 2009 17:23:18 -0000

> Ned Freed wrote:

> >This proposal seems OK to me.
> >
> Ok, I've included this into my working copy.
> Should the "string" test be required as well?
>  [...]

Yes, I think if both variables and external lists are supported, the string
test must allow :list.

> >>--------------------------------------------------------------------------
> >>[1] Proposal
> >>--------------------------------------------------------------------------
> >>
> >>
> >>2.2.  :list match type
> >>
> >>
> >>   ABNF:
> >>
> >>
> >>      MATCH-TYPE  =/ ":list"
> >>           ; only valid for supported tests
> >>
> >>
> >>   The new ":list" match type changes the interpretation of the "key-
> >>   list" parameter to supported tests.  When the match type is ":list",
> >>   the key-list becomes a list of names of externally stored lists.
> >>   The external lists are queried, perhaps through a list-specific
> >>   mechanism, and the test evaluates to "true" if any of the specified
> >>   values matches any member of one or more of the lists.
> >>
> >>
> >>   Implementations MUST support "address", "envelope" and "header" tests.
> >>   Implementations MAY support other tests but MUST raise a compile
> >>   time error when a script contains any standard test where support has
> >>   not been explicitly specified.

I'm not comfortable with this being required to be compile time error. Think
for a minute about the interaction with the ihave extension.

				Ned