On Wed, Mar 24, 2021 at 01:55:46PM +0100, Gerhard Sittig wrote: > There is a recent(?) climb in the number of messages where the > headers look like this: > > | From: A user's name via sigrok-devel <sigrok-devel@lists.sourceforge.net> > | To: sigrok-devel@lists.sourceforge.net > | Subject: [sigrok-devel] some subject > | Reply-To: user's name again <u...@example.com> > ... > What's the origin of that stupid and unsocial email setup which > results in the violation of the mailing list's foundation? Is > this some extra popular mail user agent while its authors just > are not aware? Is it a service provider doing stupid things? Was > kind of shocked to see that even git-send-email(1) traffic was > affected. Which makes me suspect that it's an ISP or mail > provider playing games. > > Can the source of this problem get identified, which makes the > affected senders look bad without their even being aware? And can > it get fixed? So that useful and helpful list communication is > possible, instead of ending up in a maze of personal service > requests and a deserted list? > > The ISP manipulated(?) git commit transmission even results in a > total misattribution of the work that the submitter has spent on > an issue, trying to help the project. Which isn't desirable > either, for several reasons. Also adds extra work on those who > try to accept this contribution, again reducing the odds of > seeing it happen. The time could have been spent on something > useful instead.
I asked the sourcehut.org community on IRC if someone recognises this pattern and Eli Schwartz (elibrokeit) was nice enough to explain it and allowed me to quote him: | It's a hugely annoying feature that mailman can enable | if the mailing list opts in to adding "[listname]" to the | subject and therefore breaks the original signing of the | sender. The list as a result destroys the from address so | that it can claim itself as the original sender, and applies | its own signature to the email. | Side effects include being incredibly ugly, breaking reply to | sender, breaking mailing list patch workflows, and being | infuriating. Solution seems to be to configure mailman right or use something more sane. My take is to not add "[sigrok-devel]" to the subject; it's redundant and only takes space from the subject line displayed in my MUA. _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
