> On Jan 10, 2023, at 18:28, Viktor Dukhovni <postfix-us...@dukhovni.org> wrote:
>
> On Tue, Jan 10, 2023 at 05:10:41PM -0800, Dan Mahoney wrote:
>> My actual question of "is there a mailing list engine that *just*
>> handles a tiny subset of what a full-blown mailman does (no cgi, no
>> membership management, some basic body tagging perhaps)" remains
>> unanswered and I can't believe that such an animal doesn't exist.
>> This is exactly the featureset we'd get with some kind of ESP, except
>> in-house.
>
> Your question is unrelated to your problem description. Why do you
> believe that mailman or similar would help? It is only really useful
> for automated archiving, s-u-b-scribe, u-n-s-u-b-scribe, and bounce
> handling, which it doesn't seem you need.
In the use case where an alias *is* being sent to from external addresses (and
is allowed to do so), things like DKIM and SPF complicate delivery, and
stripping those headers, rewriting the sender to a local one, and redelivering
with a clean set of headers (which can, themselves, be SPF/DKIM authenticated)
and a new reply-to header feels like a useful function.
This same tool is also useful in a case where I'm forwarding something with
procmail, but have somehow modified the message (stripped an attachment, tagged
the subject, etc). Breaking DKIM/SPF can cause a rejection, -- or worse, for
mail to silently and uncontrollably be silently shuffled into the spam folder
by various freemail providers, and even worse, lower the reputation of my mail
systems because users are doing this.
The idea of a command line program you can pipe a mail to with a command line
arg that lets you specify a list of recipients in a textfile, and have new
messages injected, cleanly, with stripped headers, into the queue, feels like
something that ought to exist.
Others have suggested a program that has the option to simply create a new mail
and attach the original as mime-attachment.
I suppose what I'm looking for is a smarter version of /bin/mail that knows
when to only forward the body portions of a mail, but my reading of most of the
ones in things like gnu mailutils show that they're not smart enough to do what
I want.
> If you're lucky, "owner-" aliases will help. Otherwise, perhaps more
> likely, you'll have to track down which particular recipient doesn't
> want your mail.
The recipient is known. Why their bounce message cited our internal alias as a
delivered-to address instead of their own, in their reject message, was the
problem, that exposed the original common issue of "maybe aliases are the wrong
way to go about this", and exposed my other need which is also solved by an
alternate forwarder.
-Dan
