Spamassassin score test4/20/2023 ![]() ![]() If after the modification, you can see this rule in many false negatives then you ll know it was a usefull RBL regarding your specific mail flow. If you want to disable a rule, set its score to 0.1 so that you can investigate later on. Adjusting these scores is a long and hard process we do for you but since yuor mailflow can be very specific, you can change these rules scores. Lowering the score of a SpamC rule may seem a good idea to avoid the specific false positive you just had but it may also suddently let a lot of spams get through. We strongly suggest to have a statistical approach of your issue. This documentation is most of the time used to adapt a rule s score : If you want to change a score per domain or even per user, you might want to read : Make a backup of the following file and then open it in a text editor: /etc/mail/spamassassin/local.cfĪdd your custom score configuration.This documentation aims to show you how to adapt a SpamC score for all domains. Login to the server via SSH as the root user. How to adjust the weight of a SpamAssassin Rule Once you know which rules are affecting your messages' scores, and what the existing default rule scores are, you can use the following procedure to alter the default scores for all messages server-wide.Īlso, keep in mind that each individual cPanel user has the ability to edit these default SpamAssassin scores for just their account with the steps in the following guide: var/lib/spamassassin/3.004004/updates_spamassassin_org/50_scores.cf var/lib/spamassassin/3.004004/updates_spamassassin_org/20_freemail.cfĭescribe FREEMAIL_FORGED_REPLYTO Freemail in Reply-To, but not From Searching configuration files for rule: FREEMAIL_FORGED_REPLYTO Paste or type a single SpamAssasin RuleID and press enter The following is an example output of the script if you were searching for the FREEMAIL_FORGED_REPLYTO rule. & : || echo "RuleID: $RULEID not found in any file" You would copy and paste the entire thing into the CLI:Įcho echo "Paste or type a single SpamAssasin RuleID and press enter" read RULEID echo echo "Searching configuration files for rule: $RULEID" echo find /var/lib/spamassassin /etc/mail/spamassassin -name "*.cf" | while read ruleConfigPath do awk -v RULEIDAWK="$RULEID" '$0~RULEIDAWK & (/^describe/ || /^score/) ' $ruleConfigPath done | grep -color=never. The following is a script that accepts a RULE ID and will search for the description and default scores for the rule. If you're not sure if this would be effective to resolve your issue in the first place, you can use the following guide to determine which rules are being applied to a specific message:īased on what you find with the steps in the above guide, you can see the existing rule scores by searching for them in the various locations of the source rule configurations. If you find that there are certain Spam assassin rules that are weighted too heavily, or are not weighted enough you may use the procedure in this guide to change them. The overall score is composed of the result testing the message against various rules that each assign their own sub-score. Spam Assassin determines whether or not a message is spam based upon the message's final calculated spam score. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |