You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spamassassin.apache.org by jm...@apache.org on 2004/06/30 04:51:50 UTC
svn commit: rev 22289 - spamassassin/site
Author: jm
Date: Tue Jun 29 19:51:49 2004
New Revision: 22289
Modified:
spamassassin/site/main.wmk
Log:
slimmed down static content, moved to wiki
Modified: spamassassin/site/main.wmk
==============================================================================
--- spamassassin/site/main.wmk (original)
+++ spamassassin/site/main.wmk Tue Jun 29 19:51:49 2004
@@ -82,106 +82,10 @@
${title}
---------
-Quite a few folks are now using SpamAssassin(tm) to filter mail for their
-entire network.
-
-You can either:
-
- 1. set up a procmail rule in ##/etc/procmailrc## which will scan all
- mails processed by procmail. Advantage: each user can keep their own
- preferences and Bayes databases. However you should try to make this
- conditional, so that it doesn't happen unless the user has indicated
- __they__ want scanning; many users don't want filtering.
-
- 2. Copy in a ##.procmailrc## file into the home directory of each user who
- wants to have SpamAssassin scan for spam. Again, each user can keep their
- own preferences and Bayes databases.
-
- 3. Use one of the many approaches to integrate SpamAssassin into the heart
- of the mail pipeline of your MTA. <a href=http://wiki.apache.org/spamassassin/UsingSpamAssassin>This page</a> lists
- many systems, so I won't list them here.
-
-It's worth noting that the SpamAssassin also includes **spamd**, a daemonized
-version of SpamAssassin with a low-overhead C client, contributed by Craig R.
-Hughes. This greatly improves its suitability in high-volume setups, by
-massively increasing the message throughput.
-
-Here's what to use in a system-wide procmailrc to filter all mail through
-**spamd**:
-
-<pre>
- DROPPRIVS=yes
-
- :0fw
- * < 256000
- | spamc
-</pre>
-
-You'll need to make sure **spamd** is up and running; it's a daemon. There
-are Red Hat, Solaris and Debian init scripts included in the <a
-href=$(TOP/)full/${relline}/dist/spamd/>spamd directory of the distribution</a>.
-
-There's also code to load scores and user preferences from an SQL database,
-contributed by Justin England. <a href=$(TOP/)full/${relline}/dist/sql/README>Here's how to
-set this up, in detail</a>.
-
-Stuff To Note: False Positives
-=============
-
-SpamAssassin **will** produce false positives (flagging non-spam mail as
-possible spam), and this **will** drive some of your users up the wall.
-Quite a few mail users still get very little spam.
-
-Here's some tips:
-
- - Use a more conservative default points setting, such as 8.0 or 10.0 instead
- of the default 5.0. This will cut down on false positives, at the cost of
- letting more spam through: at a rough guess, a setting of 10.0 will permit
- an additional 20% of the total spam.
-
- - You should make filtering opt-out by default, and opt-in on request, or
- else allow users a way to opt-out of filtering easily. (this can be done
- by setting ##required_hits## to 100 for that user, either in their
- ##~/.spamassassin/user_prefs## file or in the SQL database.)
-
- - Modify the default SpamAssassin report template to include site-specific
- details of how they can opt out, or how to change their threshold to
- something higher.
-
- - Let them know that you've installed a spam filter! Modify the report
- template, and send them mail! I regularly get mail from users
- who haven't got a clue why they got mail from
- 'something called SpamAssassin', asking me to leave them alone. ;)
-
-Stuff To Note: Legal Issues
-=============
-
-Note that there may be legal issues with site-wide spam filtering. For
-example, in the UK, it is apparently illegal to hold emails for examination for
-longer than 2 days. Also, the <a
-href=http://www.sng.ecs.soton.ac.uk/mailscanner/#links>MailScanner info
-page</a> reckons that under section 3(3) of the Regulation of Investigatory
-Powers Act, __care must be taken to ensure that no-one other than the sender
-and intended recipient of any message can read any part of that message.__
-
-A possible way to route around this, is by simply using SpamAssassin in it's
-default mode, so that it simply __tags__ the mails with their estimated status,
-instead of full __mail filtering__ where you redirect or delete mail without
-the user's intervention. This way, the user still has final choice in what to
-do; and they can also rest assured that nobody on your staff has been ''reading
-their mail''. However, take this advice with a grain of salt -- I am not
-a lawyer, so if you're worried, ask one.
-
-Also, there __will__ be false positives, so simply deleting or bouncing mail
-based on SpamAssassin's judgement is not a wise thing to do and not recommended.
-
-Some tests, such as the ##mail-abuse.org## RBL tests, require payment for
-site-wide use.
-
+(Page moved to http://wiki.apache.org/spamassassin/UsingSiteWide)
</content>
-
<content format="text/et" name="index.txt"><{set title="Welcome to SpamAssassin"}>
<!-- START BLOCK -->
<div align=right><a href="http://osdir.com/Article198.phtml">
@@ -322,17 +226,6 @@
href="http://wiki.apache.org/spamassassin/">here</a>.
</content>
-<content name="admin.txt" format=text/et>
-<{set title="Administrivia"}>
-
-${title}
----------
-
- - The "SourceForge home page" [sfhome].
-
- [sfhome]: http://sourceforge.net/projects/spamassassin/
-
-</content>
<content format="text/et" name="downloads.txt"><{set title="Downloads"}>
${title}
@@ -426,116 +319,7 @@
${title}
---------
-First, RTFM [2] to make sure what you want to do isn't already possible ;)
-Then, join the "mailing list" [1].
-
- [2]: $(doc)
-
- [1]: $(lists)
-
-For new functionality or rules, a <a href=http://bugzilla.SpamAssassin.org/>
-Bugzilla bug</a> should be created to track progress and provide a forum
-for discussion; any patches should be stored (as an attachment) on that
-Bugzilla bug.
-
-Rule Development and QA
-~~~~~~~~~~~~
-
-This is performed by checking in the rule into the SVN rules file
-##rules/70_cvs_rules_under_test.cf##, whereby a distributed group of
-contributors will test it against their corpus in the nightly mass-check run.
-<a href=http://www.pathname.com/~corpus/> The resulting collated accuracy data
-can be viewed here</a>.
-
-German-Language Rule Development
-~~~~~~~~~~~~
-
-Daniel Roethlisberger and a few other contributors have lists and a web page
-set up for this: <a href=http://dragon.roe.ch/SA_de/>more info here</a>.
-
-Bug Tracking
-~~~~~~~~~~~~
-
-We track bugs using <a href=http://bugzilla.spamassassin.org/>
-SpamAssassin Bugzilla</a>. If you've found a bug, it'd be
-worth reporting it here so it can be tracked easily.
-
-SVN Access
-~~~~~~~~~~
-
-SpamAssassin's source code is hosted at the Apache Software Foundation. We use
-Subversion to manage the codebase.
-
- Auto: [Subversion]: http://subversion.tigris.org/
-
-To check out the latest source using anonymous Subversion, run this command
-after installing the client components of Subversion:
-
- svn co http://svn.apache.org/repos/asf/spamassassin/trunk
-
-(Note: you do not need to install the server components! Just the 'svn'
-command and its dependencies.)
-
-It's recommended you keep up to date with the <a
-href=$(lists)>SpamAssassin-dev</a> list if you are tracking SVN, since
-things will be moving around etc.
-
-If you are a committer to SpamAssassin, you need to use authenticated
-SVN. First, get the username for your Apache.org account, and ensure
-that it has the correct commit permissions. Then, re-check out the source
-like so:
-
- svn co https://svn.apache.org/repos/asf/spamassassin/trunk
-
-And type your username and password when prompted. After that, you will be
-able to add and edit files, and commit any changes you make after that point.
-
-The SVN tree can be viewed online here:
-
- - <a href=http://svn.apache.org/viewcvs.cgi/spamassassin/trunk/?root=Apache-SVN>Trunk</a> (active development branch, a la CVS HEAD)
- - <a href=http://svn.apache.org/viewcvs.cgi/spamassassin/?root=Apache-SVN>The branches and tags</a>
-
-Legacy: the old CVS tree and other modules are <a href=https://sourceforge.net/cvs/?group_id=25457>still hosted at sourceforge.net</a>.
-
-IRC
-~~~~~~~~~~~~
-
-Now and again, we've been known to chat about development issues
-on the freenode network on <code>#spamassassin</code>. Freenode
-servers include irc.us.freenode.net, irc.eu.freenode.net, etc.
-
-GA Work and Optimization
-~~~~~~~~~~~~
-
-We optimize SpamAssassin's scores using a genetic algorithm. If you'd like to
-play around with the mass-check result files used for this, to see if a better
-optimisation or classification technique can be used, get in touch via the
-SpamAssassin-Talk list, and we'll be happy to give you access to a set.
-
-Alternatively, a public corpus of mail to test GA work, develop new spam
-filtering techniques, or benchmark spam filters with, is available <A
-href=http://spamassassin.org/publiccorpus/>here</a>.
-
-Generating mass-check results is done using the ##mass-check## script, as
-described <a href="http://spamassassin.org/full/${relline}/dist/masses/README">in the
-masses/README file</a>, and with a corpus policy specified in <a
-href="http://spamassassin.org/full/${relline}/dist/masses/CORPUS_POLICY">the CORPUS_POLICY
-file</a>. So it's quite trivial to generate your own, too, given a corpus of
-mail like the SpamAssassin Public Corpus above.
-
-We're always interested in hearing about new spam-filtering techniques --
-especially if they get good results on a diverse corpus like the one above!
-Please post your results to the SpamAssassin-users list.
-
-Note that we use the following metrics to measure classification success,
-at the moment:
-
- - TCR (Total Cost Ratio), as defined in Ion Androutsopoulos' papers.
-
- - False positives, as a percentage of non-spam mail corpus.
-
- - False negatives, as a percentage of spam mail corpus.
-
+(Page moved to http://wiki.apache.org/spamassassin/DevelopmentStuff)
</content>
<content format="text/et" name="credits.txt"><{set title="Contributors"}>
@@ -544,8 +328,7 @@
This page has been replaced by the
<a href="http://cvs.apache.org/viewcvs.cgi/spamassassin/trunk/CREDITS?root=Apache-SVN&view=markup">
-CREDITS file in the main SA distribution</a>.
-
+CREDITS file in the distribution</a>.
</content>
<content name="users.txt" format=text/et>
<{set title="Information For End-Users"}>
@@ -705,7 +488,6 @@
Please read
<a href="http://wiki.apache.org/spamassassin/UsingSpamAssassin">
the relevant pages on the SpamAssassin wiki</a> instead.
-
</content>
<content format="text/et" name="lists.txt"><{set title="Mailing Lists"}>
@@ -713,65 +495,7 @@
${title}
--------
-There's a mailing list for discussion of SpamAssassin(tm), how it can be used,
-how to get it working, and features it needs:
-
-(send mail to **spamassassin-users-subscribe at incubator.apache.org** to subscribe;
-archives: one [talkarc2], two [talkarc])
-
-(**Note**: if you post a tech support question here, please be sure to first <a
-href="http://wiki.apache.org/spamassassin/">read the FAQ Wiki</a>
-in case your question is answered there. If not, then go ahead and
-post -- but be sure to note what product you're using -- SAProxy, Amavis, or
-direct use of SpamAssassin via procmail, for example -- what version of
-SpamAssassin that uses, and your platform. If you ask a FAQ,
-you may not get an answer ;)
-
-There is an announcements-only list:
-
-http://lists.sourceforge.net/mailman/listinfo/spamassassin-announce (archives: one [annarc])
-
-A developers list:
-
-(send mail to **spamassassin-dev-subscribe at incubator.apache.org** to subscribe;
-archives: one [devarc2], two [devarc])
-
-A list for German-language rule development:
-
-(send mail to **spamassassin-dev-de-subscribe at incubator.apache.org** to subscribe; archives: one [derarc])
-
-And a list for Brazilian rule development:
-
-http://lists.sourceforge.net/mailman/listinfo/spamassassin-devel-br (archives: one [brarc])
-<!-- (send mail to **spamassassin-dev-br-subscribe at incubator.apache.org** to subscribe; archives: one [brarc]) -->
-
- [talkarc]: http://marc.theaimsgroup.com/?l=spamassassin-users&r=1&w=2
- [talkarc2]: http://news.gmane.org/thread.php?group=gmane.mail.spam.spamassassin.general
- [annarc]: http://marc.theaimsgroup.com/?l=spamassassin-announce&r=1&w=2
- [devarc]: http://marc.theaimsgroup.com/?l=spamassassin-devel&r=1&w=2
- [devarc2]: http://news.gmane.org/thread.php?group=gmane.mail.spam.spamassassin.devel
- [derarc]: http://marc.theaimsgroup.com/?l=spamassassin-devel-de&r=1&w=2
- [brarc]: http://marc.theaimsgroup.com/?l=spamassassin-devel-br&r=1&w=2
-
-
-
-Searching The List Archives
-===============
-
-This form will search the __spamassassin-users__ archives at <a
-href=http://news.gmane.org/thread.php?group=gmane.mail.spam.spamassassin.general>GMANE.org</a>:
-
-<table cellpadding=4 width="100%"> <tr>
-<td class="webtd" bgcolor="#009900" >
-<form method="get" name="mform" action="http://search.gmane.org/search.php">
-<table> <tr> <td class="wetd">Search group</td>
-<td colspan=2><input type=text name=query size=50 value=""></td>
-</tr> <tr valign=top> <td class="wetd"> </td>
-<td><input type=hidden name=group value="gmane.mail.spam.spamassassin.general">
-<input type=submit value="Search >>"></td>
-<td align=right><a href="http://we.gmane.org/"><img border=0 src="http://we.gmane.org/textit.php?string=we:search&color=black&size=30" name="we:search" alt="" /></a>
-</td></tr> </td> </tr> </table> </td> </tr> </table> </form>
-
+(Page moved to http://wiki.apache.org/spamassassin/MailingLists)
</content>
<media src="doc" name="*.html" listname="alldocs" />
@@ -977,21 +701,16 @@
<td valign=top>
<div align=right>
<font size=-1>
- [<a href="http://wiki.apache.org/spamassassin/">Wiki</a>]
- [<a href="http://wiki.apache.org/spamassassin/UsingSpamAssassin">Where</a>]
[<a href="$(index)">Features</a>]
[<a href="$(downloads)">Download</a>]
+ [<a href="http://wiki.apache.org/spamassassin/">Wiki/FAQ</a>]
<br />
[<a href="$(doc)">Documentation</a>]
- [<a href="$(lists)">Lists</a>]
+ [<a href="http://wiki.apache.org/spamassassin/MailingLists">Lists</a>]
[<a href="$(tests)">Tests</a>]
- [<a href="$(sitewide)">Site-Wide</a>]
<br />
- [<a href="$(hacking)">Hacking</a>]
[<a href="http://bugzilla.spamassassin.org/">Bugs</a>]
[<a href="$(TOP/)full/3.0.x/dist/CREDITS">Credits</a>]
- [<a href="$(admin)">Admin</a>]
- [<a href="$(TOP/)gtube/">GTUBE</a>]
</font>
</div></td>
</tr></table>