Philip explained to Trevor about locking on implicit delivery to $DEFAULT
when procmail falls off the end of /etc/procmailrc,
| That comment is inaccurate in two ways:
| 1) if DEFAULT is a maildir, MH, 'directory' folder or '|', then procmail
| won't use a locallockfile, and
It shouldn't if DEFAULT is /dev/null either.
| 2) it doesn't use or conflict with the LOCKFILE variable: procmail can
| hold two separate lockfiles, one using LOCKFILE and one using a
| locallockfile on a recipe or implicity when delivering to $DEFAULT.
It's inaccurate in three ways:
3) While there is implicit delivery to $DEFAULT when procmail falls off the
end of ~/.procmailrc or an rcfile named on the command line (or a SWITCHRC
on the same level), that isn't the case for the end of /etc/procmailrc. At
the end of /etc/procmailrc, procmail moves to the recipient's personal
rcfile (named $HOME/.procmailrc unless you took the unusual step of changing
the source code). If that file is nonexistent or unusable, only then would
procmail do default delivery after finishing /etc/procmailrc.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail