From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Eric Wong <e@80x24.org>
Cc: meta@public-inbox.org
Subject: Re: Showcasing lei at Linux Plumbers
Date: Wed, 8 Sep 2021 09:36:15 -0400 [thread overview]
Message-ID: <20210908133615.grlzysueyxwgcoyn@meerkat.local> (raw)
In-Reply-To: <20210907221404.GB17787@dcvr>
On Tue, Sep 07, 2021 at 10:14:04PM +0000, Eric Wong wrote:
> > 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).
I'm worried that read-only imap folders are going to cause problems for dumber
imap clients, including mbsync. My goal is to make it easy for folks to use
existing tools to which they are already accustomed, since my experience is
that if the learning curve is too steep or requires too much fiddling to
configure, the uptake is going to be extremely limited.
On the other hand, a service that offers full search-based imap/pop3 folders
is going to be an easy sell:
- it works with any imap client as a simple extra account
- it can be mirrored locally and synced two-ways via mbsync
- it can be incorporated into existing services like gmail, so people can
monitor things on the go
- I can do clever things like suspend "lei up" runs if there was no access to
the folder for over N weeks
- we can use FS dedupe features since all messages are going to be
identical after writing them out to maildirs
The slightly harder part is making it easy for people to configure their
search parameters, but I'm hoping to expose this via a git repo.
I'm not implementing this right away, but I'm going to float this idea at
plumbers to see what the reception is going to be. I believe this will be of
interest to many devs, since this would allow them to no longer depend on
their corporate mail servers and their mail-mangling ways.
-K
next prev parent reply other threads:[~2021-09-08 13:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 21:12 Showcasing lei at Linux Plumbers Konstantin Ryabitsev
2021-09-02 21:58 ` Eric Wong
2021-09-03 15:15 ` Konstantin Ryabitsev
2021-09-04 21:36 ` [PATCH] lei_to_mail+mbox_reader: fix handling of empty/bogus emails Eric Wong
2021-09-07 18:17 ` Konstantin Ryabitsev
2021-09-07 20:56 ` Eric Wong
2021-09-07 21:20 ` Konstantin Ryabitsev
2021-09-07 22:22 ` Eric Wong
2021-09-07 21:33 ` Showcasing lei at Linux Plumbers Konstantin Ryabitsev
2021-09-07 22:14 ` Eric Wong
2021-09-08 13:36 ` Konstantin Ryabitsev [this message]
2021-09-08 14:49 ` Eric Wong
2021-09-08 17:17 ` Konstantin Ryabitsev
2021-09-08 17:32 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210908133615.grlzysueyxwgcoyn@meerkat.local \
--to=konstantin@linuxfoundation.org \
--cc=e@80x24.org \
--cc=meta@public-inbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).