This has been covered so many times on this list.

1:  if you're not on spamassassin 3.1.5 get it now, and run sa-update
(via a cron job daily, but test first with a manual sa-update -D)

2:  pop over to http://www.rulesemporium.com and get an appropriate
selection of their rules, and configure Rules du Jour (
http://www.exit0.us/index.php?pagename=RulesDuJour ) to download them
daily.

3:  don't forget the additional rules here:
http://www.rulesemporium.com/other-rules.htm
I've found Fred's header rules helpful

4:  add the ImageInfo plugin from
http://www.rulesemporium.com/plugins.htm

5:  if you want to be adventurous, make sure you have ImageMagick,
ImageMagick-perl and other prerequisites installed and use the FuzzyOCR
plugin ( latest version at http://www.joval.info/proj/FuzzyOcr.html ,
but see also http://wiki.apache.org/spamassassin/FuzzyOcrPlugin ).
The FuzzyOCR mailing list is very helpful too.

In my experience here a well-trained Bayes plus the various
RulesEmporium rulesets gets most of them.

Cheers,

Phil
--
Phil Randal
Network Engineer
Herefordshire Council
Hereford, UK  

> -----Original Message-----
> From: Dylan Bouterse [mailto:[EMAIL PROTECTED] 
> Sent: 02 October 2006 14:38
> To: users@spamassassin.apache.org
> Subject: Stock spam in images
> 
> I'm a newbie to the list and have been scanning recent posts to see if
> what I'm about to ask about has been covered but I haven't 
> seen anything
> yet.
> 
> Lately I have been getting more and more of the stock alert 
> spam but now
> all the good info is in an image and typically following the image is
> random text to fool the Bayesian filter. I think the random text thing
> has been covered here recently. It's frustrating when sa is giving a
> -1.6 (or so) score to these emails right off the bat. Quite a few of
> these aren't even getting spam headers because they aren't 
> scoring high
> enough. Is there some magical trick to help score these 
> messages higher?
> Maybe a future version of sa will incorporate an OCR module? :)
> 
> Dylan
> 

Reply via email to