From: James Bottomley <James.Bottomley@HansenPartnership.com> To: Konstantin Ryabitsev <email@example.com>, Eric Wong <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Thoughts on search-based imap mailboxes Date: Fri, 05 Feb 2021 14:37:55 -0800 [thread overview] Message-ID: <bad84d1ade2695bf16acb0be2a0547314ed06228.camel@HansenPartnership.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Sat, 2020-10-03 at 10:50 -0400, Konstantin Ryabitsev wrote: > On Fri, Oct 02, 2020 at 08:08:30PM +0000, Eric Wong wrote: [...] > > A client-side tool is likely required anyways, I'm thinking > > having saved search functionality in a local tool writing to > > Maildir/mbox might be the best way forward as w.r.t. scalability > > and offline access (and reading + saving flags from the > > Maildir/mbox). Colour me annoyed by the inability to mark email messages as Seen too. > > External/detached index I'm working on for global search will > > also be appropriate for client-side tooling, I think, as it's > > being designed with non-public-inbox data sources in mind, too. > > Instead of a "client-side" can it just be an intermediary tool that > can run either on the client, or on any other piece of > infrastructure? The main reason I'm interested in that is because > several people I know use very thin clients for their work > (chromebooks) and I would like to offer them this service as a perk > of kernel.org instead of forcing them to set it up and maintain on > their own. Actually, I'd like a "server" side solution to this as well because I want the message "seen" status to be updated on all my devices when I read a message on any of them. Could this be implemented as something like a pass-through imap server which has a login infrastructure for storing the flag metadata but sends most other queries to the backend? If such a beast existed I'd be happy to run it locally on my cloud system, and I'm sure Konstantin could run it for all those of use with kernel.org addresses. James
next prev parent reply other threads:[~2021-02-05 22:37 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-02 14:34 Konstantin Ryabitsev 2020-10-02 20:08 ` Eric Wong 2020-10-03 14:50 ` Konstantin Ryabitsev 2020-10-03 19:40 ` Eric Wong 2021-02-05 22:37 ` James Bottomley [this message] 2021-02-06 0:01 ` 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=bad84d1ade2695bf16acb0be2a0547314ed06228.camel@HansenPartnership.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Thoughts on search-based imap mailboxes' \ /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
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 NNTP newsgroup(s).