From: Eric Wong <email@example.com>
Subject: existing mail protocol thoughts (POP3 vs NNTP vs IMAP)
Date: Sun, 14 Aug 2022 18:16:45 +0000 [thread overview]
Message-ID: <20220814181645.M588951@dcvr> (raw)
Random thinking aloud on existing mail protocols...
POP3 doesn't support compression, so that makes it wasteful.
We also use a wonky account system to track deletes.
POP3 is not supported by lei, yet, and Net::POP3 has the same
performance problem as Net::NNTP and Mail::IMAPClient in that it
lacks pipelining support.
NNTP mandates extra headers (Path:, Newsgroup:, Xref:) which can
waste space and screw up exact dedupe and DKIM checking.
Compression support is still lacking in Net::NNTP.
IMAP supports compression, and doesn't add/modify existing
headers at all. So I think it's the least bad from that
perspective, but we need to slice it into multiple mailboxes
to avoid overloading clients.
JMAP doesn't have many widely available CLI client options in
distros, atm (e.g. mpop, getmail, offlineimap, isync/mbsync,
 Net::NNTP COMPRESS support patch:
reply other threads:[~2022-08-14 18:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
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 \
* 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
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).