The Message-ID: header, though, often can have legit `$' chars in it.
I wanted to exclude that header. The following may or may not be
a bit sloppy (improvements solicited!); but it's what I came up with:
:0 i # two+ `!' or `$' symbols in headers . . .
* ! ^(Return-Path|Sender):.*list
* -175^0
* 100^1 [$!]
* -100^1 ^Message-ID:.*[$!]
{ do some other things if we're here }
So, I had a piece of mail come in that had two `$' chars in the
Message-ID: header. There were no other `!' or `$' signs in the
headers. The logs, though, showed a total score for this section
of -75, not -175! I don't understand how that could be.
Here is that section of the log (verbose format):
procmail: Match on ! "^(Return-Path|Sender):.*list"
procmail: Score: -175 -175 ""
procmail: Score: 200 25 "[$!]"
procmail: Score: -100 -75 "^Message-ID:.*[$!]"
Interesting. I don't understand this either ;-) The middle score
should be 100, not 200. Are you absolutely positive that no other
header except Message-ID matched [$!]? Have you tested the same
recipe with a Message-ID header that contains only one $ or ! ?
If such a message yields 100, you may have found a bug ...
John Summerfield writes:
[...]
Filtering on chars in message-id seems to me fraught with the risk of
mis-identifying legit mail as spam.
Yeah, but such is the risk of all filtering.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail