![]() Things Ive tried: - Updated the local.cf file to change the score from 5.0 in there. No user has any user configuration file - I have ran the /scripts/restartsrvspamd command after every single change that I have made. If any of the score values are surrounded by parenthesis '()', then all of the scores in the line. Setting a rule's score to 0 will disable that rule from running. ![]() The fourth score is used when Bayes is enabled and network tests are enabled (score set 3). 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.ĭo 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. I am trying to update the requiredscore setting on SpamAssassin for all my users. The third score is used when Bayes is enabled and network tests are disabled (score set 2). Void, you did not mention the version of Zimbra that you're running. 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. 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. So any of your changes need to be backed up so you can easily rebuild them. cf files results in stuff you'll lose on every upgrade-none of it gets preserved. SpamAssassins default rule scores have been chosen based on experience with large quantities of both spam and non-spam messages. The local.cf file contains basic settings, like the score you must reach before a message is considered spam, what the subject line should be changed to if the.
0 Comments
Leave a Reply. |