I've done the preliminary work to integrate SpamAssassin tests in
dada_bridge pl -

The version with these changes is live and being used for this list,
but unfortunately, I can't enable it, as I get, "Out of Memory!"
errors when it is enabled I tried for a few hours to optimize the
dada_bridge pl plugin (with good success!), but nothing seemed to
sway the problem - SpamAssassin just may be a resource hog

So, I'm probably going to leave it in the plugin, but perhaps not
have it enabled Rob, I'll be contacting you shortly to see if I
can't get it to work with SpamAssassin 3 0 on your server :)

If you're curious on the changes, the newest dev version can be found
here:

<http://mojomail
cvs
sourceforge
net/mojomail/dada_mail_stable/dada/ 

plugins/dada_bridge pl?view=log&pathrev=dada_mail_2_10_9_maintenance- branch>

One thing that is puzzling me is when SpamAssassin is run on the
messages in the POP3 inbox -

When Dada Mail checks the POP3 account, the SpamAssassin specific
headers are not present, meaning, I have to run SpamAssassin
directly on the message in question But, when I check the POP3
account on my desktop computer using something like Apple's Mail app,
they turn up That's a little more voodoo than I can currently
handle :) The headers I'm talking about look sort of like this:

X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 3 1 0 (2005-09-13) on example com X-Spam-Level: ** X-Spam-Status: Yes, score=24 8 required=5 5
tests=BAYES_99,DATE_IN_PAST_96_XX, FORGED_YAHOO_RCVD,HELO_DYNAMIC_HCC,HELO_DYNAMIC_IPADDR2, HTML_IMAGE_ONLY_08,HTML_MESSAGE,HTML_SHORT_LINK_IMG_1,MIME_HTML_ONLY, SARE_UNF,URIBL_SC_SURBL autolearn=unavailable version=3 1 0 X-Spam-Report: * 4 1 HELO_DYNAMIC_HCC Relay HELO'd using suspicious hostname (HCC) * 3 8 HELO_DYNAMIC_IPADDR2 Relay HELO'd using suspicious hostname (IP * addr 2) * 2 0 DATE_IN_PAST_96_XX Date: is 96 hours or more before Received:
date * 1 8 FORGED_YAHOO_RCVD 'From' yahoo com does not match 'Received' * headers * 0 0 HTML_MESSAGE BODY: HTML included in message * 3 1 HTML_IMAGE_ONLY_08 BODY: HTML: images with 400-800 bytes of
words * 3 5 BAYES_99 BODY: Bayesian spam probability is 99 to 100% * [score: 1 0000] * 0 0 MIME_HTML_ONLY BODY: Message only has text/html MIME parts * 1 0 SARE_UNF RAW: SARE_UNF * 4 5 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist * [URIs: v1ckb1ke34 com] * 0 9 HTML_SHORT_LINK_IMG_1 HTML is very short with a linked image X-Spam-Help: For more information see http://support example com/antispam html

It's pretty easy to parse these sort of headers, and not have to call
SpamAssassin directly - if they'd only show

Oh well, more research to be done;