Chris Arnold wrote:
> Warning: 2.63 is vulnerable to a DoS attack. Not to mention extraordinarily 
> old.
> If you're stuck in 2.6x, at least upgrade to 2.64:
> 
> http://www.cpan.org/modules/by-module/Mail/Mail-SpamAssassin-2.64.tar.gz
> 
> I am having a hrad time trying to upgrade to any version (i sent an email to 
> the list about this).
> 
> 
> NO!
> 
> All the files in /usr/share/spamassassin will be parsed and enabled by 
> default.
> 
> This directory contains the "default" configuration for SA.
> 
> Anything in /etc/mail/spamassassin is present to over-ride the defaults. So, 
> for
> example, if you wanted to change the score of one of the default tests, you'd 
> do
> so by adding a score statement to your local.cf.
> 
> In general the way SA parses files handles duplicate settings by clobbering 
> the
> previous setting with the new one.
> 
> For SA 2.6x the parse order is:
> 
> /usr/share/spamassassin/*.cf (in alphabetical order)
> /etc/mail/spamassassin/*.cf (again, in alpha order)
> ~/.spamassassin/user_prefs
> 
> (newer versions start off with reading /etc/mail/spamassassin/*.pre first, but
> that only applies to SA 3.0.0 and newer)
> 
> OK, let me ask straight-out; it does not seem like anything is getting tagged 
> "spam" when coming from the dnsbl. And how do i append ***SPAM*** to the 
> header (i have rewrite_header set to 1 in local.cf, nothing is getting 
> rewritten). Thanks again

Well, first, rewrite_header is not a valid command in SA 2.63. It's
rewrite_subject in versions of SA older than 3.0.0. That said, it should be
enabled by default.


Second, just being listed in a single DNSBL is generally not sufficient to get a
message tagged as spam by SA. Take a look at the rule for that DNSBL, and it's
score. Unless it's score is higher than your required_hits it alone won't cause
a message to get tagged.

Third, be sure to run spamassassin --lint. This should run quietly, but if your
config has errors, it will complain when you run this check. (SA has no other
way of complaining about config errors, so do this here).

Reply via email to