For example: 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).
By default, sa-update will require the use of GPG signatures to verify that downloaded updates are in fact legitimate.
directory, which will have each channel in its own directory underneath.
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.
However, there may be channels which do not publish GPG signatures, or the system may not have GPG installed.
In these situations, specify the Specify which GPG key ids should be trusted to sign update packages.
If there are multiple keys, use this option multiple times to list them.
Generally it's safer to specify the whole key fingerprint, but it is more common to see simply the last 8 hex digits used. This can be useful just to see what sa-update is doing, but is also useful to debug problems, etc.System: Free BSD 6.x Plesk Version: 8.0.x May work with other versions.The stock plesk Spamassassin is a 3.1.x variant, which gets pretty old pretty quick.Note: This page is under construction and shouldn't be considered "complete".If there are any questions, etc, please feel free to contact the users -at- spamassassin.list for more information.ie: The goal of sa-update is to download new configuration files (rules, scores, etc,) so that Spam Assassin will use them to better catch spam and/or to avoid catching ham messages.