DESCRIPTIONipop2d and ipop3d are servers which support the POP2 and POP3 remote mail access protocols respectively. ipop2d and ipop3d can also be used by POP2 and POP3 clients respecitively to access mailboxes on IMAP servers by specifying a login user name in the form <host>:<user> e.g., SERVER.WASHINGTON.EDU:SMITH.
These daemons contain CRAM-MD5 and APOP support. See the md5.txt documentation file for additional information.
BUGSThe POP2 and POP3 protocols are intrinsically less flexible than IMAP and do not maintain `read' vs `unread' state on the server. As a result, most POP based software transfers all the mail from the server to the client and deletes it from the server. This necessarily locks the user into using only a single client.
POP3 does not allow you to specify an alternate folder from the user's default.