From: Claus Atzenbeck
Sent: Monday, January 10, 2005 8:36 AM
[...]
******************************
:0 fwh:
* ^X-Spambayes-Classification.*spam
| formail -i "X-Spam-Info: [cumulus] found pre-marked spam
through X-Spambayes-Classification (spam)"
******************************
What this recipe simply should do is to add a X-Spam-Info line iff there
is a X-Spambayes-Classification in the head that includes "spam".
I get the following error messages:
procmail: Couldn't determine implicit lockfile from "formail"
procmail: Missing action
Any idea what might be wrong?
- the short answer is this is a 'filtering recipe', and generally there is
no
lockfile needed. So, drop the trailing ':' that follows 'fwh'.
- the longer answer is the trailing colon tells procmail to use/create a
lock file.
When you don't supply an explicit file name, procmail has to try and guess
an appropriate lock file. Here's what 'man procmailrc' has to say:
Local lockfile
If you put a second (trailing) ':' on the first recipe line, then
proc-
mail will use a locallockfile (for this recipe only). You can
option-
ally specify the locallockfile to use; if you don't however,
procmail
will use the destination filename (or the filename following the
first
'>>') and will append $LOCKEXT to it.
There's also a global lock file which can be specified via the LOCKFILE
variable. This has more advanced uses, and is best learned another day.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail