Author: parker
Date: Tue Jun 21 08:59:35 2005
New Revision: 191672
URL: http://svn.apache.org/viewcvs?rev=191672&view=rev
Log:
Initial stab at UPGRADE docs for 3.1
Modified:
spamassassin/trunk/UPGRADE
Modified: spamassassin/trunk/UPGRADE
URL: http://svn.apache.org/viewcvs/spamassassin/trunk/UPGRADE?rev=191672&r1=191671&r2=191672&view=diff
==============================================================================
--- spamassassin/trunk/UPGRADE (original)
+++ spamassassin/trunk/UPGRADE Tue Jun 21 08:59:35 2005
@@ -1,11 +1,52 @@
Note for Users Upgrading to SpamAssassin 3.1.0
-----------------------------------------------
-- The AWL support for NDBM_File databases has been dropped, due to a bug in
- that package which renders it useless (bug 4353). It appears that SDBM_File,
- the package which will be used instead, is fully compatible with NDBM
- however, so this should be unnoticeable.
+- A significant amount of core functionality has been moved into
+ plugins. These include, AWL (auto-whitelist), DCC, Pyzor, Razor2,
+ SpamCop reporting and TextCat. For information on configuring these
+ plugins please refer to their individual documentation:
+ perldoc Mail::SpamAssassin::Plugin::* (ie AWL, DCC, etc)
+- Due to license restrictions the DCC and Razor2 plugins are disabled
+ by default. We encourage you to read the appropriate license
+ yourself and decide if you are able to re-enable the plugins for
+ your site.
+
+- The use_auto_whitelist config option has been moved to a user config
+ option, this allows individual users to turn on or off whitelisting
+ regardless of what is set in the system config. If you would like
+ to disable AWL (auto-whitelist) then you can comment out the plugin
+ in v310.pre.
+
+- The bayes_auto_learn_threshold_* config options for bayes have moved
+ to a plugin. In general the default should work just fine however
+ if you are interested in changing these values you should see:
+ perldoc Mail::SpamAssassin::Plugin::AutoLearnThreshold
+
+- The AWL support for NDBM_File databases has been dropped, due to a
+ bug in that package which renders it useless (bug 4353). It appears
+ that SDBM_File, the package which will be used instead, is fully
+ compatible with NDBM however, so this should be unnoticeable.
+
+- The prefork algorithm for spamd has been changed. In this version
+ spamd will attempt to keep a small number of "hot" child processes
+ as busy as possible, and keep any others as idle as possible, using
+ something similar to the Apache httpd server scaling algorithm.
+ This is accomplished by the master process coordinating the
+ activities of the children. You can use the --round-robin switch
+ for spamd to disable this scaling algorithm, and the behaviour seen
+ in the 3.0.x versions will be used instead, where all processes
+ receive an equal load and no scaling takes place.
+
+- See http://wiki.apache.org/spamassassin/UpgradeTo310 for a
+ supplementary list of upgrade notes. It will be updated with any
+ upgrade notes not captured in this document.
+
+- Finally, this document is likely not complete. Other configuration
+ options/arguments may have changed from older versions, etc. It would
+ be good to double-check any custom configuration options to make sure
+ they're still valid. This could be as simple as running "spamassassin
+ --lint", or more complex, as required by the environment.
Note for Users Upgrading from SpamAssassin 3.0.x
------------------------------------------------
Date: Tue Jun 21 08:59:35 2005
New Revision: 191672
URL: http://svn.apache.org/viewcvs?rev=191672&view=rev
Log:
Initial stab at UPGRADE docs for 3.1
Modified:
spamassassin/trunk/UPGRADE
Modified: spamassassin/trunk/UPGRADE
URL: http://svn.apache.org/viewcvs/spamassassin/trunk/UPGRADE?rev=191672&r1=191671&r2=191672&view=diff
==============================================================================
--- spamassassin/trunk/UPGRADE (original)
+++ spamassassin/trunk/UPGRADE Tue Jun 21 08:59:35 2005
@@ -1,11 +1,52 @@
Note for Users Upgrading to SpamAssassin 3.1.0
-----------------------------------------------
-- The AWL support for NDBM_File databases has been dropped, due to a bug in
- that package which renders it useless (bug 4353). It appears that SDBM_File,
- the package which will be used instead, is fully compatible with NDBM
- however, so this should be unnoticeable.
+- A significant amount of core functionality has been moved into
+ plugins. These include, AWL (auto-whitelist), DCC, Pyzor, Razor2,
+ SpamCop reporting and TextCat. For information on configuring these
+ plugins please refer to their individual documentation:
+ perldoc Mail::SpamAssassin::Plugin::* (ie AWL, DCC, etc)
+- Due to license restrictions the DCC and Razor2 plugins are disabled
+ by default. We encourage you to read the appropriate license
+ yourself and decide if you are able to re-enable the plugins for
+ your site.
+
+- The use_auto_whitelist config option has been moved to a user config
+ option, this allows individual users to turn on or off whitelisting
+ regardless of what is set in the system config. If you would like
+ to disable AWL (auto-whitelist) then you can comment out the plugin
+ in v310.pre.
+
+- The bayes_auto_learn_threshold_* config options for bayes have moved
+ to a plugin. In general the default should work just fine however
+ if you are interested in changing these values you should see:
+ perldoc Mail::SpamAssassin::Plugin::AutoLearnThreshold
+
+- The AWL support for NDBM_File databases has been dropped, due to a
+ bug in that package which renders it useless (bug 4353). It appears
+ that SDBM_File, the package which will be used instead, is fully
+ compatible with NDBM however, so this should be unnoticeable.
+
+- The prefork algorithm for spamd has been changed. In this version
+ spamd will attempt to keep a small number of "hot" child processes
+ as busy as possible, and keep any others as idle as possible, using
+ something similar to the Apache httpd server scaling algorithm.
+ This is accomplished by the master process coordinating the
+ activities of the children. You can use the --round-robin switch
+ for spamd to disable this scaling algorithm, and the behaviour seen
+ in the 3.0.x versions will be used instead, where all processes
+ receive an equal load and no scaling takes place.
+
+- See http://wiki.apache.org/spamassassin/UpgradeTo310 for a
+ supplementary list of upgrade notes. It will be updated with any
+ upgrade notes not captured in this document.
+
+- Finally, this document is likely not complete. Other configuration
+ options/arguments may have changed from older versions, etc. It would
+ be good to double-check any custom configuration options to make sure
+ they're still valid. This could be as simple as running "spamassassin
+ --lint", or more complex, as required by the environment.
Note for Users Upgrading from SpamAssassin 3.0.x
------------------------------------------------