MaestroPanel SpamAssassin Configuration File

local.cf

#
# MaestroPanel SpamAssassin Configuration File
#
###########################################################################
version_tag maestropanel
rewrite_header Subject *****SPAM*****
report_safe 0
required_score 5.0

use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1

skip_rbl_checks 1
rbl_timeout 12
allow_user_rules 0

ok_languages all
ok_locales all

#whitelist_from *@domain.com
#whitelist_from *@domain.net

#blacklist_from *@domain.cool
#blacklist_from *@domain.info

#   Set headers which may provide inappropriate cues to the Bayesian
#   classifier
#
# bayes_ignore_header X-Bogosity
# bayes_ignore_header X-Spam-Flag
# bayes_ignore_header X-Spam-Status


ifplugin Mail::SpamAssassin::Plugin::Shortcircuit
#
#   default: strongly-whitelisted mails are *really* whitelisted now, if the
#   shortcircuiting plugin is active, causing early exit to save CPU load.
#   Uncomment to turn this on
#
# shortcircuit USER_IN_WHITELIST       on
# shortcircuit USER_IN_DEF_WHITELIST   on
# shortcircuit USER_IN_ALL_SPAM_TO     on
# shortcircuit SUBJECT_IN_WHITELIST    on

#   the opposite; blacklisted mails can also save CPU
#
# shortcircuit USER_IN_BLACKLIST       on
# shortcircuit USER_IN_BLACKLIST_TO    on
# shortcircuit SUBJECT_IN_BLACKLIST    on

#   if you have taken the time to correctly specify your "trusted_networks",
#   this is another good way to save CPU
#
# shortcircuit ALL_TRUSTED             on

#   and a well-trained bayes DB can save running rules, too
#
# shortcircuit BAYES_99                spam
# shortcircuit BAYES_00                ham

endif # Mail::SpamAssassin::Plugin::Shortcircuit