[EMAIL PROTECTED] wrote:
I've been using Messagewall for a while now, and I decided to throw
SpamAssassin into the mix. Messagewall is great, but it's not dynamic
enough.
Problem is that I eventually want messagewall to tag messages only, then
pass them on to SA.
Messagewall always adds the header "X-MessageWall-Score: <score>
(<host.domain.tld>)".
I'm doing something similar, using bogofilter to cross-check SA scoring.
Just make sure you add a "bayes_ignore_header X-MessageWall-Score" to
your SA config if you're using bayes, lest it learn to associate that
header (regardless of score) with spam.
I want to write a rule for SpamAssassin that
basically says, "if <score> is greater than or equal to 15, then it's a
match." Note that <score> can be more than two digits.
This is how far I've gotten in local.cf:
header MW_SPAM X-MessageWall-Score: =~ /^[>=15].*/
score MW_SPAM 1.00
Er, hmm. How downright clever of you! I pass incoming messages through
virus scanning and bayes scripts before spamassassin, but hadn't thought
about letting good ol' spamassassin do all that hard math stuff for me.
And it opens up possibilities with metas. Not to mention simplifying
procmailrc, and scoring recipes.
Good stuff.
- Bob
