From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] README: add POP3 bits
Date: Mon, 20 Feb 2023 11:06:03 +0000 [thread overview]
Message-ID: <20230220110603.2392450-1-e@80x24.org> (raw)
Maybe this can make our newish support of POP3 more
noticeable...
---
README | 14 +++++++++-----
1 file changed, 9 insertions(+), 5 deletions(-)
diff --git a/README b/README
index 01089314..abe8ddc0 100644
--- a/README
+++ b/README
@@ -3,7 +3,7 @@ public-inbox - an "archives first" approach to mailing lists
public-inbox implements the sharing of an email inbox via git to
complement or replace traditional mailing lists. Readers may
-read via NNTP, IMAP, Atom feeds or HTML archives.
+read via NNTP, IMAP, POP3, Atom feeds or HTML archives.
public-inbox spawned around three main ideas:
@@ -38,7 +38,7 @@ headers. List server admins are also burdened with delivery
failures.
public-inbox uses the "pull" model. Casual readers may
-follow the list via NNTP, IMAP, Atom feed or HTML archives.
+follow the list via NNTP, IMAP, POP3, Atom feed or HTML archives.
If a reader loses interest, they simply stop following.
@@ -56,7 +56,7 @@ Features
* stores email in git, readers may have a complete archive of the inbox
-* Atom feed, IMAP, NNTP allows casual readers to follow via local tools
+* Atom feed, IMAP, NNTP, POP3 allows casual readers to follow via local tools
* uses only well-documented and easy-to-implement data formats
@@ -64,7 +64,7 @@ Try it out now, see https://try.public-inbox.org/
Requirements for reading:
-* any software capable of IMAP, NNTP or following Atom feeds
+* any software capable of IMAP, NNTP, POP3 or following Atom feeds
Any basic web browser will do for the HTML archives.
We primarily develop on w3m to maximize accessibility.
@@ -133,6 +133,10 @@ You may also clone all messages via git:
git clone --mirror https://public-inbox.org/meta/
torsocks git clone --mirror http://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/meta/
+POP3 access instructions are at:
+
+ https://public-inbox.org/meta/_/text/help/#pop3
+
Anti-Spam
---------
@@ -157,7 +161,7 @@ aims to preserve the focus on content, and not presentation.
Copyright
---------
-Copyright 2013-2021 all contributors <meta@public-inbox.org>
+Copyright all contributors <meta@public-inbox.org>
License: AGPL-3.0+ <https://www.gnu.org/licenses/agpl-3.0.txt>
This program is free software: you can redistribute it and/or modify
reply other threads:[~2023-02-20 11:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230220110603.2392450-1-e@80x24.org \
--to=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).