At 12:05 AM -0800 12/1/02, Gregory Hicks wrote:

 Actually, if you have popper in 'server' mode with a temp-drop-dir set
 to something other than the spool dir, enable-cache-dir set to something
 else also (usually the same as temp-drop-dir), service is vastly
 improved - even for those users that have large mail files...
The cache file allows Qpopper to avoid reading the spool if no new mail has arrived since the previous mail check (bulletins are OK). (To do: use the cache file even when new mail has arrived.)

 A gotcha though is that most mail clients will 'forget' about messages
 that are too large to download over dial-up connections (popper
 presents the info one time about the message, the MUA (mail user agent)
 'forgets about the particular message, and popper never presents the
 mail as being unread again.)
Qpopper presents the messages each time (in UIDL, for example). It's up to the client to download or not. There may be some clients that put the message ID in their list of known messages, then neglect to download or delete, but this has nothing to do with Qpopper.

Some clients allow the user to make sure old messages get deleted off the server. For example, Eudora has a 'check mail special' option (hold down shift while checking mail on Windows, hold down option on a Mac). This allows the user to, for example, tell Eudora to delete everything that exists on the server, or to download the headers of all messages on the server, which can then be gone through and marked for deletion off the server.




Reply via email to