At 10:57 AM +0100 3/5/02, Eric Luyten wrote: >It invariably happens after a new message arrived for a given user AND >a subsequent succesful POP session, with 'leave messages on server' set.
Can you reproduce this with debug tracing? Perhaps it is a problem updating the cache on the previous session, as you suggested. Or maybe in the case where new mail arrived during a session Qpopper updates the cache after the spool. It may even be a a case where the code is working as intended, and the error should really be a debug trace message instead. (Currently, Qpopper does not use the cache if new mail arrived, in the interest of robustness. To do so would be a useful enhancement.)
