Hi, >> After looking at it more closely, it's also only hitting bayes20 for >> you. Do the others also score so low? This hits bayes99 on my system. > > The ones that SA doesn't catch, yes, they are typically low. I have some > that are bayes50, some bayes20, some bayes00. Any that are bayes99 are > almost certainly in my spam folder and I'm typically not looking at them (I > don't have that much time to look at spam, so I prefer to look at FN rather > than TP).
I'd say if you have any that are hitting bayes20 or lower, your database is not working properly and you should probably start over. It seems that populating it further with ham and FNs won't eliminate the incorrect classification of the spam that's there already. I thought you may have manually modified the body because this looks unique: <x-html><!x-stuff-for-pete base= Do your other FNs have this? If so, you could consider generating a rule from it. Try running it as "spamassassin -t -D < sample > /tmp/sample.out 2>&1 Then go through /tmp/sample.out. You should see it processing the config files. Make sure it's including all the rules from your installation. You might also create a header or body rule to tag something unique: header MY_SUBJ_RULE Subject =~ /Mobility Solutions from Hoveround/i score MY_SUBJ_RULE 1.0 rawbody MY_BODY_RULE /Enjoy Life Again with Mobility Solutions/i score MY_BODY_RULE 1.0 >> It also hits the "LONGWORDS" rule and "MIME_NO_TEXT", pushing it over >> to be spam. Have you otherwise modified the body? ... > I'm not sure why those rules are hitting for you and not for me. I wonder > if something is misconfigured on my installation. I should disclose that my > installation is on a Parallels Pro Control Panel machine... PPCP ships with > an SA rpm, but I've updated it with the version from RPMforge > (spamassassin-3.3.1-3.el5.rf, which is the latest one on that repo). > sa-update is run nightly via cron. Search your installation and see if the two rules even exist on your system. # pwd /var/lib/spamassassin/3.003002/updates_spamassassin_org # grep LONGWORDS 20_body_tests.cf ... meta LONGWORDS (__LONGWORDS_A + __LONGWORDS_B + __LONGWORDS_C > 1) When running it in debug mode, you should see something like this: Jun 13 21:36:08.949 [1771] dbg: rules: ran body rule __LONGWORDS_B ======> got hit: "committees udometer forgets operated defoliated between choose indeed micromanagement " Regards, Alex
