IETF Logo Mail Archive

Re: [sieve] [Technical Errata Reported] RFC5229 (5015)

Stan Kalisch <stan@glyphein.mailforce.net> Mon, 05 June 2017 10:42 UTC

Return-Path: <stan@glyphein.mailforce.net>
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 471901250B8 for <sieve@ietfa.amsl.com>; Mon, 5 Jun 2017 03:42:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level:
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mailforce.net header.b=VBZuyoq4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Tf3wgQSN
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 cJgOAd8aGFPr for <sieve@ietfa.amsl.com>; Mon, 5 Jun 2017 03:42:13 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93185120724 for <sieve@ietf.org>; Mon, 5 Jun 2017 03:42:13 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 8912A20B65; Mon, 5 Jun 2017 06:42:10 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Mon, 05 Jun 2017 06:42:10 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mailforce.net; h=cc:content-transfer-encoding:content-type:date:from :in-reply-to:message-id:mime-version:references:subject:to :x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=CT3ssF M09ugnuuFVGzWTPFHWhvzyCtU4lnzLusgB4Ok=; b=VBZuyoq4jXsO0Ndg9R4ViE +o3KLD8Rh0DnSjp88f6d3frBB6NA7iuMCE3XgYojV+Me2AxeZq0DOs1vTm6BgQg8 TTNwYata5O2WmAvl8Vl529ssPdM237FQxXxcMuydf3aq8dnx0vSzqy68LymYNtsd NmlJS2TZHm6cvjNNTs4WOt5PK7WGfxBdZxmG/eNb5TEnI8j0VtOoqjppcMAm5Bji 2QXc7eoMeRSLQVCyuwplk7ptad+rAxmDUiJeW3kBCZf1ToZoxf6C2RVMrwKPZvpe y6E2QiwsOpOqZFbckq0w8HWM3GnB7GOdb5JXCNhGgTSvjcO+/tvdcCgj2ty/pq5w ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=CT3ssFM09ugnuuFVGzWTPFHWhvzyCtU4lnzLusgB4Ok=; b=Tf3wgQSN WG00mjZFnnYKOGQe+Ti+0gIzYtpw1sFrE5uB7hJ96j3z/TE7+sTSEGX/R6SdMiuw FD5kB0WMeNMa8QpDSum1973Ielx2H7K2xe78xHO/X+vYXmgkZTYStvasUmhCuVNY voyIrukdWv0z1lmW8cLo9fK3T0M/aKeJxwsIrZTiViDLMvrHVBN2CXXXfS8jbAKk XbNKbUoRF27gmgfwOYloPnpDVuXxuUBiVZug9c3DjUfVFnHIu4XPrWR5sJfbyKlL ffOAL4G5vhHEez6P+GiI8dOYyaGX47XhyxF1X9G20kPs75MCEyg4nc4Nx5PESck5 pzbIrySZFpW68A==
X-ME-Sender: <xms:gjU1WVmWZXy0PkJezeygJ06RfmawLuJ-fFEw1SFrgncRsgVgwU7R2w>
X-Sasl-enc: LCb4o550E8RW1+gqo/sYLx4gHwiAG2nXmLIZpFRAnf0K 1496659330
Received: from [10.251.88.159] (29.sub-97-45-70.myvzw.com [97.45.70.29]) by mail.messagingengine.com (Postfix) with ESMTPA id 1690F7E850; Mon, 5 Jun 2017 06:42:10 -0400 (EDT)
References: <20170511000521.5100EB812F9@rfc-editor.org> <1494489592.5978.3.camel@ifi.uio.no>
Mime-Version: 1.0 (1.0)
In-Reply-To: <1494489592.5978.3.camel@ifi.uio.no>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <631D2029-41E8-4392-933A-B495558645CA@glyphein.mailforce.net>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, ben@nostrum.com, alissa@cooperw.in, aamelnikov@fastmail.fm, cyrus@daboo.name, aaron@serendipity.cx, sieve@ietf.org
X-Mailer: iPhone Mail (13B143)
From: Stan Kalisch <stan@glyphein.mailforce.net>
Date: Mon, 05 Jun 2017 06:42:07 -0400
To: Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
Archived-At: <https://mailarchive.ietf.org/arch/msg/sieve/_SveNvUMSknBFms3GB-bGzUV9vs>
Subject: Re: [sieve] [Technical Errata Reported] RFC5229 (5015)
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: Mon, 05 Jun 2017 10:42:15 -0000

Apologies for the lateness of this reply.

> On May 11, 2017, at 3:59 AM, Kjetil Torgrim Homme <kjetilho@ifi.uio.no> wrote:
> 
> on. den 10. 05. 2017 klokka 17.05 (-0700) skreiv RFC Errata System:
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata/eid5015
>> 
>> --------------------------------------
>> Type: Technical
>> Reported by: Stan Kalisch <stan@glyphein.mailforce.net>
>> 
>> Section: 3.2
>> 
>> Original Text
>> -------------
>> # Imagine the header
>>      # Subject: [acme-users] [fwd] version 1.0 is out
>>      if header :matches "Subject" "[*] *" {
>>          #  will hold "acme-users",
>>          #  will hold "[fwd] version 1.0 is out"
>>          fileinfo "INBOX.lists."; stop;
>>      }
>> 
>> Corrected Text
>> --------------
>> # Imagine the header
>>      # Subject: [acme-users] [fwd] version 1.0 is out
>>      if header :matches "Subject" "[*] *" {
>>          #  will hold "acme-users",
>>          #  will hold "[fwd] version 1.0 is out"
>>          fileinto "INBOX.lists."; stop;
>>      }
>> 
>> Notes
>> -----
>> This suggestion corrects the spelling of the "fileinto" action in the example.
> 
> mea culpa!  the fix is correct.
> 
> aside: it is interesting that the mail copy of this notification has
> removed the "${1}" and "${2}" from the text.  it is correct in the web
> version.

I noticed the omissions still existed in the emailed notification of the verification of the errata.  Does anyone know if the cause of this has been fixed?


Stan

v2.23.0 | Report a Bug | By Email