From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 9E6241F4BD; Thu, 10 Oct 2019 10:06:54 +0000 (UTC) Date: Thu, 10 Oct 2019 10:06:54 +0000 From: Eric Wong To: Alyssa Ross Cc: meta@public-inbox.org Subject: Re: Do I need multiple publicinbox..address values? Message-ID: <20191010100654.wn6jp3quu7rfyanr@dcvr> References: <87imp05hlm.fsf@alyssa.is> <20191008001050.rwd7bh7cek7qrydi@dcvr> <877e5eceov.fsf@alyssa.is> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <877e5eceov.fsf@alyssa.is> List-Id: Alyssa Ross wrote: > > Sorry for that confusion. Historically, I wrote public-inbox > > and -mda because I needed to migrate mailing lists with a > > several month window where the old list would be active, > > but I was preparing for the switch: > > > > So it started as: > > > > posters -> to_be_shutdown_host -> MTA (postfix) -> public-inbox-mda > > > > And ends up being: > > > > posters -> MTA (postfix) -> public-inbox-mda --[1]--> (mlmmj|mailman) > > > > > > It sounds like what you're doing is: > > > > MTA -> (mlmmj|mailman) -> public-inbox-mda > > > > Which wasn't my original intended usecase for -mda, but is for -watch. > > Interesting! The reason I set it up this way is that mailman (at least > v3) doesn't archive raw incoming mail -- the default archiver, > Hyperkitty, pulls out the body and some headers it cares about, saves > them into a database, and discards the rest. Which IMO is not great for > an archiver (although I do like Hyperkitty as a web interface for people > who haven't yet seen the light of mail). So my plan is to use > public-inbox as my primary archiver, and just use Hyperkitty as a > "modern" web interface. Yeah, right now you could have Mailman deliver to an address -> Maildir which public-inbox-watch runs on. It's a bit roundabout and you'd need to age out old messages from the Maildir. Or you could write an NNTP -> pipe-to-arbitrary command script which can pipe to Mailman or mlmmj, keeping track of which messages have already been sent (or wait for me to write it). I've been meaning to replace scripts/ssoma-replay (for mlmmj) with that script at some point. I've never actually run Mailman, but I assume it allows raw messages to be piped to it like most mail tools.