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,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 7DD1D1F8C6; Tue, 7 Sep 2021 22:14:04 +0000 (UTC) Date: Tue, 7 Sep 2021 22:14:04 +0000 From: Eric Wong To: Konstantin Ryabitsev Cc: meta@public-inbox.org Subject: Re: Showcasing lei at Linux Plumbers Message-ID: <20210907221404.GB17787@dcvr> References: <20210902211225.pmnykwcwcxeaunt5@meerkat.local> <20210902215850.GA5063@dcvr> <20210907213337.zir2mes6fiy4lbw7@meerkat.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20210907213337.zir2mes6fiy4lbw7@meerkat.local> List-Id: Konstantin Ryabitsev wrote: > On Thu, Sep 02, 2021 at 09:58:50PM +0000, Eric Wong wrote: > > # the destination, could be Maildir > > MFOLDER=imaps://user@example.com/INBOX.landlock > > > > # initial search: > > lei q -o $MFOLDER -t -I https://lore.kernel.org/all/ --stdin < > If I had a local mirror with extindex and I wanted to do the same thing, would > I just modify the -I flag to point at the extindex location? Yes. For local stuff that's permanently mounted, I tend to do "lei add-external $PATHNAME" so it's included by default. > One of the > options I want to investigate is making IMAP/POP3 accessible individual > mailboxes fed by lei, such that a new subsystem maintainer could have a > ready-made mailbox available to them without needing to subscribe/unsubscribe > to a bunch of mailing lists. (This would be different from read-only imap > mailboxes offered by public-inbox-imapd, since we'll be tracking individual > message state. The POP3 bit would allow them to plug it into something like > Gmail which allows sucking down remote POPs.) I think using the "-o v2:..." option for now would be the way to go for making a v2 inbox available via -imapd (and it'll get JMAP/POP3 support in the future). We don't have POP3 support in client nor server form, yet. Not sure how account/state management would work, nor how to prioritize it vs JMAP support. I'm thinking POP3 takes priority since there's more clients for it... Existing POP3 servers would work, too; since lei can output to Maildir/mbox* which can work with them. On a side note, I'm not aware of IMAP sync tools accounting for read-only IMAP servers well, since they attempt bidirectional sync. "lei import" seems alright in that regard, treating IMAP the same way it will (eventually) treat POP3.