Page History

...

To perform updates without attempting to put the files into the system-wide location (either for users or to test, etc,) use the --updatedir option to aim at a different directory for which to put the updates.

Installed Updates

When updates are downloaded, they are put into a directory under the local state dir (default /var/lib/spamassassin/<spamassassin version>) similar to:

/var/lib/spamassassin
`-- 3.001001
    |-- updates_spamassassin_org
    `-- updates_spamassassin_org.cf

The files from the update go into updates_spamassassin_org, and the *.cf files are then included by updates_spamassassin_org.cf, which also keeps track of what update version is installed. Therefore, if it is desired to change the update directory, the .cf and the update directory will exist there.

Additonal Notes / FAQ

• Currently, for 3.1.1 and 3.2.0, to use any channel for updates requires that updates.spamassassin.org also be used. This is because once the update directory exists, the SpamAssassin modules expect to find all rules in that directory.
  Can plugins be distributed via updates/channels?
  

  indent
  \\ From a technical standpoint, updates can contain plugins. However, the default channel, updates.spamassassin.org, will not publish plugins using this method at this time since people are likely not ready to accept automatic code updates. \\

  
  After sa-update completes, do I have to move the files somewhere for them to be used?
  

  indent
  \\ No. By default, sa-update and the [SpamAssassin] modules use the same location for updates. This means that after a successful update run, the new rules are available for use. As usual, if using spamd, a restart is required for the new rules to be read in and enabled. \\

  
  

...