> IIRC, that serves a different purpose, specifically preventing
> multiple popper processes from running simultaneously. The
> /var/mail/username.lock or /var/spool/mail/username.lock file is used
> to prevent concurrent updates to the mailspool by popper and some other
> process such as mail delivery. The latter is the shared locking
> mechanism that Randall and I referred to.
OK!. So then I should be safe upgrading to
procmail 3.15.1 using user.lock in /var/spool/mail, while still
running qpopper 2.5.2? That will give me more time to
study the 4.0.3 manual etc.
Homer
