bionnh.blogg.se - Spamassassin auto whitelist

The end user is allowed to create his or her own spam checking rules if certain conditions apply. If a mail client has issues with divided headers, this parameter can be adjusted. In the miscellaneous category, fold_headers controls whether the headers that SpamAssassin adds are broken up (the default) or kept as one single long line. Rewrite_header (default: no default)ĭescribe SYMBOLIC_TEST_NAME description. Message tagging and header processing options. The options in Figure 3.9 control how headers are added to spam messages and header processing. Whitelist_allows_relays settings are a matter of personal preference and should be set as the user and administrator see fit. The settings in Figure 3.8 control how SpamAssassin processes and manages whitelists and blacklists as well as the auto-whitelisting feature. If it is too conservative, letting a lot of spam get through, adjust it downward. If you feel SpamAssassin is being too aggressive and creating lots of false positives, adjust the score threshold upward. This value can be adjusted higher or lower, depending upon the point at which you want SpamAssassin to consider a message to be spam. The required_score defines what SpamAssassin considers to be spam. The scoring keywords define what is to be considered spam and the scores assigned by rules (see Figure 3.7). Under the unprivileged class of configuration keywords available to anyone, the available options can be broken down as follows: Scoring Please consult Appendix E for a complete list and description of available configuration options for all three classes of keywords (global, administrator permitted, and administrator only). Spamd users are not allowed to change the privileged files unless the administrator has set allow_user_rules to 1.

Users running spamassassin from their procmailrc or forward files.

The administrator via the system-wide /etc/mail/spamassassin file.

The following classes of users are allowed to manipulate the privileged commands: Settings that can only be changed by the SpamAssassin administrator in local.cf

Options that are changeable with permission of the SpamAssassin administrator (if allow_user_rules is enabled).

Those that can be changed globally, by the user and/or system-wide (in other words, both user_prefs and local.cf).

The three classifications of keywords are as follows: spamassassin)Ĭonfiguration settings come in different classes.

Local user_prefs file (user's home directory, in a directory called.

Local rules directory, in alphabetic order (by default /etc/mail/spamassassin).

SpamAssassin default rules directory, in alphabetic order (defaults to /usr/share/spamassassin).

So, it is important to know that the files are processed in this order:

You need to be aware that the SpamAssassin rule processing is "last touched wins." In other words, the last setting is the one that is used. This makes integration with large mail systems easier. Also, with the virtual support available within spamd, user preferences can be located in a variable location, depending upon the mail account's domain and/or username. The ability for individual users to have their own user_prefs is a tunable parameter. The individual user configuration file is called user_prefs and is normally located in the user's home directory in the.

You should not place configuration files in /usr/share/spamassassin, as those files may get deleted during future SpamAssassin upgrades. The site-wide configuration is by convention called local.cf and should be placed in /etc/mail/spamassassin. cf extension are read in alphabetically at spamassassin startup time. The SpamAssassin configuration files live by default in /usr/share/spamassassin and /etc/mail/spamassassin. "SpamAssassin Configuration File." Figures 3.7– 3.15 and 3.17 are based on information from. A complete description of all configuration parameters is contained in Appendix E. Due to the large number of configuration parameters available, only highlights of the configuration files are presented here. SpamAssassin can be run with the as-shipped configuration files, requiring little or no change. Learn More Buy SpamAssassin Configuration Files Slamming Spam: A Guide for System Administrators