Glen asked,
| I'm receiving the following error message in one of my $HOME/.procmail/log
| files:
|
| procmail: Couldn't determine implicit lockfile from
| "/usr/local/bin/listserve.cgi"
|
| Any thought as to why I'm receiving this and what I need to do to correct
| it?
When you ask procmail to use a local lockfile on a recipe (a second colon
on the colon line), it needs a name for the local lockfile.
If you have a name for the local lockfile to the right of that second colon,
procmail uses that name.
But if you have nothing (or only a comment) to the right of the second colon,
procmail has to figure out a name for the local lockfile on its own. If the
action of the recipe is to save to a folder, procmail adds $LOCKEXT (usually
".lock") to the full pathname of the folder to get a name for the local
lockfile. If the action is to pipe to a program, and there is an append
redirector (">>") on the action line, procmail adds $LOCKEXT to the first
word after the append redirector to get a name for the local lockfile.
Usually you don't have to supply a name, because procmail will pick the best
possible name on its own.
However, if you ask for a local lockfile, you don't supply a name for it on
the colon line, and procmail can't infer one from the action line either, you
get that error message: you neither told procmail a name for the local lock-
file nor gave it anything to guess from.
There are two ways to fix it: if the action line really needs a local
lockfile (it might not), put a name for it to the right of the second colon
on the colon line. If the action line doesn't need a local lockfile after
all, get rid of the second colon.