sagerest.blogg.se

Zimbra spamassassin configuration
Zimbra spamassassin configuration













The second score is used when Bayes is disabled, but network tests are enabled (score set 1). The first score is used when both Bayes and network tests are disabled (score set 0). If four valid scores are listed, then the score that is used depends on how SpamAssassin is being used. If only one valid score is listed, then that score is always used for a test. SYMBOLIC_TEST_NAME is the symbolic name used by SpamAssassin for that test for example, 'FROM_ENDS_IN_NUMS'. Scores can be positive or negative real numbers or integers. score SYMBOLIC_TEST_NAME n.nn Īssign scores (the number of points for a hit) to a given test. This option was previously known as required_hits and that name is still accepted, but is deprecated. It is not recommended to automatically delete or discard messages marked as spam, as your users will complain, but if you choose to do so, only delete messages with an exceptionally high score such as 15.0 or higher. 5.0 is the default setting, and is quite aggressive it would be suitable for a single-user setup, but if you're an ISP installing SpamAssassin, you should probably set the default to be more conservative, like 8.0 or 10.0. Set the score required before a mail is considered spam. SCORING OPTIONS required_score n.nn (default: 5) The following options can be used in both site-wide ( local.cf) and user-specific ( user_prefs) configuration files to customize how SpamAssassin handles incoming email messages. Test names ("SYMBOLIC_TEST_NAME") can only contain alphanumerics/underscores, can not start with digit, and must be less than 128 characters. Where appropriate below, default values are listed in parentheses. Whitespace in the files is not significant, but please note that starting a line with whitespace is deprecated, as we reserve its use for multi-line rule definitions, at some point in the future.Ĭurrently, each rule or configuration setting must fit on one-line multi-line settings are not supported yet.įile and directory paths can use ~ to refer to the user's home directory, but no other shell-style path extensions such as globing or ~user/ are supported. NOTE: if the # character is to be used as part of a rule or configuration option, it must be escaped with a backslash. The # character starts a comment, which continues until end of line. The following web page lists the most important configuration settings used to configure SpamAssassin novices are encouraged to read it first: FILE FORMAT SpamAssassin is configured using traditional UNIX-style configuration files, loaded from the /usr/share/spamassassin and /etc/mail/spamassassin directories. Lang pt_BR report O programa detetor de Spam ZOE DESCRIPTION Lang es describe FROM_FORGED_HOTMAIL Forzado From: simula ser de Header FROM_HAS_MIXED_NUMS From =~ FROM_HAS_MIXED_NUMS From: contains numbers mixed in with letters

zimbra spamassassin configuration

1618/iĭescribe PARA_A_2_C_OF_1618 Claims compliance with senate bill 1618 Mail::SpamAssassin::Conf - SpamAssassin configuration file SYNOPSIS # a commentįull PARA_A_2_C_OF_1618 /Paragraph. RULE DEFINITIONS AND PRIVILEGED SETTINGS.















Zimbra spamassassin configuration