![]() Sty 17 13:00:47.226 dbg: generic: Perl 5.020002, PREFIX=/usr, DEF_RULES_DIR=/usr/share/spamassassin, LOCAL_RULES_DIR=/etc/mail/spamassassin, LOCAL_STATE_DIR=/var/lib/spamassassin Sty 17 13:00:47.225 dbg: logger: logging level is DBG Sty 17 13:00:47.225 dbg: logger: adding facilities: all # and a well-trained bayes DB can save running rules, tooĮndif # Mail::SpamAssassin::Plugin::Shortcircuit # if you have taken the time to correctly specify your "trusted_networks", # the opposite blacklisted mails can also save CPU # shortcircuiting plugin is active, causing early exit to save CPU load. # default: strongly-whitelisted mails are *really* whitelisted now, if the Ifplugin Mail::SpamAssassin::Plugin::Shortcircuit # Some shortcircuiting, if the plugin is enabled # them to UTF-8 before the text is given over to rules processing. ![]() # Whether to decode non- UTF-8 and non-ASCII textual parts and recode ![]() # Set headers which may provide inappropriate cues to the Bayesian # Bayesian classifier auto-learning (default: 1) # Set the threshold at which a message is considered spam (default: 5.0) # Set file-locking method (flock is not safe over NFS, but is faster) # Set which networks or hosts are considered 'trusted' by your mail # modifying the original message (0: off, 2: use text/plain instead) # Save spam messages as a message/rfc822 MIME attachment instead of # Add *****SPAM***** to the Subject header of spam e-mails # Only a small subset of options are listed below # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be # This is the right place to customize your installation of SpamAssassin. => /etc/mail/spamassassin/v320.pre /etc/mail/spamassassin/v330.pre /etc/mail/spamassassin/v340.pre /etc/mail/spamassassin/v341.pre local.cf <= Loadplugin Mail::SpamAssassin::Plugin::DKIM # renders the DomainKeys plugin redundant. What am I not understanding? Thank you for the help.=> /etc/mail/spamassassin/customrules.pre /etc/mail/spamassassin/init.pre /etc/mail/spamassassin/local.cf /etc/mail/spamassassin/sa-update-keys /etc/mail/spamassassin/v310.pre /etc/mail/spamassassin/v312.pre version 0.20 or later is installed, this So something is wrong! The wiki says edit /opt/zimbra/data/spamassassin/localrules/salocal.cf but the top of that files says not to. URIBL_BLOCKED=0.001] autolearn=no autolearn_force=noīut I also noticed it loses my changes to that salocal.cf after I reboot. X-Spam-Status: No, score=2.679 tagged_above=-10 required=4.8 This is the supported location for doing customizations of SpamAssassin for ZCS 8.5 and later."Īnd restart zimbra when spam that is flagged with BAYES_50 it only gives it a score of 0.8. sausers.cf is migrated to the /opt/zimbra/data/spamassassin/localrules directory. So if I update a BAYES rule("score BAYES_50 0 0 2.0 2.8") in /opt/zimbra/data/spamassassin/localrules/salocal.cf like this says hereįor ZCS 8.5, Spamassassin layout has been corrected as per the SpamAssassin developers. I linked to that page above, but like I said above.those settings aren't sticking for me. opt/zimbra/data/spamassassin/localrules/salocal.cf So where should I change the rules? I'm assuming if I edit /opt/zimbra/data/spamassassin/state/3.004000/updates_spamassassin_org/50_scores.cf directly I could get my scores to update and mark spam the way I want, but that doesn't seem correct.Ī. /opt/zimbra/data/spamassassin/state/3.004000/updates_spamassassin_org/50_scores.cfĬ. This page says that I should edit /opt/zimbra/data/spamassassin/localrules/salocal.cf, but if I do that my changes don't stick. That almost looks like it is an update to the spamassassin rules but didn't get imported in. It is still using the default and it looks like it is pulling it /opt/zimbra/data/spamassassin/state/3.004000/updates spamassassin org folder. For example I change the default BAYES_99 level to 4.0. My problem is it isn't pulling the custom rules. I am using 8.5 and have been placing my custom spamassassin rules in /opt/zimbra/conf/salocal.cf.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |