2/6/2024 0 Comments Spamassassin ruleFor multiple channels, specify this option multiple times. If other channels should be used, specify it with this option. channel :: sa-update by default only uses the channel for updates. ![]() If updates should go into a different directory, specify it via this option. updatedir :: sa-update by default places updates in the /var/lib/spamassassin/ directory. Sa-update has several parameters that can be passed via the commandline. NOTE: Once the /var/lib/spamassassin/ directory exists, spamassassin expects to find all rules underneath that directory, so make sure that the first time you run sa-update it completes successfully (see below for information about running in debug mode). Shows the channel available for SpamAssassin 3.1.4, underneath the /var/lib/spamassassin directory.įor more information about what makes up a channel and how it all works together, please see the Publishing channels for sa-update section below. Each channel will also have a channel cf file and (optionally) a channel pre file to load the update's configurations in the update's parent directory. By default, sa-update (and spamassassin) expect to find updates in the /var/lib/spamassassin/ directory, which will have each channel in its own directory underneath. By default, sa-update will use the channel to receive official updates from the SpamAssassin project, but anyone can create a channel and publish updates. Simply put, channels are locations where sa-update can download rule and configuration files. Simply put, sa-update allows rules to be distributed as they are developed, while full SpamAssassin releases can focus on bug fixes and new features. Safelist a Sender or Domain in SpamAssassin. With sa-update, those rules can quickly (potentially within minutes) be distributed and the new spam caught. Spam is rapidly changing, and new rules are often written in response. First, it shows: config: read file /etc/mail/spamassassin/local.cf Which verifies its local.cf file is correct. The main reason to use sa-update is that the old method of disseminating rules, releasing a new version SpamAssassin, is a lengthy process that can take many months. In the debug messages I see two things which tell me that local.cf IS the correct place to add custom rules, and spamassassin is picking it up. The goal of sa-update is to download new configuration files (rules, scores, etc,) so that SpamAssassin will use them to better catch spam and/or to avoid catching ham messages. ie: export http_proxy=''įor more information about how to use sa-update and how it works, please read below. The main one of interest is "http_proxy", which should be set to an URL defining the proxy. “under these mitigating circumstances, that other rule should not be applied.Sa-update uses the LWP::UserAgent module, which allows certain environment variables to be set so that requests use defined proxy servers. Is there any known means to actually switch off one rule from another? i.e. control whether it is allowed, not force it both on and off.Īnother approach that could have existed but also does not seem to: Open /etc/mail/spamassassin/local.cf for system-wide safelisting or /.spamassassin/userprefs for yourself. ![]() Meta BUILTIN_RULE BUILTIN_RULE & !_MY_RULEĪn ideal directive under the current configuration syntax would resemble: This would work, but circular definitions are not permitted: The problem with meta is that it will not only switch off the rule if the mitigation applies, but it will switch it on when the mitigation does not apply! I don’t want the built-in rule to be forcibly enabled when it was already off I only want to turn it off when it was already on, but it is not needed. ![]() The SpamAssassin rule syntax is overly limited and seems to prevent you from doing this, but I wondered if anyone had ever found a workaround. Provided by: spamassassin3.4. Setting a rules score to 0 will disable that rule from running. The SpamAssassin filter runs its tests on each incoming email and. The fourth score is used when Bayes is enabled and network tests are enabled. I have wished for a long time that I could use one rule in SpamAssassin to control another, specifically, to mitigate a built-in rule under specific circumstances. Each SpamAssassin rule is associated with a value that can be either negative or positive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |