home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!mips!sdd.hp.com!hp-cv!ogicse!plains!news.u.washington.edu!news
- From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin)
- Newsgroups: comp.mail.misc
- Subject: POP in Pine
- Message-ID: <MS-C.712184874.1147902781.mrc@Tomobiki-Cho.CAC.Washington.EDU>
- Date: 26 Jul 92 21:07:54 GMT
- Sender: news@u.washington.edu (USENET News System)
- Organization: University of Washington
- Lines: 21
- Content-Type: TEXT/PLAIN; charset=US-ASCII
- Mime-Version: 1.0
-
- 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...
-