1 # This is the right place to customize your installation of SpamAssassin.
3 # See 'perldoc Mail::SpamAssassin::Conf' for details of what can be
6 # Only a small subset of options are listed below
8 ###########################################################################
10 # A 'contact address' users should contact for more info. (replaces
11 # _CONTACTADDRESS_ in the report template)
12 # report_contact youremailaddress@domain.tld
15 # Add *****SPAM***** to the Subject header of spam e-mails
17 # rewrite_header Subject *****SPAM*****
20 # Save spam messages as a message/rfc822 MIME attachment instead of
21 # modifying the original message (0: off, 2: use text/plain instead)
26 # Set which networks or hosts are considered 'trusted' by your mail
27 # server (i.e. not spammers)
29 # trusted_networks 212.17.35.
32 # Set file-locking method (flock is not safe over NFS, but is faster)
37 # Set the threshold at which a message is considered spam (default: 5.0)
42 # Use Bayesian classifier (default: 1)
47 # Bayesian classifier auto-learning (default: 1)
52 # Set headers which may provide inappropriate cues to the Bayesian
55 # bayes_ignore_header X-Bogosity
56 # bayes_ignore_header X-Spam-Flag
57 # bayes_ignore_header X-Spam-Status
59 # Location of bayes data
60 #bayes_path /var/local/lib/spamd/bayes
62 # Fix bayes permissions
69 # Whether to decode non- UTF-8 and non-ASCII textual parts and recode
70 # them to UTF-8 before the text is given over to rules processing.
74 # Textual body scan limit (default: 50000)
76 # Amount of data per email text/* mimepart, that will be run through body
77 # rules. This enables safer and faster scanning of large messages,
78 # perhaps having very large textual attachments. There should be no need
79 # to change this well tested default.
81 # body_part_scan_size 50000
83 # Textual rawbody data scan limit (default: 500000)
85 # Amount of data per email text/* mimepart, that will be run through
88 # rawbody_part_scan_size 500000
90 # Some shortcircuiting, if the plugin is enabled
92 ifplugin Mail::SpamAssassin::Plugin::Shortcircuit
94 # default: strongly-whitelisted mails are *really* whitelisted now, if the
95 # shortcircuiting plugin is active, causing early exit to save CPU load.
96 # Uncomment to turn this on
98 # SpamAssassin tries hard not to launch DNS queries before priority -100.
99 # If you want to shortcircuit without launching unneeded queries, make
100 # sure such rule priority is below -100. These examples are already:
102 # shortcircuit USER_IN_WHITELIST on
103 # shortcircuit USER_IN_DEF_WHITELIST on
104 # shortcircuit USER_IN_ALL_SPAM_TO on
105 # shortcircuit SUBJECT_IN_WHITELIST on
107 # the opposite; blacklisted mails can also save CPU
109 # shortcircuit USER_IN_BLACKLIST on
110 # shortcircuit USER_IN_BLACKLIST_TO on
111 # shortcircuit SUBJECT_IN_BLACKLIST on
113 # if you have taken the time to correctly specify your "trusted_networks",
114 # this is another good way to save CPU
116 # shortcircuit ALL_TRUSTED on
118 # and a well-trained bayes DB can save running rules, too
120 # shortcircuit BAYES_99 spam
121 # shortcircuit BAYES_00 ham
123 endif # Mail::SpamAssassin::Plugin::Shortcircuit
125 # hcoop-change: use local caching nameserver for RBL