> I have made
>
> spamassassin -D --lint
>
> but i got the warnings in the attached file.
Are you running German-language rules on 3.0.x? If so this is
(unfortunately) expected.
If you are only running English-language rules files, then this would
probably indicate that you had rules from 2.6x on a 3.x SA install.
> About the rulesets in rulesemporium.com what can you suggest for me?
I would suggest at least the "0" files for you, and probably the "1" files.
I suspect you get German-language email, and the SARE rules are really only
checked thoroughly aginst English. So there is a possibility that you might
get some FPs in other languages. You should watch your mail and see if you
are getting FPs, and if necessary remove an optional ruleset or rescore some
of the rules.
debug: is Net::DNS::Resolver available? no
debug: is DNS available? 0
You are not running network tests. If at all feasible you should enable
these tests, they will catch a ton of your spam.
debug: bayes: Not available for scanning, only 1 spam(s) in Bayes DB < 200
You have Bayes enabled, but you have not yet fed it at least 200 each hams
and spams, so it is not operating yet. When you feed Bayes what it needs it
will start helping too.
debug: AWL active, pre-score: -1.053, autolearn score: -1.053, mean: undef,
debug: Post AWL score: -1.053
You fed in a spam, but AWL believes this is a ham, and is happy with a
negative score. This means your AWL database is corrupted, and will not be
helping you. You should turn AWL off until you get your basic problems
fixed, clear the current AWL database, and only turn it back on (if you want
it at all) after you have the rest of the stuff working. In the mean time
it is likely to hurt.
debug: tests=ALL_TRUSTED,MISSING_DATE,MISSING_SUBJECT,NO_REAL_NAME
Here is a BIG problem! You got an ALL_TRUSTED on this spam. Assuming you
fed in a spam that came from outside and the headers are still there showing
that, it shoudl NEVER get an ALL_TRUSTED indication. This results in a
negative score, being added to the total, and in this case is probably
responsible for the major problems here. You MUST set trusted_networks
correctly.
The only rules that fired to indicate this was spam were the other three
rules shown above. These have fairly small scores. If you had the SARE
rules then there is a good chance this might have been caught as spam if
ALL_TRUSTED hadn't fired. If you had network tests enabled it almost
certainly would have been caught, especially along with SARE rules. And the
ALL_TRUSTED fix.
Loren
