>
> However in server mode, as discussed, qpopper will only lock at the
> beginning and end of the session, while first grabbing and later
> updating the spool file. It is therefore possible to get a valid lock
> in the middle of the POP session, perform operations on the spool while
> keeping it locked, write your updates back, unlock, and still end up
> with a corrupted spool when qpopper terminates - if the operations you
> performed were anything other than appending to the end of it. That's
> why server mode needs to be appropriately restricted.
OK, but if the machine is limited to qpopper reading mail and
procmail delivering mail, then we have the conditions you require, no?
Homer
