svn commit: rev 20274 - incubator/spamassassin/trunk

[du...@apache.org]

Author: duncf
Date: Sun May 23 18:51:38 2004
New Revision: 20274

Modified:
   incubator/spamassassin/trunk/README
Log:
Made some updates to the README -- removed some stuff referring to old
code. Also added Apache Incubator notice (I think we're required to
under ASF policy, someone correct me if I'm wrong. Also, I'm assuming
Sponsor = Apache BOD)


Modified: incubator/spamassassin/trunk/README
==============================================================================
--- incubator/spamassassin/trunk/README	(original)
+++ incubator/spamassassin/trunk/README	Sun May 23 18:51:38 2004
@@ -1,19 +1,19 @@
 Welcome to SpamAssassin!
 ------------------------
 
-SpamAssassin is a mail filter which attempts to identify spam using text
-analysis and several internet-based realtime blacklists.
+SpamAssassin is a mail filter which attempts to identify spam using
+text analysis and several internet-based realtime blacklists.
 
 Using its rule base, it uses a wide range of heuristic tests on mail
 headers and body text to identify "spam", also known as unsolicited
 commercial email.
 
-Once identified, the mail can then be optionally tagged as spam for later
-filtering using the user's own mail user-agent application.
+Once identified, the mail can then be optionally tagged as spam for
+later filtering using the user's own mail user-agent application.
 
 SpamAssassin typically differentiates successfully between spam and
-non-spam in between 95% and 99% of cases, depending on what kind
-of mail you get.
+non-spam in between 95% and 100% of cases, depending on what kind of
+mail you get.
 
 SpamAssassin also includes support for reporting spam messages
 automatically, and/or manually, to collaborative filtering databases such
@@ -21,39 +21,39 @@
 
 	[1]: http://razor.sourceforge.net/
 
-The distribution provides "spamassassin", a command line tool to perform
-filtering, along with the "Mail::SpamAssassin" module set which allows
-SpamAssassin to be used in spam-protection proxy SMTP or POP/IMAP server,
-or a variety of different spam-blocking scenarios.
-
-In addition, Craig Hughes has contributed "spamd", a daemonized version of
-SpamAssassin, which runs persistently.  Using "spamc", a lightweight C
-client, this allows an MTA to process large volumes of mail through
-SpamAssassin without having to fork/exec a perl interpreter for each one.
-
-For those sites running qmail as your MTA, the "qmail" directory contains
-two ways to integrate spamc with your system.  Kobe Lenjou has contributed
-a patch to qmail-scanner, and John Peacock has contributed a QMAILQUEUE
-enabled qmail-spamc.  See the README*'s for more details.
-
-Ian R. Justman has contributed "spamproxy", a spam-filtering SMTP proxy
-server.  This lives in the "released" directory on the web site.
-
-SpamAssassin lives at http://spamassassin.org/ or in CPAN, and is
-distributed under the Apache License, version 1.1, as described in the
-file named "LICENSE".  Use of the SpamAssassin name is restricted as
-documented in the file named "TRADEMARK".
-
-This module owes a lot of inspiration to Mark Jeftovic's filter.plx [2],
-which I used for a long time, and contributed some code to.  However,
-SpamAssassin is a ground-up rewrite with a new, greatly improved ruleset,
-a different code model and installation system, and hopefully will be easy
-to adapt for a multitude of applications.
-
-	[2]: http://AntiSpam.shmOOze.net/filter/
-
-Questions regarding SpamAssassin should be sent to the mailing list:
-<spamassassin-talk /at/ lists /dot/ sourceforge /dot/ net>.
+The distribution provides "spamassassin", a command line tool to
+perform filtering, along with the "Mail::SpamAssassin" module set
+which allows SpamAssassin to be used in spam-protection proxy SMTP or
+POP/IMAP server, or a variety of different spam-blocking scenarios.
+
+In addition, Craig Hughes has contributed "spamd", a daemonized
+version of SpamAssassin, which runs persistently.  Using "spamc", a
+lightweight C client, this allows an MTA to process large volumes of
+mail through SpamAssassin without having to fork/exec a perl
+interpreter for each one.
+
+If you have questions about SpamAssassin, please check the Wiki[2] to
+see if someone has already posted an answer to your question. (The
+Wiki doubles as a FAQ.) Failing that, post a message to the
+spamassassin-users mailing list[3]. If you've found a bug (and you're
+sure it's a bug after checking the Wiki), please file a report in our
+Bugzilla[4].
+
+	[2]: http://wiki.spamassassin.org/
+	[3]: http://www.spamassassin.org/lists.html
+	[4]: http://bugzilla.spamassassin.org/
+
+Please also be sure to read the man pages.
+
+SpamAssassin is an effort undergoing incubation at the Apache Software
+Foundation (ASF), sponsored by the Apache Board of
+Directors. Incubation is required of all newly accepted projects until
+a further review indicates that the infrastructure, communications,
+and decision making process have stabilized in a manner consistent
+with other successful ASF projects. While incubation status is not
+necessarily a reflection of the completeness or stability of the code,
+it does indicate that the project has yet to be fully endorsed by the
+ASF.
 
 
 Installing SpamAssassin
@@ -62,7 +62,6 @@
 See the INSTALL file.
 
 
-
 Customising SpamAssassin
 ------------------------
 
@@ -216,7 +215,6 @@
 support for this.  You will, of course, get credited for this work ;)
 
 
-
 Help With SpamAssassin
 ----------------------
 
@@ -226,7 +224,6 @@
 link to the archive of past messages.
 
 The FAQ is here: http://wiki.spamassassin.org/w/FrequentlyAskedQuestions
-
 
 
 Commercial Tests