> On Dec 4, 2022, at 11:30, Wietse Venema <wie...@porcupine.org> wrote:
>
> Dan Mahoney:
>> Hey all,
>>
>> We have a mailing list (of like ten, not-often-changing people)
>> that we'd like to not have to spin up a full mailing list program
>> like mailman or whatnot.
>>
>> We don't need subsciption management or archiving, but we could
>> really use the user rewriting akin to mailman's from_is_list
>> function, so that:
>>
>> a message
>>
>> FROM: "Joe" j...@example.com <mailto:j...@example.com>
>> TO: l...@domain.org <mailto:l...@domain.org>
>>
>> is rewritten to:
>>
>> FROM: Joe via domain list l...@domain.org <mailto:l...@domain.org>
>> TO: l...@domain.org <mailto:l...@domain.org>
>> REPLY-TO j...@example.com <mailto:j...@example.com>
>>
>> I feel like the right answer here is something like "procmail" ?
>> is there some kind of alias map that can be used to handle this?
>> Is there a standard postfix way to rewrite headers like this?
>
> Postfix can override the envelope sender address with an owner-listname
> alias. However, Postfix currently requires external software to
> replace the original From: header with three headers (X-Original-From:
> with the original sender, From: with the list address, and Reply-To:
> with the list or the original sender).
>
> The header munging could be done with a content filter (such as a
> Milter, which could also do the alias expansion), but why cobble
> together a solution when a list manager already provides a proven
> implementation.
I can't tell if that's a rhetorical question, but I'll answer it:
Because I don't need 90 percent of what that list manager does (I do not need
nor want subscription self-management, subject tagging (why break DKIM?), body
or mime tagging, archiving, digesting). I don't need the ability to handle any
commands via email. I do not want a web interface to manage the thing. VERP
is useful, but that's doable on its own with postfix.
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.
