From: Mark Wielaard <mark@klomp.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
Simon Marchi <simon.marchi@polymtl.ca>
Subject: Re: inbox.sourceware.org experiment
Date: Wed, 24 Aug 2022 00:08:51 +0200 [thread overview]
Message-ID: <YwVP8+LHvyLzUG/+@wildebeest.org> (raw)
In-Reply-To: <Yv5DvkMnDvS7wdIW@wildebeest.org>
Hi,
On Thu, Aug 18, 2022 at 03:50:54PM +0200, Mark Wielaard via Overseers wrote:
> > > And do we need to update/regenerate
> > > /etc/aliases.db and/or /etc/mailman/aliases.db ?
> >
> > The proposal is to not touch /etc/aliases* NOR /etc/mailman/aliases*.
> > The proposal is to generate a new file like
> > /etc/postfix/mailman-inbox-aliases from /etc/mailman/aliases. That
> > new file would be the one postfix would read. It could be texthash:
> > rather than hash: so postmap would not even be necessary for updates.
> > That depends on whether the relevant alias-expansion postfix process
> > is short- or long-lived.
>
> OK, I see the following in /etc/postfix.main:
>
> # CGF 2020-03-08 12:49
> alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases
>
> # CGF 2020-03-18 14:10 EST - newaliases wasn't affecting /etc/mailman/aliases
> alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases
>
> So I assume calling newaliases regenerates the hash/.db files.
>
> I can write a script to generate mailman-inbox-aliases this weekend
> when I have stable internet access again. Will post to the list before
> installing to make sure I don't accidentially break something.
Sorry this took a bit longer. But I wanted to make sure I got it right.
I solved it slightly simpler by installing a /home/inbox/.forward with:
|/usr/bin/public-inbox-mda
And then simply add the inbox user as extra recipient. So the STANZA
looks like:
# STANZA START: test-list
# CREATED: Sat Mar 7 13:49:45 2020
test-list: "|/usr/local/mailman/mailman post test-list", inbox
test-list-bounces: "|/usr/local/mailman/mailman bounces test-list"
test-list-confirm: "|/usr/local/mailman/mailman confirm test-list"
test-list-join: "|/usr/local/mailman/mailman join test-list"
test-list-leave: "|/usr/local/mailman/mailman leave test-list"
test-list-owner: "|/usr/local/mailman/mailman owner test-list"
test-list-request: "|/usr/local/mailman/mailman request test-list"
test-list-subscribe: "|/usr/local/mailman/mailman subscribe test-list"
test-list-unsubscribe: "|/usr/local/mailman/mailman unsubscribe test-list"
# STANZA END: test-list
The script to generate those is in
/etc/mailman/mailman-aliases-to-inbox.sh
And the postfix main.cf has been updated to use the generated
/etc/mailman/aliases-inbox
The only thing I don't know is how to automate the
/etc/mailman/mailman-aliases-to-inbox.sh running when new lists are
added. Should this be a mailman trigger or cronjob check?
Thanks,
Mark
next prev parent reply other threads:[~2022-08-23 22:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-13 14:14 Mark Wielaard
2022-08-15 13:00 ` Mark Wielaard
2022-08-16 21:36 ` Mark Wielaard
2022-08-16 22:10 ` Frank Ch. Eigler
2022-08-17 12:25 ` Mark Wielaard
2022-08-17 13:24 ` Frank Ch. Eigler
2022-08-17 21:18 ` Mark Wielaard
2022-08-17 21:33 ` Frank Ch. Eigler
2022-08-18 13:50 ` Mark Wielaard
2022-08-18 14:40 ` Simon Marchi
2022-08-21 17:41 ` Mark Wielaard
2022-08-23 20:15 ` Mark Wielaard
2022-08-23 22:08 ` Mark Wielaard [this message]
2022-08-24 10:05 ` Mark Wielaard
2022-08-24 21:06 ` Mark Wielaard
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=YwVP8+LHvyLzUG/+@wildebeest.org \
--to=mark@klomp.org \
--cc=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).