All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: List change - munging for From addresses
Date: Mon, 12 Aug 2024 15:54:27 +1000	[thread overview]
Message-ID: <20240812155427.14dc2281@canb.auug.org.au> (raw)
In-Reply-To: <20240805-honored-weightless-kangaroo-71e79e@lemur>

[-- Attachment #1: Type: text/plain, Size: 1980 bytes --]

Hi all,

On Mon, 5 Aug 2024 10:54:17 -0400 Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
>
> > 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.

Konstantin, thanks for your advice.

Munging the From addresses did not give wonderful results (among other
things it would make searching the archive a more conplex operation).

So, I am going to try "mean and lean" (since I am the owner/moderator
anyway).  Shortly (i.e. in the next hour or so), I will switch the
linuxppc-dev mailing list to use Mlmmj.  Hopefully this will fix all
our problems with DKIM/DMARC and delivery of posts from some domains.

For the subscribers, to see how to manage you subscription, you will be
able to end an email to <linuxppc-dev+help@lists.ozlabs.org> for
instructions.  Hopefully you all won't find it too restrictive.

Please report any problems with the list after the change to me.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-08-12  5: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
2024-08-12  5:54       ` Stephen Rothwell [this message]
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=20240812155427.14dc2281@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=konstantin@linuxfoundation.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.