[Spamassassin Wiki] Update of "RuleUpdates" by TheoVanDinter

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by TheoVanDinter:
http://wiki.apache.org/spamassassin/RuleUpdates

------------------------------------------------------------------------------
  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.apache.org list for more information.
+ 
+ ----
+ 
+ == 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?::  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?::  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?:: 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?:: 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.
+ 
+ 
+ For more information about how to use sa-update and how it works, please read below.
  
  ----
  
@@ -106, +123 @@

  }}}
  
  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?::  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?::  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.
  
  ----