IETF Logo Mail Archive

Re: [sieve] Notify (RFC 5435) questions

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 01 October 2009 21:22 UTC

Return-Path: <lunohod.baikonur@googlemail.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 8D9163A67EF for <sieve@core3.amsl.com>; Thu, 1 Oct 2009 14:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.87
X-Spam-Level:
X-Spam-Status: No, score=-1.87 tagged_above=-999 required=5 tests=[AWL=0.107, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
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 jsiuTtkE6mq7 for <sieve@core3.amsl.com>; Thu, 1 Oct 2009 14:22:19 -0700 (PDT)
Received: from mail-qy0-f191.google.com (mail-qy0-f191.google.com [209.85.221.191]) by core3.amsl.com (Postfix) with ESMTP id 75BBD3A67B3 for <sieve@ietf.org>; Thu, 1 Oct 2009 14:22:19 -0700 (PDT)
Received: by qyk29 with SMTP id 29so470112qyk.32 for <sieve@ietf.org>; Thu, 01 Oct 2009 14:23:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=sPFJwR0WyGvrWHMm00Y2pLu0xooDfFqGlIbhWRH7rp8=; b=SaiQx3W9EV51BAPdDSOpxhnz2gD3+iOpNuoRTAuEcFo7IzJqowLUEJQhmAUjKkomBc 4l2J3zWGlCLNFt5p+hJ58VC6nzpVLxmL/XQAgA2UgRwNhYLi8FufNBuWls1WZjge2F0a Vrht/aE1K6tvBQfbjYnrYEozmTOQpec31PgQk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=VtwxTD8cOiQEl3SL4JsmXAiVhxh8j5ZlP4sLPalJBwofJdyFOja33Pp9oYIlBiGcVy j0uJAm8Fwlx0vUq4OXar0pkl8uAWudX1/fE7jJa2M/SNdGWUUZPyUIHQ3S5eWP8W/eSY Qz/YYRe3m238HcLTOsS3wLSbM5TrYQHRyOUEE=
MIME-Version: 1.0
Sender: lunohod.baikonur@googlemail.com
Received: by 10.229.78.162 with SMTP id l34mr1579804qck.96.1254432225256; Thu, 01 Oct 2009 14:23:45 -0700 (PDT)
In-Reply-To: <6c9fcc2a0909282155lad81ccfvae10a5462dbfe258@mail.gmail.com>
References: <20090928143651.GB31810@schlund.de> <6c9fcc2a0909281032g16368fdco2c94185e619380ce@mail.gmail.com> <01NE9GPFVRXE00B359@mauve.mrochek.com> <6c9fcc2a0909282155lad81ccfvae10a5462dbfe258@mail.gmail.com>
Date: Thu, 01 Oct 2009 22:23:45 +0100
X-Google-Sender-Auth: 04e8f35377507eb0
Message-ID: <29d3c4cb0910011423s3eb0f4a5q159edf4b73404815@mail.gmail.com>
From: Alexey Melnikov <alexey.melnikov@isode.com>
To: barryleiba@computer.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: sieve@ietf.org, Ned Freed <ned.freed@mrochek.com>
Subject: Re: [sieve] Notify (RFC 5435) questions
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: Thu, 01 Oct 2009 21:22:20 -0000

On Tue, Sep 29, 2009 at 8:55 AM, Barry Leiba
<barryleiba.mailing.lists@gmail.com> wrote:
 [...]
> I agree that it'd be better to put it into the variables spec.  You
> know I'm not suggesting going through everything to say where you can
> and can't do variable substitution; you should know me better than
> that.  But Hannah has a point: the variables spec says this:
>
>   This extension changes the semantics of quoted-string, multi-line-
>   literal and multi-line-dotstuff found in [SIEVE] to enable the
>   inclusion of the value of variables.
>
> ...and the grammar for "importance" uses none of those three syntax
> constructions.  Taken at its word, that would imply that variable
> substitution doesn't apply here.

I am fine with this being reported as an Erratum. Do you want to do that?

> We might change RFC 5229 to add that
> variables can substitute for literal strings as well.  Or we might
> decide that it's clear enough, and doesn't need changing.

v2.46.0 | Report a Bug | By Email | System Status