If that's insufficient, then you can address the sort of issue you're keying on.
SPAMASSASSIN SCORES LICENSE
Use Razor for fuzzy matching (see also Installing Razor) if the license works for you.Bayes in SpamAssassin is another must-have, though it requires training.DNS Blocklists, including DNSBLs & URIBLs, are a necessity set them up before all else.Other user_prefs file options can be found in the Mail::SpamAssassin::Conf man page or at Mail::SpamAssassin::Conf on the SpamAssassin website.You can use SpamAssassin to penalize mail received within certain hours, but it's messy.īefore we start, verify that SA's primary defenses are properly set up: Let's say that you receive several newsletters from a company whose email addresses all end with You can whitelist all of those at once with the following directive:įor reference, here are the default settings we use for the Department:Īdd_header all Status _YESNO_, score=_SCORE_ required=_REQD_ tests=_TESTS_ autolearn=_AUTOLEARN_ version=_VERSION_ Whitelist_from can whitelist entire domains, if you want. If often gets flagged as spam, you can whitelist her with the following line in your ~/.spamassassin/user_prefs file: You do this with the whitelist_from configuration directive. If that happens frequently to the same sender, you can whitelist that sender's email address to tell SpamAssassin that email from that person or organization should never be considered spam. Sometimes SpamAssassin will flag a message as spam even if it's not. Prevent Certain Email Addresses from Being Considered Spam To set your threshold to 5.3, put the following in your ~/.spamassassin/user_prefs file: Thresholds can be decimal numbers, so you can use, say, 5.3 if you want. Some people have good results with thresholds as low as 2.
The most common threshold for SpamAssassin is 5. The default value for the CS mailserver is 7, which is a very conservative setting-it's pretty unlikely to flag something as spam when it's not, but it also lets a fair amount of spam in untagged. The most common thing to customize is your spam score threshold. To create an empty config file, from a command prompt on one of our Linux clients, run the following commands: You can use that file to customize SpamAssassin's behavior for your messages. SpamAssassin uses a configuration file in your home directory (on our Linux clients) to supplement its Department-wide configuration.
SPAMASSASSIN SCORES HOW TO
The Filtering Spam with Procmail page describes how to automatically filter messages that have been flagged as spam. The SpamAssassin page describes what is done by default to spam-flagged messages. Any message whose overall score is equal to or greater than 7 is flagged as spam. SpamAssassin's default rule scores have been chosen based on experience with large quantities of both spam and non-spam messages.īy default, the CS Department uses a threshold of 7 for its spam classification. Some rules have negative scores, indicating that messages with those features are probably not spam. It considers each rule in turn and if it determines that a rule applies to or matches the message, then that rule's score is added to the message's overall score. SpamAssassin uses a set of rules that control how it scores each message.
0 kommentar(er)
