user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
* POP3 server?
@ 2016-04-11  3:41 Eric Wong
  0 siblings, 0 replies; only message in thread
From: Eric Wong @ 2016-04-11  3:41 UTC (permalink / raw)
  To: meta

Thinking about it more, supporting POP3 would require no
more server storage overhead than running a mlmmj/mailman

And unlike running mlmmj/mailman, it still goes with the
"pull" model we favor with public-inbox and avoids the
impedance mismatch of NNTP for reading and SMTP for posting.

Users would "login" using the list address and a unique
password they generate themselves.  The password would be
used as a cookie to keep track of which messages the
user has fetched.

All the POP3 server would have to do is keep track of is the
cookie and which message (git commit SHA-1) they've seen in a
key-value store.  The caveat is if the server admin screws up
and loses the key-value DB, then users will see all messages
again :<

The k-v store would probably be SQLite, though, to reduce
installation dependencies since we already (optionally) use
SQLite for Message-ID prefix matching in the WWW interface and
NNTP article number mapping.

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2016-04-11  3:41 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-04-11  3:41 POP3 server? Eric Wong

Code repositories for project(s) associated with this inbox:

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