On Tue, Feb 11, 2020 at 05:25:39PM +0100, Wolfgang Denk wrote:
Dear Tom,
In message 20200211150800.D895B2403FE@gemini.denx.de I wrote:
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.
There is even a clean approach upstream [1]:
[1] https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1825
Apparently the first RC where this commit is included is mailman 2.1.30rc1; we expect it will take ~ 1 month for v2.1.30 to get released, 2 months max. If it's OK we will jsut wait for this release, then upgrade, and configure with this option set:
1446 # The process which avoids sending a list copy of a message to a member who 1447 # is also directly addressed in To: or Cc: can drop the address from Cc: to 1448 # avoid growing a long Cc: list in long threads. This can be undesirable as 1449 # it can break DKIM signatures and possibly cause confusion. To avoid changes 1450 # to Cc: headers, set the list's drop_cc to No. 1451 DEFAULT_DROP_CC = Yes
Agreed?
Agreed, thanks again!