Re: [sieve] redirect-dsn, redirect-deliverby

NED+mta-filters@mauve.mrochek.com Sun, 15 April 2018 16:45 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 44525126BF6 for <sieve@ietfa.amsl.com>; Sun, 15 Apr 2018 09:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 JXexjfR59f2K for <sieve@ietfa.amsl.com>; Sun, 15 Apr 2018 09:45:26 -0700 (PDT)
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 AE74C124BE8 for <sieve@ietf.org>; Sun, 15 Apr 2018 09:45:26 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01QRD5J97U7400JAHA@mauve.mrochek.com> for sieve@ietf.org; Sun, 15 Apr 2018 09:40:18 -0700 (PDT)
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 <01QR4MYJ0NQO000051@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for sieve@ietf.org; Sun, 15 Apr 2018 09:40:12 -0700 (PDT)
From: NED+mta-filters@mauve.mrochek.com
Cc: sieve@ietf.org
Message-id: <01QRD5J5YQJA000051@mauve.mrochek.com>
Date: Sun, 15 Apr 2018 09:35:21 -0700 (PDT)
In-reply-to: "Your message dated Tue, 10 Apr 2018 12:52:36 -0400" <943ce364-2965-72fc-7e27-b2e4daff67cf@fastmail.com>
References: <943ce364-2965-72fc-7e27-b2e4daff67cf@fastmail.com>
To: Ken Murchison <murch@fastmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sieve/CdXTYKe15_QXzOGQhRqWq9MSaTw>
Subject: Re: [sieve] redirect-dsn, redirect-deliverby
X-BeenThere: sieve@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 15 Apr 2018 16:45:28 -0000

> So, I'm implementing RFC 6009 and I'm wondering why the values of
> :bymode are specified as lowercase and those for :ret are uppercase.

Sieve parameters like this are case-insensitive - this follows from the fact
that they are defined using ABNF strings which are always case-insensitive - so
who cares what case they are shown in?

> And why was :notify specified as a single string with comma-separated
> values rather than a stringlist?

I don't really remember, but it's probably to be more compatible with
the SMTP parameter.

				Ned