From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 8C6B13858C3A for ; Wed, 6 Sep 2023 09:41:35 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8C6B13858C3A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=klomp.org Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=klomp.org Received: from r6.localdomain (82-217-174-174.cable.dynamic.v4.ziggo.nl [82.217.174.174]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id DC3A43000716; Wed, 6 Sep 2023 11:41:33 +0200 (CEST) Received: by r6.localdomain (Postfix, from userid 1000) id C62743403B2; Wed, 6 Sep 2023 11:41:32 +0200 (CEST) Message-ID: <6139a36551fbec18edf62bf87e462dfda5c9b2ba.camel@klomp.org> Subject: Re: unexpected list configuration change? From: Mark Wielaard To: Jan Beulich via Overseers Cc: Jan Beulich Date: Wed, 06 Sep 2023 11:41:32 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 (3.48.4-1.fc38) MIME-Version: 1.0 X-Spam-Status: No, score=-3027.3 required=5.0 tests=BAYES_00,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,RCVD_IN_BARRACUDACENTRAL,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Jan, On Wed, 2023-09-06 at 10:34 +0200, Jan Beulich via Overseers wrote: > all of the sudden, when sending a 3-patch series just a few minutes ago, > I've observed all Cc: disappearing from mails sent to/through the list. > Quite some time ago I recall such happening for certain individuals, but > aiui at that time it was a per-user choice. Of course with just two > samples I can't exclude old behavior having been restored (and both of > the people Cc-ed having that (mis-)feature turned on), but even then I > would wonder why that was done. Stripping Cc-s makes replying more > difficult, when on the reply you want to have the same set of Cc-s as > was on the original mail. There was an upgrade of mailman and a tweak to CC dropping: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29713#c42 That should have had the opposite behaviour, keep the CCs. But the binutils list apparently sets it to Yes explicitly (or maybe that was caused by the mailman upgrade): https://sourceware.org/mailman/admin/binutils/?VARHELP=3Dgeneral/drop_cc "Should duplicate avoidance drop addresses from Cc: headers" YES I have explicitly set it to NO now. Hopefully that fixes things. Thanks for the report and please let us know if the above didn't fix the issue. Cheers, Mark