![]() ![]() Specifically, "*" and "?" are allowed, but all other metacharactersĪre not. Whitelist and blacklist addresses are now file-glob-style patterns,Īll work. Trouble, so it doesn't provide a shortcut around SpamAssassin. This way, if spammers impersonate them, they'll get into big ![]() Version_tag myrules1 # version=2.41-myrules1 Whitelist and blacklist options whitelist_from Used to specify addresses which send mail that is often tagged (incorrectly)Īs spam it also helps if they are addresses of big companies with lots Or your initials followed by a number which you increase with each A good choice for string is your last name You should include it when modify your ruleset, especially if you Version_tag string This tag is appended to the SA version in the X-Spam-Status header. Of SpamAssassin tries to read configuration from this file, it will Require_version n.nn Indicates that the entire file, from this line on, requires a certain version of SpamAssassin to run. How SpamAssassin handles incoming email messages. The following options can be used in both site-wide (" local.cf")Īnd user-specific (" user_prefs") configuration files to customize spamassassin located in every user's home-dir. User preferences are read from the file ~/.spamassassin/user_prefs, Summary of tests hit for standard report (for body reports)Ĭontents of the ' report_contact' setting Terse report of tests hits (for header reports) AWL=-3.0.)įull results for positive RBL queries in DNS URI format Tests hit separated by, (or other separator)Īs above, except with scores appended (eg. One * (use any character) for each score point (50 at most)Īutolearn status (" ham", " no", " spam") Optional, and the default is shown below. Some tags can take an argument (in parentheses). They will be replaced by the corresponding value when Tags The following "tags" can be used as placeholders in certain options Where appropriate, default values are listed in parentheses. Paths can use " ~" to refer to the user's home directory. Multi-line settings are not supported yet. Multi-line rule definitions, at some point in the future.Ĭurrently, each rule or configuration setting must fit on one-line Whitespace in the files is not significant, but please note that starting a line with whitespace is deprecated, as we reserve its use for The " #" character starts a comment, which continues until end of line. 1618/iĭescribe PARA_A_2_C_OF_1618 Claims compliance with senate bill 1618 header FROM_HAS_MIXED_NUMS From =~ FROM_HAS_MIXED_NUMS From: contains numbers mixed in with letters score A_HREF_TO_REMOVE 2.0 lang es describe FROM_FORGED_HOTMAIL Forzado From: simula ser de Description SpamAssassin is configured using some traditional UNIX-style configurationįiles, loaded from the /usr/share/spamassassin and /etc/mail/spamassassin Localiation Name Mail::SpamAssassin::Conf - SpamAssassin configuration file Synopsis # a comment rewrite_subject 1 full PARA_A_2_C_OF_1618 /Paragraph. This page presents all the tunning you can add to SpamAssassin when it checks your emails for spam.ĭeprecated options Privileged preferences SpamAssassin allows a large number of customization of user preferences. SpamAssassin configuration file SpamAssassin configuration file ![]()
0 Comments
Leave a Reply. |