Re: [Tools-discuss] Interesting mailman side-effect?

Alice Russo <arusso@amsl.com> Fri, 27 May 2022 23:17 UTC

Return-Path: <arusso@amsl.com>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A095AC14F724 for <tools-discuss@ietfa.amsl.com>; Fri, 27 May 2022 16:17:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5RIh9YVfEbXT for <tools-discuss@ietfa.amsl.com>; Fri, 27 May 2022 16:17:03 -0700 (PDT)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8822AC14F608 for <tools-discuss@ietf.org>; Fri, 27 May 2022 16:17:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6F361427C641; Fri, 27 May 2022 16:17:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZxR_ZmZD1-WZ; Fri, 27 May 2022 16:17:03 -0700 (PDT)
Received: from [192.168.1.10] (unknown [104.245.133.1]) by c8a.amsl.com (Postfix) with ESMTPSA id 1EA29427C640; Fri, 27 May 2022 16:17:03 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Alice Russo <arusso@amsl.com>
In-Reply-To: <24d88680-4af9-b9f1-d481-b9bc407170fb@gmail.com>
Date: Fri, 27 May 2022 16:17:02 -0700
Cc: Tools Team Discussion <tools-discuss@ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8407A241-8D23-4C6B-B4AF-E54E0ED60426@amsl.com>
References: <24d88680-4af9-b9f1-d481-b9bc407170fb@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/lLkFUc3xwTTz5YTsRCpFYjNVBHE>
Subject: Re: [Tools-discuss] Interesting mailman side-effect?
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 May 2022 23:17:05 -0000

Hi Brian,
I've read through your mail regarding an RFC errata notification mail CC'ed to the ipv6 mailing list.

Re:
> Is there some weird coupling between the errata processing and mailman?

Not that we know of. Errata notification mails are sent from rfc-editor@rfc-editor.org and the WG mailing list is CC'ed (when relevant). 

We have not received reports of a similar issue with other errata notification mails. Please let us know if this recurs.

Thanks,

Alice Russo
RFC Production Center


> On May 11, 2022, at 10:37 PM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> 
> Hi,
> 
> The other day I submitted an erratum via the RFC Edior site and noticed that I never received a copy of the resulting email sent (among other places) to the corresponding WG. I checked, of course, that it hadn't been spam-filtered or otherwise deleted.
> 
> In my mailman subscription to that WG, I have set the option to not receive copies of my own messages to the list, and the "no duplicates" option. I do that on all lists to avoid clutter. But the message in question says:
> 
> From: RFC Errata System <rfc-editor@rfc-editor.org>
> Cc: brian.e.carpenter@gmail.com, ipv6@ietf.org, rfc-editor@rfc-editor.org
> 
> The message in question is
> Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/O3wuw-Nsdgwb2_t0OMEnPtBTkeU>
> 
> I can understand why mailman decided not to send it to me ("no duplicates"), but I do not understand why the Cc: failed when the message was originated. Is there some weird coupling between the errata processing and mailman?
> 
> By the way, the first response to the message
> Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/XmEOTuQz75Ss0Xhi0wQ6XG6bl4g>
> indicates that the copies sent out by mailman did *not* contain the Cc: to me.
> 
> (FWIW, I submitted an erratum about 3 years ago, and I did receive my copy, and that time it was for a WG that I was not subscribed to.)
> 
> Any thoughts?
> 
> Thanks
>   Brian
> 
> 
> ___________________________________________________________
> Tools-discuss mailing list - Tools-discuss@ietf.org
> This list is for discussion, not for action requests or bug reports.
> * Report datatracker and mailarchive bugs to: datatracker-project@ietf.org
> * Report tools.ietf.org bugs to: webmaster@tools.ietf.org
> * Report all other bugs or issues to: ietf-action@ietf.org
> List info (including how to Unsubscribe): https://www.ietf.org/mailman/listinfo/tools-discuss
>