🚀 go-pugleaf

To express what David Collier-Brown said a bit more fully and accurately:

Pine uses the c-client library.  As such, it has local mail file capability
with various storage technologies, and remote mail capability with IMAP2.
There is no c-client driver for POP2 or POP3, but it would not be difficult to
write one.  Other than as a fun exercise, the question is `why?'  POP2 or POP3
with Pine would be much slower than with IMAP2, because capabilities that are
intrinsic in IMAP would have to be simulated with POP.

The c-client distribution includes IMAP2, POP2, and POP3 servers.  All of
these servers themselves use c-client.  It is possible to use the POP server
to open an IMAP connection from a POP client!  So, in the c-client model, the
protocols (IMAP or POP) are really nothing more than remote procedure call
mechanisms between c-clients.

One of the neatest things about IMAP2bis is remote MIME parsing.  So, if you
received a Godzilla MIME message, the MIME parsing is done at the server and
its structure is passed to the client.  Then you can select what MIME data you
want to fetch.  This is great over SLIP lines!  In POP, you end up having to
fetch the entire message to do MIME parsing, which can be a problem for small
PC's and slow links...