By the way, SpamAssassin on my receiving host pegged your
message as spam.
Pedro Santa wrote Monday, September 10, 2007 6:09 PM:
I simply don't understand. The Spam still escapes the filter. I've
caught a specific one to report here. A mail with "X-Spam-Level:
*******".
The recipe I'm using is the following:
:0
* ^X-Spam-Level: \*\*\*
{
SPAMLEVEL=" [SPAM 1]"
}
Here is the portion of the log of that mail:
(...)
procmail: No match on "^X-Spam-Level: \*\*\*"
I'm so so confused! I mean, to me all the recipes are pretty straight
forward. What I don't understand is why it doesn't match on
X-Spam-Level???
I will attach the message source so you can check that X-Spam-Level...
Works for me:
1:38pm [~/Mail] 526[0]> procmail -m DEFAULT=/dev/null VERBOSE=y pedro.rc
< messagesource.txt
procmail: [22704] Wed Sep 12 13:39:07 2007
procmail: Assigning "MAILDIR=."
procmail: Rcfile: "poop.rc"
procmail: Match on "^X-Spam-Level: \*\*\*"
procmail: Assigning "SPAMLEVEL= [SPAM 1]"
procmail: Assigning "LASTFOLDER=/dev/null"
procmail: Opening "/dev/null"
From - Mon Sep 10 16:57:49 2007
Subject: [GESTAO] ssielles
Folder: /dev/null
Are you sure the source had only one space before the first asterisk?
I suspect SpamAssassin is changing the spacing or it was a tab or
something -- your included source nothwithstanding. Try:
* ^X-Spam-Level:.*\*\*\*
dman
____________________________________________________________
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