jdow schrieb:

From: "Thomas Booms" <[EMAIL PROTECTED]>


Loren Wilton schrieb:

Well, header I have on detected spams like these (possibly I need to
reconfigure something) to get the above lists:

X-Spam-Status: No, score=-1.8 required=1.5 tests=BAYES_00,
DATE_IN_FUTURE_03_06 autolearn=ham version=3.0.4


This says that the message is NOT spam.  Bayes in particular is convinced
that it was ham, and has auto-learned it as such.  It looks like your
Bayes
database is corrupt and will need to be rebuilt at some point.

However, before doing that, we need to figure out why all this hit was
date-in-future.

I'm a little concerned that that initial Received header from Qmail may
be
keeping SA from analyzing the return headers.  This could case a lot fo
the
net tests to fail.  Hiwever, maybe that header is ok.  Others that know
more
about received headers than I do will look at it.

If that spam had been in English the body text would have nailed it.
"Greencard lottery" is pretty much a guaranteed spam indicator all by
itself.  This looks like a case where a few of the rules for these things
could profitably be translated to German, by someone that speaks both
languages.  (I don't, or I'd just do it.)

There is a good chance though that register-usa.com should have hit
SURBL.
This makes me think your net tests aren't working.  Since this is 3.0.4,
they should be by default.

Why don't you run "spamassassin --lint -D" and post the output.  My guess
is
you either have a problem with the Net::DNS version, or init.pre insn't
installed correctly.  (Of course you might be starting SA with the -L
parameter that disables net tests.)

      Loren





Well, here's the content of my init.pre and then the running
spamassassin task:

# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
# This file will be loaded before *all other* configuration files,
including
# the system configuration.  As such, it's a good place to set things that
# will affect how those files are parsed, like which plugins are loaded
# etc.
#

###########################################################################
# RelayCountry - add metadata for Bayes learning, marking the countries
# a message was relayed through
#
# loadplugin Mail::SpamAssassin::Plugin::RelayCountry

# URIDNSBL - look up URLs found in the message against several DNS
# blocklists.
#
loadplugin Mail::SpamAssassin::Plugin::URIDNSBL

# Hashcash - perform hashcash verification.
#
loadplugin Mail::SpamAssassin::Plugin::Hashcash

# SPF - perform SPF verification.
#
loadplugin Mail::SpamAssassin::Plugin::SPF

(I've never touched that file)

/usr/bin/perl -T -w /usr/bin/spamd -q -H /etc/mail/spamassassin
\_ spamd child
\_ spamd child
\_ spamd child
\_ spamd child
\_ spamd child

Contents of local.cf also matter. If you have DNS rules off or your
DNS misconfigured from what SA wants it isn't going to work well.

{^_^}




Here's the content of my local.cf:

rewrite_subject 1
report_safe 2
trusted_networks ****
user_scores_dsn DBI:mysql:****:****
user_scores_sql_username ****
user_scores_sql_password ****
user_scores_sql_custom_query SELECT preference, value FROM _TABLE_ WHERE username = _USERNAME_ OR username = '$GLOBAL' OR username = CONCAT('%',_DOMAIN_) ORDER BY username ASC
razor_config /etc/mail/spamassassin/.razor/razor-agent.conf
urirhssub       URIBL_BLACK  multi.uribl.com.        A   2
body            URIBL_BLACK  eval:check_uridnsbl('URIBL_BLACK')
describe        URIBL_BLACK  Contains an URL listed in the URIBL blacklist
tflags          URIBL_BLACK  net
score           URIBL_BLACK  3.0

urirhssub       URIBL_GREY  multi.uribl.com.        A   4
body            URIBL_GREY  eval:check_uridnsbl('URIBL_GREY')
describe        URIBL_GREY  Contains an URL listed in the URIBL greylist
tflags          URIBL_GREY  net
score           URIBL_GREY  1.0

The 1st 3 lines were added a few minutes ago.

Thomas

--
Booms EDV
- hosting & more -
Herrenstrasse 10
D-59073 Hamm

www.booms-edv.de
[EMAIL PROTECTED]

Reply via email to