SAproxy 1.2 uses 2.55. I'd suggest than Dan upgrade to SAproxy 1.2, of
course.
--
I just downloaded, but have not installed yet. maybe today.
In terms of writing new rules, the best place to begin is Matt Kettler's
rule writing guide. Is there a permanent URL for that? Maybe we can
add a li
Tony Earnshaw wrote:
Dan Baker wrote:
I downloaded the "latest" from SAproxy
the header that comes thru says:
X-Spam-Checker-Version: SpamAssassin 2.52-cvs (1.174.2.7-2003-03-20-exp)
"SpamAssassin 2.52-cvs". Here I'm absolutely stymied. There was never a
2.52-cvs
Tony Earnshaw wrote:
> one thing I noticed is that for messages that are enc-64 , it seems
> that other tests are NOT run on the decoded message. I'd suggest
> decodeding and then running all the regular tests OR if there is no
> plain or html message and its only enc-64, chances are 99% that
Tony Earnshaw wrote:
Simon Byrnand wrote:
Well, if you think other tests are not being run on base-64 encoded
messages, then you may have found a bug, because all the normal tests,
including bayes are supposed to run on the decoded text. (AFAIK)
People who (normally) are so dense that they refus
I'm having great luck with spamassassin... a few things slip thru of
course, and I wanted to post in case it gives developers a good idea.
one thing I noticed is that for messages that are enc-64 , it seems that
other tests are NOT run on the decoded message. I'd suggest decodeding
and then run
