linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: List change - munging for From addresses
Date: Mon, 5 Aug 2024 10:54:17 -0400	[thread overview]
Message-ID: <20240805-honored-weightless-kangaroo-71e79e@lemur> (raw)
In-Reply-To: <20240805124204.49ed65df@canb.auug.org.au>

On Mon, Aug 05, 2024 at 12:42:04PM GMT, Stephen Rothwell wrote:
> > I would generally say that From-munging isn't a great option for any list that
> > receives patches. A much better approach is to just not modify the message
> > headers or message body. This should be possible with mailman.
> 
> Unfortunately, I have not found a way to ensure Mailman (v2, at least)
> will not modify messages in all cases e.g. in some circumstances it
> will modify the To/Cc list.

Right, Mailman-2 is also dependent on Python-2, which is quite obsolete by
this point as well.

> So, an alternative for us (though considerable more work) is to change
> mailing list software.  Mailmanv3 would be an option, but seems overly
> complex.  I see vger.kernel.org is now using mlmmj - is that a
> reasonable option for us (i.e. is it able to not modify messages but
> still have enough features)?  If so any hints about migrating? ;-)

I'd say that mlmmj has a very different approach than mailman -- it exposes
very little to end-users and list admins. Any changes to the list
configuration must be made by server admins, which can be seen as very
limiting by someone used to how mailman does it.

However, it *is* a great option for running mailing lists that process
patches and couples well with public-inbox for archiving. It also requires a
fraction of resources of mailman-3.

If you want to be able to have a more hands-off approach to your mailing list
management, with a fancy UI and lots of list admin tunables, your best option
is Mailman-3. If you want a "mean and lean" option, then mlmmj is the way to
go.

-K

  reply	other threads:[~2024-08-05 14:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  3:03 List change - munging for From addresses Stephen Rothwell
2024-08-02  3:19 ` Stephen Rothwell via Linuxppc-dev
2024-08-02 15:54 ` Konstantin Ryabitsev
2024-08-05  2:42   ` Stephen Rothwell
2024-08-05 14:54     ` Konstantin Ryabitsev [this message]
2024-08-12  5:54       ` Stephen Rothwell
2024-08-12  6:19         ` Stephen Rothwell
2024-08-12  6:32           ` Michael Ellerman
2024-08-12 13:53           ` Konstantin Ryabitsev
2024-08-25 22:41             ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240805-honored-weightless-kangaroo-71e79e@lemur \
    --to=konstantin@linuxfoundation.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).