PBleickardt <wbleickardt(_at_)monmouth(_dot_)com> writes:
No, I don't have verbose on...
I figured what the problem was:
/var/spool/mail was owned by root:root
When I changed its owner to contact:contact, procmail honored the
contact.lock file.
But I really don't want /var/spool/mail to be owned by contact! And what if
I need to lock other spoolfiles. What is the solution to this problem?
Either a) the mailspool needs to be world writable; or b) the mailspool
needs to be group writable and procmail setgid to the group of the
spool. Otherwise, it doesn't have enough privilege to create or remove
the lockfile, even if it's setuid root (it gives up it root privileges
before it starts parsing the user's .procmailrc).
Philip Guenther