From: Eric Wong <email@example.com> To: firstname.lastname@example.org Subject: POP3 server? Date: Mon, 11 Apr 2016 03:41:04 +0000 Message-ID: <20160411034104.GA7817@dcvr.yhbt.net> (raw) Thinking about it more, supporting POP3 would require no more server storage overhead than running a mlmmj/mailman instance. 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.
reply index Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publically 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=20160411034104.GA7817@dcvr.yhbt.net \ --email@example.com \ --firstname.lastname@example.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
user/dev discussion of public-inbox itself Archives are clonable: git clone --mirror https://public-inbox.org/meta git clone --mirror http://czquwvybam4bgbro.onion/meta git clone --mirror http://hjrcffqmbrq6wope.onion/meta git clone --mirror http://ou63pmih66umazou.onion/meta Example config snippet for mirrors Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta nntp://news.gmane.org/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ AGPL code for this site: git clone https://public-inbox.org/public-inbox.git