5/3/2023 0 Comments Spamassassin auto whitelist![]() 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. 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. 4 Prevent Certain Email Addresses from Being Considered Spamįor an overview of how we use SpamAssassin in our department, please first read our SpamAssassin article.New: Retriving SQL prefs from mySQL DB stops shortly after spamd start.Retriving SQL prefs from mySQL DB stops shortly after spamd start.New: make spamd debugging easier bugzilla-daemon.New: whitelist_from_rcvd doesn't work with numeric IPs bugzilla-daemon.proposed updates for spamc "make" system bugzilla-daemon.hit-frequencies performance improvements bugzilla-daemon.New: put in default timeout for rbl tests bugzilla-daemon.New: ()'s in rewrite_header Subject are changed to 's bugzilla-daemon.()'s in rewrite_header Subject are changed to 's bugzilla-daemon.convert Razor, Pyzor, and DCC to plug-in(s) bugzilla-daemon.Bad DNS lookups (spamassassin is looking up domains with a ) bugzilla-daemon.New: Rule submission, subject rule: dollars only bugzilla-daemon.Re: CPU over loaded Alexander Litvinov.New: mass-check -net doesn't run to completion (process hangs) bugzilla-daemon.mass-check -net doesn't run to completion (process hangs) bugzilla-daemon.New: pyzor check timed out after 10 secs (Bad file descriptor) bugzilla-daemon.spamc tests skipped under Windows unless test started in t/ directory bugzilla-daemon.New: Can't call SpamAssassin->finish(), multiple finish() errors bugzilla-daemon.New: Fix "oops! still tied to bayes DBs, untie'ing" with compile_now bugzilla-daemon.spamd processes get stuck, eating all processor time bugzilla-daemon.Re: Detecting Phishers is not working.Fix "oops! still tied to bayes DBs, untie'ing" with compile_now bugzilla-daemon.New: spamd children should terminate after some timeout limit bugzilla-daemon.spamd children should terminate after some timeout limit bugzilla-daemon.Re: Metting Justin, Daniel and Theo Jeff Chan.Metting Justin, Daniel and Theo Jeff Chan. ![]()
0 Comments
Leave a Reply. |