From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH 0/2] preliminary POP3 daemon
Date: Tue, 19 Jul 2022 02:49:48 +0000 [thread overview]
Message-ID: <20220719024950.1831808-1-e@80x24.org> (raw)
Only tested with mpop and getmail as far as real-world clients
go. mpop is pretty strict and fast, too; getmail was ignoring
sequence number bugs :x
...And now I think I know where IMAP inherited horrible message
sequence number idea from :P
The on-disk storage aspect still has me a little nervous :x
over.sqlite3 is totally overkill (and thus slower than optimal)
for this, but I don't think it's worth a schema version change,
either.
Lot more code cleanups and maybe some optimizations on the way.
Eric Wong (2):
public-inbox-pop3d - a mostly read-only POP3 server
pop3: implement IN-USE from RESP-CODES (RFC 2449)
Documentation/public-inbox-config.pod | 12 +-
Documentation/public-inbox-pop3d.pod | 122 +++++++
Documentation/standards.perl | 12 +-
MANIFEST | 5 +
lib/PublicInbox/Config.pm | 5 +-
lib/PublicInbox/Daemon.pm | 8 +-
lib/PublicInbox/Inbox.pm | 10 +-
lib/PublicInbox/POP3.pm | 444 ++++++++++++++++++++++++++
lib/PublicInbox/POP3D.pm | 231 ++++++++++++++
script/public-inbox-pop3d | 8 +
t/pop3d.t | 254 +++++++++++++++
11 files changed, 1094 insertions(+), 17 deletions(-)
create mode 100644 Documentation/public-inbox-pop3d.pod
create mode 100644 lib/PublicInbox/POP3.pm
create mode 100644 lib/PublicInbox/POP3D.pm
create mode 100755 script/public-inbox-pop3d
create mode 100644 t/pop3d.t
next reply other threads:[~2022-07-19 2:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 2:49 Eric Wong [this message]
2022-07-19 2:49 ` [PATCH 1/2] public-inbox-pop3d - a mostly read-only POP3 server Eric Wong
2022-07-19 2:49 ` [PATCH 2/2] pop3: implement IN-USE from RESP-CODES (RFC 2449) Eric Wong
2022-07-20 7:27 ` [PATCH 3/2] pop3: fix numerous bugs in delete handling Eric Wong
2022-07-20 9:24 ` [PATCH v2 0/5] public-inbox POP3 daemon Eric Wong
2022-07-20 9:24 ` [PATCH v2 1/5] public-inbox-pop3d - a mostly read-only POP3 server Eric Wong
2022-07-20 9:24 ` [PATCH v2 2/5] pop3: implement IN-USE from RESP-CODES (RFC 2449) Eric Wong
2022-07-20 9:24 ` [PATCH v2 3/5] pop3: TOP requests do not expire messages Eric Wong
2022-07-20 9:24 ` [PATCH v2 4/5] netd: setup TLS bits for well-known STARTTLS ports Eric Wong
2022-07-20 9:24 ` [PATCH v2 5/5] pop3: advertise STLS in CAPA if appropriate 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=20220719024950.1831808-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).