[SOLVED] Anybody know how to change the Spam Assassin Score?

[void]

I have been running SpamAssassin for years, but the way it is integrated in to Zimbra is baffling me...

I have my /opt/zimbra/conf/spamassassin/local.cf set to:
required_score 5

and yet I get spam delivered to my inbox, with no subject line changed, that has
X-Spam-Status: No, score=0.9 tagged_above=-10 required=7


If the score is in excess of the required score, it should be tagged as spam, but it's not, Spamassassin thinks my requirement is 7.

I have changed the value to 5 in the following files:
/opt/zimbra/conf/spamassassin/10_default_prefs.cf
/opt/zimbra/conf/spamassassin/local.cf
/opt/zimbra/conf/salocal.cf.in
/opt/zimbra/conf/salocal.cf

How does one override the Zimbra default of 7?

Somebody has to know...

[void]

Still nothing huh?

Nobody here ever had to change this value or knows how?

[mrvanes]

Had the same problem. Combed the conf dir for string 6.6 and guess what? It's defined in amavisd.conf:

$sa_tag2_level_deflt = 6.6; # add 'spam detected' headers at that level

Cheers.
Martin

update: it's more complicated. amavisd.conf seems to be generated from amavisd.conf.in while the daemon is (re)started. amavisd.conf.in defines the line like this:

$sa_tag2_level_deflt = %%range VAR:zimbraSpamTagPercent 0 20%%; # add 'spam detected' headers at that level

This variable can be set in the admin interface under Global Settings AS/AV tab. So, in the end, it's less complicated than I thought

Default value is 33% (for crying out loud, why convert SA points to %?) which yields 6.6, so 100% is probably 20 (rounding down). If you want a spamassassin required_score of 5.0 you should fill in 25%.

I'm speeking for Zimbra 5.0RC2, btw.

[dwmtractor]

That required score is defined by a setting in your admin UI. Go to Global Settings, the AS/AV tab, and you'll see kill and tag percentages. The "Required" score is 20 times the percentage in that tag field. So for example, 20 * 35% (0.35) = 7. Change that to a lower number and you'll have a lower required score--I have mine set at 24% which results in a required score of 4.8.

Then of course you still have the issue of whether your messages are getting the kind of scores you want. This article has tons of options for tweaking to your heart's content. I'm partial to the RBLs and some of the customization to Bayes filtering because those two things have been helpful to me (well, that and killing off a few whitelists ) but there are lots of different approaches you can try.

Dan

[dwmtractor]

I should have added: editing any of the .cf files results in stuff you'll lose on every upgrade--none of it gets preserved. So any of your changes need to be backed up so you can easily rebuild them. I keep all my changes that must be done at the file level in local.cf so I don't have to restore multiple files/settings.

The nice thing about changing your tag/kill percent for overall score values is that this setting DOES survive upgrades and any other tweaking you do from within Zimbra. . .while manually-implemented settings can be overwritten depending upon the action you do.

void, you did not mention the version of Zimbra that you're running. There have been some bugs in prior versions that created some heartburn in this area--for example, if my memory serves version 4.5.7 had a buglet where any change to the spam settings in the UI wiped out any RBLs you had set from the command line.

Do a zmcontrol -v and paste the resulting string into the version field in your forum profile (and then update it whenever you upgrade) and people will be able to help you with version-specific joys & sorrows. . .

Cheers,

Dan

[void]

Ah thats what was thwarting me. I was GREPing everything for that dang setting using all the tricks I could think of... but alas it is set by that percentage in the admin panel according to that math you posted.

You win this time Math, but I'll be back!

Version for the curious:
Release 4.5.9_GA_1454.RHEL5_20071016194233 CentOS5 NETWORK edition


Thanks for the assistance on this. It is much appreciated.

[mmorse]

btw amavisd.conf.in would have shown the mappings...
zmprov gacf | grep Spam
would have given ya zimbraSpamKillPercent & zimbraSpamTagPercent