Zhiliang asked,
| I have the following /etc/procmailrc working well to filter out "bad"
| mails for our site. However the only problem I cannot figure out is
| the lock - it always complains "cannot unlock ..." no matter how I
| change the lock file location. The lock file always has root as
| owner and permission as 400 -- isn't /etc/procmailrc executed by root?
Yes, it is, and you aren't removing the lockfile when you give up root
privileges at the end of /etc/procmailrc. So when procmail finishes and
is no longer root, it can't remove the lockfile.
Recommendation: remove the lockfile (by unsetting the LOCKFILE variable;
just put the word LOCKFILE alone on a line) somewhere inside /etc/procmailrc.
If the user has no ~/.procmailrc, procmail will try to secure a local
lockfile for delivery to $DEFAULT or $ORGMAIL (if they're plain files) and
the global lockfile will be unnecessary; if the user has a ~/.procmailrc,
then lockfiles for its code are the user's responsibility.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail