qpop.2.1.0.Z This version of the popper has been handled by a few sites. It has had a few enhancments added to it as well as making a small departure from the popper RFC. We honor deletes and read messages when the request occurs. The RFC states that messages will not be deleted until the QUIT command is received. We found this to be a problem for dialup users who have connections fail midway through a session. We go one step further with "leave mail on server" enabled by marking messages read when you start to read them. This means that if a session terminates abnormally while reading a message it will be marked as read. This has the advantage of allowing the user to bypass a problem message. The down side is that the message is now unavailable to the user unless they disable "leave mail on server". Read all the other readme's for more information about who changed what. The latest version is 2.1.1 Mark Erikson mark@qualcomm.com This version of the popper was modified by Steve Dorner and Paul Pomes at the UIUC.edu to fix a couple of bugs and add a timeout feature. Version - 2Q1 It was then modified by Keith Pilotti at Qualcomm.com to write out changes to the temporary pop log on an abort. This diverts from the Popper RFC but it made our users life much easier. The below feature is only useful with Eudora's "Leave mail on Server" switch set (or any other client that leaves mail on the server). Basically, if a user has read 5 out of 10 messages and the session dies, the first 5 messages are marked as read. If the 5th message is good but you only receive part of it then it will be skipped (bad). But if the message was bad and caused the mail client to abort then you can continue to receive the rest of your mail (good). Version - 2Q2 This version of the popper was then modified by Mark Erikson to add HPUX file locking calls and a shorter timeout. The timeout can be configured at the command line. The timer for any of these versions starts after a command or message has been delivered and the popper is expecing input from the client. If the response takes longer than the timeout then the popper closes down the socket and cleans up the files. Version - 2Q3 This version fixes a bug in the cleanup code. If an error occurs during the login phase then a core file is dumped. Annoying but not serious since the .user.pop file is unlocked and the popper deals with this old file as a matter of course.