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-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 5B9A61F55B; Wed, 13 May 2020 22:17:15 +0000 (UTC) Date: Wed, 13 May 2020 22:17:15 +0000 From: Eric Wong To: "Eric W. Biederman" Cc: meta@public-inbox.org Subject: Re: I have figured out IMAP IDLE Message-ID: <20200513221715.GA11718@dcvr> References: <87eeyvmx74.fsf@x220.int.ebiederm.org> <20200513193144.GA9299@dcvr> <87ftc3mrq6.fsf@x220.int.ebiederm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <87ftc3mrq6.fsf@x220.int.ebiederm.org> List-Id: "Eric W. Biederman" wrote: > Eric Wong writes: > > Is your stuff based on Mail::IMAPClient still working well? > > Yes. I have fixed a few things to make the code more robust. > Which is mostly me learning how Mail::IMAPClient works. > > I also keep tweaking the ckde to make it more generic/simpler > so it has the potential to be usable by someone else. > > Would be interested if I rebased onto the lastest release and > posted my code? Perhaps you could put into contrib until you > have something that gets properly tested? Definitely. Just having it here in the archives as an attachment ought to be enough. Thanks in advance. > > I'm starting to integrate Mail::IMAPClient support into > > public-inbox-watch, but not sure how to go about with > > automated test cases... > > > > I guess it's reason to implement a read-only IMAP server along > > the lines of public-inbox-nntpd :> > > That sounds like a pain but it does sound like a good plan. I think > there are a lot of people that if there was even a simple IMAP server > would find it easier to get started using public-inbox. Agree on the pain vs payoff part; I wonder if I can just implement the UID commands and ignore the unstable sequence number madness. Mail::IMAPClient does the right thing by defaulting to Uid=>1, at least.