At 2:43 PM -0400 7/10/02, Alan Brown wrote: > if user processes lock the spool in qpopper-compatible ways > then it will never gain the lock in the first place.
Depends on what you mean by "qpopper-compatible." If it uses dot-locks (which are usually what people mean by "qpopper-compatible"), then you have a problem if the user process graps the spool during the Qpopper session. On the other hand, if you mean that the user process creates a .user.pop file, then all will be well, since Qpopper and the user process will be mutually exclusive. > 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. With educated users, you can get away with a lot. > I ran qpopper in server mode for 8 years on a small ISP where users had > pine (tweaked to also set pop locks) It should be perfectly fine if pine is creating .user.pop files.
