svn commit: rev 22858 - spamassassin/site

[fe...@apache.org]

Author: felicity
Date: Mon Jul 12 16:50:24 2004
New Revision: 22858

Modified:
   spamassassin/site/main.wmk
Log:
added links to surbl, pyzor, dcc.  removed Mail::Audit reference.

Modified: spamassassin/site/main.wmk
==============================================================================
--- spamassassin/site/main.wmk	(original)
+++ spamassassin/site/main.wmk	Mon Jul 12 16:50:24 2004
@@ -135,21 +135,25 @@
     style (to put it politely), and some characteristic disclaimers
     and CYA text.  SpamAssassin can spot these, too.
 
-  - **blacklists**: SpamAssassin supports many useful existing blacklists, such
-    as <a href=http://www.mail-abuse.org>mail-abuse.org</a>, <a
-    href=http://www.ordb.org>ordb.org</a> or others.
+  - **blacklists**: SpamAssassin supports many useful existing
+    blacklists, such as <a
+    href=http://www.mail-abuse.org>mail-abuse.org</a>, <a
+    href=http://www.ordb.org>ordb.org</a>, <a
+    href=http://www.surbl.org/>SURBL</a>, and others.
 
   - **learning classifier**: SpamAssassin uses a Bayesian-like form of
     probability-analysis classification, so that a user can train
     it to recognise mails similar to a training set.
 
   - **distributed hash databases**: <A href=http://razor.sf.net/>Vipul's
-    Razor</a>, Pyzor and DCC are collaborative spam-tracking databases, which
-    work by taking a signature of spam messages.  Since spam typically operates
-    by sending an identical message to hundreds of people, these databases
-    short-circuit this by allowing the first person to receive a spam to add it
-    to the database -- at which point everyone else will automatically block
-    it.
+    Razor</a>, <a href=http://pyzor.sourceforge.net/>Pyzor</a> and
+    <a href=http://www.rhyolite.com/anti-spam/dcc/>DCC</a> are
+    collaborative spam-tracking databases, which work by taking a
+    signature of spam messages.  Since spam typically operates by
+    sending an identical message to hundreds of people, these
+    databases short-circuit this by allowing the first person to
+    receive a spam to add it to the database -- at which point
+    everyone else will automatically block it.
 
 Once identified, the mail can then be optionally tagged as spam for later
 filtering using the user's own mail user-agent application.
@@ -193,7 +197,6 @@
     href=doc/Mail_SpamAssassin.html>Mail::SpamAssassin classes</a>, it can be
     used in a wide variety of setups.  This means that SpamAssassin support is
     available for a variety of mail systems -- traditional procmail, a
-    Mail::Audit plugin,
     <a href=http://wiki.apache.org/spamassassin/UsingSpamAssassin>**qmail**</a>,
     <a href=http://wiki.apache.org/spamassassin/UsingSpamAssassin>**sendmail**</a>,
     <a href=http://wiki.apache.org/spamassassin/UsingSpamAssassin>**Postfix**</a>,