user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <e@80x24.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: meta@public-inbox.org
Subject: IMAP server [was: Q: V2 format]
Date: Fri, 13 Jul 2018 23:07:46 +0000	[thread overview]
Message-ID: <20180713230746.GA2680@dcvr> (raw)
In-Reply-To: <878t6f1ch7.fsf@xmission.com>

"Eric W. Biederman" <ebiederm@xmission.com> wrote:
> > "Eric W. Biederman" <ebiederm@xmission.com> wrote:
> >> Eric Wong <e@80x24.org> writes:
> > As far as personal mail goes, I wouldn't want serial numbers at all
> > (more unnecessary state to keep track of).
> 
> At least imap requires serial numbers, and I imagine the easy transition
> for mail clients is to have an imap server.  As you have mentioned an
> ordered list of commits is good enough to reconstruct the msgnum
> reliably so it is unlikely we would need to do anything special there.

I would rather layer IMAP (and POP3) on top of NNTP than to tie
it to any git/SQLite/Xapian parts in public-inbox.  We could
ship it with public-inbox, of course; but I don't see why an
IMAP or POP3 server could not work by using innd (or similar) as
a backend.

I don't think any design compromises need to be made to existing
the git/SQLite/Xapian parts to support IMAP/POP3.

Hosting an IMAP/POP3 server is way more overhead for the admin
as it requires storing user credentials and storing per-reader
state.  So the preference is to do NNTP as well as possible and
layer the complexity of per-user account data on top of it.

Right now, none of the NNTP/HTTP parts require write access
to the machine it runs on aside from log files.

Thus the goal is to promote NNTP usage as it's cheapest/easiest
for the server admin; but to still have IMAP/POP3 as stopgaps
(similar to the ssoma/mlmmj-replay script I use to allow SMTP
subscriptions to this inbox).

  parent reply	other threads:[~2018-07-13 23:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-11 20:01 Q: V2 format Eric W. Biederman
2018-07-11 21:18 ` Konstantin Ryabitsev
2018-07-11 21:41   ` Eric W. Biederman
2018-07-12  1:47 ` Eric Wong
2018-07-12 13:58   ` Eric W. Biederman
2018-07-12 23:09     ` Eric Wong
2018-07-13 13:39       ` Eric W. Biederman
2018-07-13 20:03         ` Eric W. Biederman
2018-07-13 22:22           ` msgmap serial number regeneration [was: Q: V2 format] Eric Wong
2018-07-14 19:01             ` Eric W. Biederman
2018-07-15  3:18               ` Eric Wong
2018-07-16 15:20                 ` Eric W. Biederman
2018-07-13 22:02         ` bug: v2 deletes on incremental fetch " Eric Wong
2018-07-13 22:51           ` Eric W. Biederman
2018-07-14  0:46           ` [PATCH] v2writable: unindex deleted messages after incremental fetch Eric Wong
2018-07-13 23:07         ` Eric Wong [this message]
2018-07-13 23:12           ` IMAP server [was: Q: V2 format] Eric W. Biederman
2018-09-28 20:10           ` Johannes Berg
2018-09-28 21:01             ` Eric W. Biederman
2018-10-01  7:46               ` Johannes Berg
2018-10-01  8:51                 ` Eric W. Biederman

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=20180713230746.GA2680@dcvr \
    --to=e@80x24.org \
    --cc=ebiederm@xmission.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/public-inbox.git

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).