On Wed, 2010-04-28 at 12:38 -0400, Carlos Mennens wrote:
> I checked /etc/mail/spamassassin/local.cf just now and found only the
> following:
>
> required_hits 5
> report_safe 0
> rewrite_header Subject [SPAM]
>
> However I don't know if Amavisd-new is looking at local.cf because I
> show parameters in my amavisd.conf file for SpamAssassin:
>
> $sa_tag_level_deflt = -999.0; # add spam info headers if at, or
> above that level
> $sa_tag2_level_deflt = 5.0; # add 'spam detected' headers at that level
> $sa_kill_level_deflt = 8.0; # triggers spam evasive actions (e.g.
> blocks mail)
> $sa_dsn_cutoff_level = 10; # spam level beyond which a DSN is not sent
> $sa_quarantine_cutoff_level = 12; # spam level beyond which quarantine is off
> $penpals_bonus_score = 8; # (no effect without a @storage_sql_dsn database)
> $penpals_threshold_high = $sa_kill_level_deflt; # don't waste time on hi spam
>
These settings are for amavisd-new and not spamassassin. Amavisd-new is
the glue between your MTA and spamassassin (and virus scanners). Most
of the behavior of spamassassin is still controlled through the local.cf
(although some settings can be defined in both places and the
amavisd.conf file will take precedence).
> $sa_mail_body_size_limit = 400*1024; # don't waste time on SA if mail is
> larger
> $sa_local_tests_only = 0; # only tests which do not require internet
> access?
> [...]
> $sa_spam_subject_tag = '***SPAM*** ';
> $defang_virus = 1; # MIME-wrap passed infected mail
> $defang_banned = 1; # MIME-wrap passed mail containing banned name
> # for defanging bad headers only turn on certain minor contents categories:
> $defang_by_ccat{+CC_BADH.",3"} = 1; # NUL or CR character in header
> $defang_by_ccat{+CC_BADH.",5"} = 1; # header line longer than 998 characters
>
> When I get a spam message that was scored by SA, it says ***SPAM***
> and not [SPAM] so that leaves me to believe that SA parameters are
> being fed from amavisd.conf file. Does this make sense to you guys?
This is just the setting in amavisd.conf taking precedence. If you were
to comment out $sa_spam_subject_tag I *believe* the value in your
local.cf would then be used.
