Re: [sieve] Working Group Last Call: draft-ietf-sieve... autoreply, notify-presence, vacation-seconds

NED+mta-filters@mauve.mrochek.com Wed, 13 October 2010 00:24 UTC

Return-Path: <NED+mta-filters@mauve.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 E2EB53A686E for <sieve@core3.amsl.com>; Tue, 12 Oct 2010 17:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.27
X-Spam-Level:
X-Spam-Status: No, score=-2.27 tagged_above=-999 required=5 tests=[AWL=0.329, BAYES_00=-2.599]
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 N01rkcdqetJn for <sieve@core3.amsl.com>; Tue, 12 Oct 2010 17:24:08 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id AEA653A6832 for <sieve@ietf.org>; Tue, 12 Oct 2010 17:24:08 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NSZ2PULG1C007K8B@mauve.mrochek.com> for sieve@ietf.org; Tue, 12 Oct 2010 17:25:22 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01NSI5YX1W0G000CVY@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Tue, 12 Oct 2010 17:25:20 -0700 (PDT)
From: NED+mta-filters@mauve.mrochek.com
Message-id: <01NSZ2PTFXCI000CVY@mauve.mrochek.com>
Date: Tue, 12 Oct 2010 17:23:07 -0700
In-reply-to: "Your message dated Tue, 12 Oct 2010 19:47:38 -0400" <4CB4F39A.8040806@att.com>
MIME-version: 1.0
Content-type: TEXT/PLAIN; Format="flowed"
References: <AANLkTik994DjP7T7tj-VzJQ4J1nAgtq4hTdj5ZFQ-h=u@mail.gmail.com> <4CB4F39A.8040806@att.com>
To: Tony Hansen <tony@att.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1286927569; i=@mrochek.com; bh=rrue9VXzlLuYe3FphSzartMSK/XUoT7xNC+u16wtfLw=; h=From:Cc:Message-id:Date:Subject:In-reply-to:MIME-version: Content-type:References:To; b=Et0WtZbgEnJxBrRY2w8YkqnQiiEyesiNtWnYuwRA9YpUmi78apOyBd27VG8ZxWe4c Upl6hJwMK7eTk1Bjr1hX1lrcTLcp4PQD0a0Hv3TE7XdkudyQu19I25WO3Z1t/JObGU zGEj3VarNjCVere1hQx4rZ4J9LYwAwZKzQPqN93Y=
Cc: Sieve mailing list <sieve@ietf.org>
Subject: Re: [sieve] Working Group Last Call: draft-ietf-sieve... autoreply, notify-presence, vacation-seconds
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: Wed, 13 Oct 2010 00:24:10 -0000

> =======
> notify-presence

> The value of "unknown" should be explicity listed in section 2 for each
> item that can return that value, rather than being mentioned in passing
> at the end of section 2.

> I think it would be worth putting a note in somewhere that an
> implementation may wish to cache the results of a call to
> notify_method_capability so that if it is used in a series of if/else
> tests, it only needs to be retrieved once.

Now that you bring this up, I'm tempted to go even further, and say that any
result should be consistent throughout the script. If statuses change and
notify_method_capability returns inconsistent results at different times in the
same script, I could see that causing some unpleasant results.

I did something similar in the date extension - currentdate is required to
use a single, consistent value throughout the script.

				Ned