You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by mm...@apache.org on 2010/01/21 00:42:39 UTC
svn commit: r901442 - /spamassassin/trunk/UPGRADE
Author: mmartinec
Date: Wed Jan 20 23:42:38 2010
New Revision: 901442
URL: http://svn.apache.org/viewvc?rev=901442&view=rev
Log:
the UPGRADE file: backported revised text from release notes
on a need to edit a .pre file when upgrading to activate a DKIM plugin
Modified:
spamassassin/trunk/UPGRADE
Modified: spamassassin/trunk/UPGRADE
URL: http://svn.apache.org/viewvc/spamassassin/trunk/UPGRADE?rev=901442&r1=901441&r2=901442&view=diff
==============================================================================
--- spamassassin/trunk/UPGRADE (original)
+++ spamassassin/trunk/UPGRADE Wed Jan 20 23:42:38 2010
@@ -11,11 +11,16 @@
install a new version to determine if any SQL updates need to be made to
your local installation.
-- The DKIM plugin is now enabled by default for new installs, if you have the
- "Mail::DKIM" perl module installed from CPAN. However, SpamAssassin will not
- overwrite existing plugin .pre configuration files, so if you wish to use
- DKIM, and are upgrading from a previous release, you will need to edit the
- "v312.pre" file yourself to uncomment it.
+- The DKIM plugin is now enabled by default for new installs, if the perl
+ module Mail::DKIM is installed. However, installation of SpamAssassin
+ will not overwrite existing .pre configuration files, so to use DKIM when
+ upgrading from a previous release that did not use DKIM, a directive:
+
+ loadplugin Mail::SpamAssassin::Plugin::DKIM
+
+ will need to be uncommented in file "v312.pre", or added to some
+ other .pre file, such as local.pre.
+
Note for Users Upgrading to SpamAssassin 3.2.0
-----------------------------------------------
@@ -33,6 +38,7 @@
them appropriately. See the Mail::SpamAssassin::Conf manual page for the
"msa_networks" setting.
+
Note for Users Upgrading to SpamAssassin 3.1.0
-----------------------------------------------
@@ -115,6 +121,7 @@
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 to SpamAssassin 3.0.x
----------------------------------------------