Dear Tom, In message <20200211135633.8b4d0240...@gemini.denx.de> I wrote: > > > I'm a little wary of changing the global setting for everyone as well. > > Perhaps we just need to note the problem happened for now and see if it > > really happens again in the future, such that we need to consider such a > > heavy-handed work-around. Thanks for looking into this more! > > We will continue to look into this a bit deeper; I will report back.
Running some more tests confirms that 1) mailman indeed removes entries from the Cc: address list, if these refer to subscribers _and_ these have the "nodupes" flag set; 2) unsetting the "nodupes" option makes the problem go away. The statement in [1] suggests that this is considered "intentional by design", though I cannot follow the argument that otherwise Cc: lists would grow in long threads. Apparently there are many different opinions, see for example [3]. The code snippet given in the original bug description [2] is still about the same in the version of mailman which we are running (v2.1.26) so it should be easy to remove the responsible "else" branch... So an easy work around for the problem is to clear the "nodupes" setting in your subscription - alternatively we can try and patch mailman to behave like we want it. What do you think should we do? [1] https://bugs.launchpad.net/mailman/+bug/1216960/comments/1 [2] https://bugs.launchpad.net/mailman/+bug/1216960 [3] https://bugs.launchpad.net/mailman/+bug/266682 Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de "All my life I wanted to be someone; I guess I should have been more specific." - Jane Wagner
