From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gnu.wildebeest.org (gnu.wildebeest.org [45.83.234.184]) by sourceware.org (Postfix) with ESMTPS id 734AA3858D1E for ; Tue, 23 Aug 2022 22:08:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 734AA3858D1E Received: from reform (deer0x0c.wildebeest.org [172.31.17.142]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gnu.wildebeest.org (Postfix) with ESMTPSA id 7A492302AB2C; Wed, 24 Aug 2022 00:08:51 +0200 (CEST) Received: by reform (Postfix, from userid 1000) id 4B5A12E81601; Wed, 24 Aug 2022 00:08:51 +0200 (CEST) Date: Wed, 24 Aug 2022 00:08:51 +0200 From: Mark Wielaard To: Overseers mailing list Cc: "Frank Ch. Eigler" , Simon Marchi Subject: Re: inbox.sourceware.org experiment Message-ID: References: <20220813141403.GL5520@gnu.wildebeest.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-5.3 required=5.0 tests=BAYES_00, JMQ_SPF_NEUTRAL, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Aug 2022 22:08:54 -0000 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