Mailing-List: contact commits-help@spamassassin.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Spam Assassin Dev" <spamassassin-dev@incubator.apache.org>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: spamassassin-cvs@incubator.apache.org
To: spamassassin-cvs@incubator.apache.org
Subject: =?iso-8859-1?q?=5BSpamAssassin_Wiki=5D_Updated=3A__CustomPlugins?=
Date: Mon, 23 Aug 2004 19:17:19 -0000
Message-ID: <20040823191719.28558.39678@minotaur.apache.org>

   Date: 2004-08-23T12:17:19
   Editor: JustinMason <jm@jmason.org>
   Wiki: SpamAssassin Wiki
   Page: CustomPlugins
   URL: http://wiki.apache.org/spamassassin/CustomPlugins

   no comment

Change Log:

---------------------------------------------------------------------------=
---
@@ -6,9 +6,11 @@
 =

 Please add links to third-party SA plugins here.  Note that only SpamAssas=
sin 3.0.0 or later can use these (and it's not released yet!).  To use thes=
e, just place the file(s) in /etc/mail/spamassassin (if you use spamd, be s=
ure to restart); SpamAssassin will need at least 1 rule file (ending in .cf=
) to load the plugin, and that will typically use a ''loadplugin'' line to =
load a .pm file containing the plugin's perl code.
 =

+The .pm file can be kept in /etc/mail/spamassassin, too. (once [http://bug=
zilla.spamassassin.org/show_bug.cgi?id=3D3717 bug 3717] is fixed.)
+
 Before running these plugins please do the following:
 =

- 1. Read any extra info available with the plugins, including the comments=
 in the .cf files.
+ 1. Read any extra info available with the plugins, including the comments=
 in the .cf files, or the POD documentation in the .pm file.
  2. Check to make sure that the default scores fit your installation.  You=
 might want to modify scores. =

  3. Make sure to --lint the rules after loading them.
  4. Test the new plugin.  Keep an eye on hits from the new rules to determ=
ine if the scoring is right for you.