On Sat, 29 Nov 2003, mairhtin wrote:
> procmail: Extraneous locallockfile ignored
That's coming from this line:
> :0:
The trailing colon means to use a lockfile, but your action (i.e., nested
recipes enclosed in braces) doesn't provide procmail with a filename that
it can use as the basis for a lockfile name.
> The recipie I put in was :
>
>
> :0:
> * \/To:.*
> {
> LOG=`formail -X "To:"`
> }
You're mixing your metaphors, so to speak, and getting both of them wrong
to boot. The above tells procmail: Begin a recipe using a lockfile (:0:)
which is triggered for headers matching the regular expression "/To:.*" (a
backslash is discarded when it is the first character of a condition line)
and on a match execute the additional recipes contained in the braces,
which in this case is an assignment to the LOG variable of the result of
using formail to extract the To: line.
You want either *only*
LOG=`formail -X "To:"`
(and nothing else), or you want
:0
* ^\/To:.*$
{
LOG="$MATCH"
}
which tells procmail: Begin a recipe with no lockfile, which is triggered
when an entire line in the header matches "To:.*", and on such a match
store in the MATCH variable (that's what the \/ means when it is NOT the
very first thing in the conditions) everything after the beginning of the
line up to and including the final newline (the $ sign) and execute the
additional recipies in the braces, which in this case is to assign the
previously-stored value of MATCH to the LOG variable.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
