![]() ![]() Spam is a dynamic, not a static, problem, and spammers usually respond very quickly and cleverly to countermeasures of any kind. The proportion of email advertising messages can be greater than 50 percent, forcing employees to check every piece of email and manually dump at least every second message in the Trash. Policies can be applied on both mail servers and later using the user's own mail user-agent application.Spam in your Inbox at home is a nuisance you can hardly avoid, but what is merely irritating at home is a genuine problem in the business world. Once classified, site and user-specific policies can then be applied against spam. Easy Configuration: SpamAssassin requires very little configuration you do not need to continually update it with details of your mail accounts, mailing list memberships, etc.The Mail::SpamAssassin classes can be used on a wide variety of email systems including procmail, sendmail, Postfix, qmail, and many others. Flexible: SpamAssassin encapsulates its logic in a well-designed, abstract API so it can be integrated anywhere in the email stream.Easy to extend: Anti-spam tests and configuration are stored in plain text, making it easy to configure and add new rules.Free software: it is distributed under the same terms and conditions as other popular open-source software packages such as the Apache web server.This makes it harder for spammers to identify one aspect which they can craft their messages to work around. Wide-spectrum: SpamAssassin uses a wide variety of local and network tests to identify spam signatures.:Happy Birthday! Apache SpamAssassin turned 18. If you do not update to 3.4.2 or later, you will be stuck at the last ruleset with SHA-1 checksums. ![]() *** On March 1, 2020, we will stop publishing rulesets with SHA-1 checksums.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |