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 08FD51F4BD; Tue, 8 Oct 2019 22:11:09 +0000 (UTC) Date: Tue, 8 Oct 2019 22:11:08 +0000 From: Eric Wong To: "Eric W. Biederman" Cc: Alyssa Ross , meta@public-inbox.org Subject: Re: Do I need multiple publicinbox..address values? Message-ID: <20191008221108.3wsso25kviiwd7ek@dcvr> References: <87imp05hlm.fsf@alyssa.is> <20191008001050.rwd7bh7cek7qrydi@dcvr> <87wodfctwd.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87wodfctwd.fsf@x220.int.ebiederm.org> List-Id: "Eric W. Biederman" wrote: > Eric Wong writes: > > > Alyssa Ross wrote: > > > >> Subject: Do I need multiple publicinbox..address values? > > > > Absolutely not > > > >> Suppose I have a mailing list, foo-discuss@example.org, and a > >> public-inbox set up, subscribed to that mailing list, that is subscribed > >> to that list as public-inbox+foo-discuss@example.org, where my MTA > >> delivers to public-inbox using public-inbox-mda. > > > > Currently, -mda does if you're mirroring, unfortunately. I > > think Eric Biederman is/was working on List-Id support to drop > > that requirement, but I'm not sure where that is... > > > > Eric B: would you mind if I take List-Id support over? I've got > > some hours free in the coming days(s)... (I think :x) > > I believe I have the config side of the work done. I haven't > figured out how to add this to public-inbox-mda/public-inbox-watch. > > Let me send out what I have and then you can work on the bits > for public-inbox-watch public-inbox-mda. Thanks, will do. > Last round I was messing with this I almost had my imap fetcher in > shape. I may try again but let's get the listid thing settled first > if we can. Alright. Btw, would using libcurl for IMAP support be easier for you? I'm considering introducing libcurl support via Inline::C (it might be easier to hook into the event loop for other things). I'm also thinking about distributing some C via *.h header files so it's easier to sparse/lint the code w/o it being embedded inside a Perl file (I'd send those *.h files to Inline::C for production use). Using *.h since MakeMaker will automatically assume any *.c files will be made into an XS extension, and I'm not sure how to workaround that... (using GNU make w/o MakeMaker is an option) Whether it's Perl or C; I want to keep everything on end-user systems in source form, so they can just hack/update the source if needed instead of having to find/download/build it to experiment.