# This is the right place to customize your installation of SpamAssassin.
#
# See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
# tweaked.
#
# Only a small subset of options are listed below
#
###########################################################################

#   Add *****SPAM***** to the Subject header of spam e-mails
#
rewrite_header Subject [ SPAM ]


#   Save spam messages as a message/rfc822 MIME attachment instead of
#   modifying the original message (0: off, 2: use text/plain instead)
#
# report_safe 1
report_safe 0

#   Set which networks or hosts are considered 'trusted' by your mail
#   server (i.e. not spammers)
#
clear_trusted_networks
clear_internal_networks
trusted_networks !203.124.10.107 203.124.10/24 203.124.11/24 121.14.105/24
always_trust_envelope_sender 1

internal_networks !203.124.10.107 203.124.10/24 203.124.11/24 121.14.105/24

#   Set file-locking method (flock is not safe over NFS, but is faster)
#
# lock_method flock


#   Set the threshold at which a message is considered spam (default: 5.0)
#
required_score 5.0


#   Use Bayesian classifier (default: 1)
#
# use_bayes 1


#   Bayesian classifier auto-learning (default: 1)
#
# bayes_auto_learn 1

bayes_min_ham_num 20
bayes_path /var/backend/spam_pref/communilink.net/bayes

#   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


#   Some shortcircuiting, if the plugin is enabled
# 
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


###############################
# Overide the default rulesets
###############################
score ALL_TRUSTED -10
score FORGED_MUA_OUTLOOK 0.1
score RCVD_IN_BL_SPAMCOP_NET 3
score DEAR_SOMETHING 0.1
score KAM_MXURI 0.1
score TVD_PH_SUBJ_ACCOUNTS_POST 0.1
score FH_RELAY_NODNS 0.1
score DOS_OUTLOOK_TO_MX 0.1
score FILL_THIS_FORM_LONG 0.1
score DOS_OE_TO_MX 0.1
score FM_IS_IT_OUR_ACCOUNT 0.1
score STOX_REPLY_TYPE_WITHOUT_QUOTES 0.1
###############################

pyzor_options --homedir /etc/mail/spamassassin
allow_user_rules 1
whitelist_from @passgroup.com


trusted_networks !203.124.10.107 203.124.10/24 203.124.11/24 121.14.105/24
always_trust_envelope_sender 1   

internal_networks 203.124.10.44