unexpected list configuration change?

unexpected list configuration change?

[Jan Beulich]

(re-sending to this address, as per Andreas Schwab's suggestion)

Hello,

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.

Thanks for any insight,
Jan

Re: unexpected list configuration change?

[Mark Wielaard]

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=29713#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=general/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