...
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. \\
What do I need to do with-respect-to sa-update after a SpamAssassin upgrade?indent \\ Whenever you upgrade the version of [SpamAssassin] that's installed, the directory where the updates are expected to be changes (it's based on the version). So whenever you upgrade, you will want to run sa-update for all of the channels that you want to have installed. \\
After upgrading SpamAssassin several times, there are a number of directories .../3.001001, .../3.001002, .../3.001003, etc. What should I do with them?indent \\ You definitely want to keep the latest version that matches the version of [SpamAssassin] that you have installed. However, the older versions can be removed whenever you like. \\
After sa-update was used, the report contact setting becomes @@.indent \\ This is a known issue being tracked in \[http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4862 bug 4862\]. The quick fix for it right now is to set "report_contact <whatever you want>" in your local.cf file. Future updates will not include the report_contact setting (typically set in 10_misc.cf), and so instead of @<at:var at:name="CONTACT_ADDRESS" />@ will be the default "the administrator of that system" text. \\
For more information about how to use sa-update and how it works, please read below.
...