On Wed, 10 Jul 2002, Randall Gellens wrote: > Qpopper only locks the spool during initialization and at > termination; in between the spool is unlocked. In server mode, > Qpopper assumes that the only change to the spool that can occur > during the period is new mail delivery.
Yes, but if user processes lock the spool in qpopper-compatible ways then it will never gain the lock in the first place. Yes, I know there's a race condition there, but as long as users are educated/informed of the dangers of simultaneous access then they only have themselves to blame if their spool gets trashed. I ran qpopper in server mode for 8 years on a small ISP where users had pine (tweaked to also set pop locks) and only ever had corruption problems caused by old versions of qpopper vs eudora 2.*, not between qpopper and local access modes (the corruption occured on user accounts where the users didn't have the smarts or inclination to even know what Pine was). AB
