[Mailman-Developers] Re: X-Mailman-Original-DKIM-Signature
On Thu, 2021-04-15 at 10:28 +0200, Alessandro Vesely wrote: > Hi, > > I discovered this just today, after a list I'm subscribed to enabled it. > > I have a filter which tries to validate original signatures by removing > footers > and subject tags. Removing "X-Mailman-Original-" is going to be the next > addition. > > I guess the purpose of this option is to spare a dkim=fail result in the > recipient's header. However, for documentation purposes[*], I'd be comforted > by some document, discussion, or even a crispy comment about the intended > usefulness of masking existing signatures. Google found nothing. Any > pointer? > Hi Ale, Here's he commit that was merged into MM 2.1 on 2016-05-26: https://code.launchpad.net/~jimpop/mailman/preserve_dkim It grew out of the discussion starting here: (login required): https://list.mailop.org/private/mailop/2016-May/007692.html hth, -Jim P. ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: [Mailman-Users] The last release from the GNU Mailman project
On Sat, 2020-02-29 at 16:26 +0900, Stephen J. Turnbull wrote: > > As always in open source, everybody in general is invited, (almost) > nobody gets a personal invitation.[1] It's unfortunate that the way > things work folks like you and Jim don't find it so easy to pop over > to mailman-developers to find out about these things in advance, but > we also don't want to burden mailman-users with nitty-gritty details > that that may never be relevant to them. Ahem, I've been on mm-dev for years now, Stephen we've interacted here several times in the past several years.. -Jim P. ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
[Mailman-Developers] Re: mailman3 merge strategies (squashing commits vs. leaving commits as they are)
On Fri, 2019-08-09 at 17:10 +0900, Stephen J. Turnbull wrote: > Abhilash Raj writes: > > + Mailman Developers, since this seems like a general discussion topic. > > > > On Thu, Aug 8, 2019, at 2:01 AM, Mike Gabriel wrote: > > > Hi Abhilash, > > > > > > I just looked into the two recent merges from Daniel on mailman's > > > master branch. > > > > > > I noticed that you squashed the MR branch commits into one commit > > > before the merge and that this one commit uses the latest commit > > > messages of the MR branch to describe what the squashed commits do. > > > Unfortunately, that commit messages does not appropriately describe > > > what the commit in fact does. > > I seem to recall that somebody (one of the VCSes? one of the web repo > hosting services?) has a system that squashes the commits and > concatenates all the log messages for the merged branch. Perhaps > gitlab has an option to do this? Yes, gitlab has an option to do this, it's a checkbox during the creation of the MR. -Jim P. ___ Mailman-Developers mailing list -- mailman-developers@python.org To unsubscribe send an email to mailman-developers-le...@python.org https://mail.python.org/mailman3/lists/mailman-developers.python.org/ Mailman FAQ: https://wiki.list.org/x/AgA3 Security Policy: https://wiki.list.org/x/QIA9
