Re: [sieve] Sieve :index and string/hasflag tests

NED+mta-filters@mauve.mrochek.com Thu, 26 January 2017 20:36 UTC

Return-Path: <NED+mta-filters@mauve.mrochek.com>
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 0065F129B13 for <sieve@ietfa.amsl.com>; Thu, 26 Jan 2017 12:36:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.202
X-Spam-Level:
X-Spam-Status: No, score=-3.202 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham 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 LhOpr-NA8ye1 for <sieve@ietfa.amsl.com>; Thu, 26 Jan 2017 12:36:19 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [68.183.62.69]) (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 257F1129AD6 for <sieve@ietf.org>; Thu, 26 Jan 2017 12:36:19 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QA524W1VPC003NEX@mauve.mrochek.com> for sieve@ietf.org; Thu, 26 Jan 2017 12:31:17 -0800 (PST)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii; Format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QA4UGNSGZK0003XB@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Thu, 26 Jan 2017 12:31:14 -0800 (PST)
From: NED+mta-filters@mauve.mrochek.com
Message-id: <01QA524UZB640003XB@mauve.mrochek.com>
Date: Thu, 26 Jan 2017 12:29:50 -0800 (PST)
In-reply-to: "Your message dated Tue, 24 Jan 2017 10:34:27 -0500" <cca72672-b9f3-31cf-75bf-d5a1c137a1cd@andrew.cmu.edu>
References: <cca72672-b9f3-31cf-75bf-d5a1c137a1cd@andrew.cmu.edu>
To: Ken Murchison <murch@andrew.cmu.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sieve/vZQq-FloT76o6rzT6NE3aivAqX4>
Cc: sieve@ietf.org
Subject: Re: [sieve] Sieve :index and string/hasflag tests
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 26 Jan 2017 20:36:20 -0000

> All,

> I just noticed that the :index extension has leaked into our grammar for
> the string and hasflag tests.  I can't think of any use case for this
> combination but wanted to check with the community before I rip it out.

I can't think of a meaning either and our implementation doesn't allow
:index to be combined with string or hasflag (although since we implement
ihave it's an evaluation time check).

				Ned