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/08 02:51:29 UTC

svn commit: r897077 - in /spamassassin/trunk: INSTALL build/announcements/3.3.0-release.txt

Author: mmartinec
Date: Fri Jan  8 01:51:25 2010
New Revision: 897077

URL: http://svn.apache.org/viewvc?rev=897077&view=rev
Log:
INSTALL, 3.3.0-release.txt: mention that a version of sa-update
should match the rest of SA (old version may lack some command line
option, or some functionality);  mention that --updatedir may
need to be used when installing rules into non-default location

Modified:
    spamassassin/trunk/INSTALL
    spamassassin/trunk/build/announcements/3.3.0-release.txt

Modified: spamassassin/trunk/INSTALL
URL: http://svn.apache.org/viewvc/spamassassin/trunk/INSTALL?rev=897077&r1=897076&r2=897077&view=diff
==============================================================================
--- spamassassin/trunk/INSTALL (original)
+++ spamassassin/trunk/INSTALL Fri Jan  8 01:51:25 2010
@@ -140,6 +140,11 @@
 Installing Rules
 ----------------
 
+Rules are normally installed by running a sa-update command.
+The version of sa-update program should match the version of SpamAssassin
+modules, so invoking sa-update should be performed only after installing
+or upgrading SpamAssassin code, not before.
+
 Installing rules from network is done with a single command:
 
         sa-update
@@ -162,19 +167,28 @@
 
     curl -O http://spamassassin.apache.org/updates/GPG.KEY
 
-Import the signing key to the SpamAssassin keyring, so that the rules
+Import the signing key to the SpamAssassin gpg keyring, so that the rules
 files can be verified safely:
 
     sa-update --import GPG.KEY
 
 Install rules from a compressed tar archive:
 
-    sa-update --install Mail-SpamAssassin-rules-3.3.0-rc1.r893295.tgz
+    sa-update --install Mail-SpamAssassin-rules-xxx.tgz
 
 Note that the ".tgz.asc", ".tgz.md5" and ".tgz.sha1" files all need to
 be in the same directory, otherwise sa-update will fail.
 
 
+If the intended rules destination directory differs from a default location
+as assumed by sa-update and SpamAssassin, such as when running a content
+filter within a Unix jail or on an unusual installation, please supply the
+rules destination directory to sa-update through its option --updatedir,
+such as:
+
+    sa-update --updatedir /var/jail/var/db/spamassassin/3.003000
+
+
 CPAN
 ----
 

Modified: spamassassin/trunk/build/announcements/3.3.0-release.txt
URL: http://svn.apache.org/viewvc/spamassassin/trunk/build/announcements/3.3.0-release.txt?rev=897077&r1=897076&r2=897077&view=diff
==============================================================================
--- spamassassin/trunk/build/announcements/3.3.0-release.txt (original)
+++ spamassassin/trunk/build/announcements/3.3.0-release.txt Fri Jan  8 01:51:25 2010
@@ -82,11 +82,11 @@
 - it may be worth mentioning that a rule DKIM_VERIFIED has been renamed
   to DKIM_VALID, to match its semantics;
 
-- due to a change in internal data structure (Bug 6185, 6254), third-party
-  plugins which accesss the $pms->{main}->{conf}->{headers_spam} (and ham)
-  need to be updated. One such example is the ClamAVPlugin plugin - please
-  find a fresh version on its wiki page. It retains backwards compatibility,
-  so can be used with both 3.2.5 as well as with SpamAssassin 3.3.0;
+- due to changes in some internal data structures (like Bug 6185, 6254),
+  some third-party plugins may need to be updated. One such example is
+  the ClamAVPlugin plugin - please find a fresh version on its wiki page.
+  The updated ClamAVPlugin plugin can be used with both 3.2.5 as well as
+  with SpamAssassin 3.3.0;
 
 - versions of amavisd-new between 2.5.2 and 2.6.1 (inclusive) are incompatible
   with SpamAssassin 3.3; please upgrade amavisd to 2.6.2 or later, or apply
@@ -101,11 +101,12 @@
 INSTALLING RULES
 
 Rules are normally installed by running a sa-update command.
-The version of sa-update should match the version of SpamAssassin
-modules, so invoking sa-update should be performed after installing
+The version of sa-update program should match the version of SpamAssassin
+modules, so invoking sa-update should be performed only after installing
 or upgrading SpamAssassin code, not before.
 
-Installing rules from network is done with a single command:
+Installing rules from network is done with a single command,
+normally run as root:
   sa-update
 
 Installing rules from files: