On Sun, Dec 04, 2022 at 03:59:07PM -0800, Dan Mahoney <d...@prime.gushi.org> 
wrote:

> My needs are pretty much two things:
> 
> 1) Only subscribed people may post.
> 2) That post should not get killed by DMARC, which means forwarded
> messages need to pass SPF/DKIM, which means remailing, not forwarding.
> 
> The state of mailing list managers right now is also complex.  Would
> you rather have:
> 
> The one that is based on a two-years EOL version of python with no
> clean migration path to the current version (which still inexplicably
> has a TON of open source stuff under it, including ISC, IETF, and
> NANOG) (mailman2)
> 
> Or the "current version" of that one that takes not only a database
> but also four different packages plus a full nginx/django install to
> set up (mailman3)
> 
> Or the perl-based one written for perl 4 with the last release
> sometime in 2000 (majordomo)?
> 
> If there's a better piece of software, please let me know.

Assuming that wasn't a rhetorical question, :-)
I'd consider majordomo. It probably does
what you need without being a hassle.
It works in Perl 5 too, you know. :-)
And it doesn't need a database or a web server.

If memory serves, you need to set up enough aliases
for each mailing list that it's worth automating
their addition, but if it's a single list, you
wouldn't need to. This is what I used to have in
aliases for each list.

  # Majordomo template
  # (e.g. (LIST, DOMAIN, DOM, ME) = (firewall-users, fwup.org, fwup, raf))
  #
  # majordomo-DOM: "| /opt/majordomo/wrapper majordomo -C 
/opt/majordomo/DOMAIN.cf"
  # owner-majordomo-DOM: ME
  #
  # Mailing List Template (with digest and archive)
  #
  # LIST: "| /opt/majordomo/wrapper resend -C /opt/majordomo/DOMAIN.cf -l LIST 
-h DOMAIN LIST-outgoing"
  # LIST-digest: LIST
  # LIST-outgoing: :include:/opt/majordomo/lists/DOMAIN/LIST,
  #   "| /opt/majordomo/wrapper digest -c /opt/majordomo/DOMAIN.cf -r -C -l 
LIST-digest LIST-digest-outgoing",
  #   "| /opt/majordomo/wrapper archive2.pl -C /opt/majordomo/DOMAIN.cf -a -m 
-f /opt/majordomo/lists/DOMAIN/LIST.archive"
  # LIST-digest-outgoing: :include:/opt/majordomo/lists/DOMAIN/LIST-digest
  # owner-LIST: owner-majordomo-DOM
  # owner-LIST-outgoing: owner-LIST
  # owner-LIST-digest: owner-LIST
  # owner-LIST-digest-outgoing: owner-LIST
  # LIST-request: "| /opt/majordomo/wrapper majordomo -C 
/opt/majordomo/DOMAIN.cf -l LIST"
  # LIST-digest-request: "| /opt/majordomo/wrapper majordomo -C 
/opt/majordomo/DOMAIN.cf -l LIST-digest"
  # LIST-approval: owner-LIST
  # LIST-digest-approval: owner-LIST

The above creates digests and archives (both optional),
but it does nothing to make the archives available on the web.

Oh, actually majordomo.pl shouldn't work in perl5 since 5.10.
It uses $* which was removed then (2007). That's wierd. It
was still working for me in 2015.

But here's a version that has that fixed for later perls:

  https://github.com/Distrotech/majordomo

And here's a version of majordomo 2 (which I hadn't
heard of before):

  https://github.com/jasontibbitts/majordomo

cheers,
raf

Reply via email to