Despam v0.6b, Copyright 1997 by Leslie M. Barstow III

What is Despam?

   Despam is a tool which examines incoming mail to determine whether it
   is a known e-mail spam or not.  Programs like procmail can use despam
   to determine what action to perform on identified spam.

Ok, what is spam?

   Spam, as used in the context of this README, is any substantially
   identical message sent to many different locations.  Despam specifically
   looks at e-mail "spam" - also known as UCE (Unsolicited Commercial
   E-mail, although it isn't always commercial).

   If you want the full, technical, and gory details (eww!), see
   the Spam FAQ.

What are the features of despam?

   Despam is fully configurable and easily expandable.  It accepts
   NoCeM-type messages to allow quick updates from multiple sources,
   while maintaining the security of PGP-signed messages.  It also
   accepts expansion modules to enhance its search capabilities.
   Three search modes come with despam - sender-block, message checksum
   match, and message keyphrase search.

   Users can tell despam not to process by one or more search modes, and can
   also choose to accept blocked messages by category (I want all
   CyberPromo stuff, but not Quantum Communications).

What are the limitations of despam?

   Despam requires that someone get spammed, and that the recipient tell
   others of the spam.

   Also, at this time, I don't have a mailbox despammer, so once it
   gets past despam, you've got to read it... (I suggest bouncing it to
   your admin in charge of abuse and having them whip up a new despam
   rule to send out to the anti-spam world ;-)

What do I need to run despam?

   Despam is a Perl5 script, so you will need Perl5 installed on your
   system.  Also, a mail filter which is capable of evaluating the return
   value of a program; I use procmail, so at this time, if you want to use
   the supplied configuration, you have to have procmail.

   In addition, you need to have root access if you wish to install
   despam system-wide.  It also helps to be able to set up a despam
   alias for sendmail (or its equivalent) to automatically process
   incoming spam reports.

How do I set up despam?

   See the INSTALL file for details.  If you are using procmail, once
   despam is installed, each user must type 'despam-on' to configure
   despam.  'despam-off' will remove the procmail rule from the
   .procmailrc, and will prompt the user if she wants to remove her
   .despamrc.

How do I debug despam, especially on false hits?

   Despam does have some debugging code.  If you edit despam, one of
   the first lines of code, commented out, is #$debug++;.  Uncomment
   the line and then redirect the message to despam through standard in
   (despam < messagecopyfile).  Despam will produce copious output, with
   the last couple of lines indicating the matched file.

I found a spammer not in the searches - what do I do?

   First, try to locate the spammer's real origin (you can check out
   my Web page at http://www.servtech.com/public/phoenix and follow the
   spam links for hints...)

   Next, make a new despam pattern file, and add it to despam's pattern
   directory - you won't get spam from them any more ;-)

   I am trying not to become a center for the co-ordination of spam
   patterns.  Once the NoCeM messages are fully operational, that will
   be the sole method of distribution.  Until then, try to hold on.  I
   will probably be getting the same spam soon enough :-(

Who do I contact for gripes?

   Contact Les Barstow at phoenix@faerealm.com.  *Please* notify me if
   I add someone I shouldn't (I added a whole bunch from CyberENet, but
   tried to remove the legit systems from the list, for example...).

What do I owe for saving my life from spammers?

   Nothing, although generous contributions are gladly accepted.  Again,
   write me at phoenix@faerealm.com, and I'll tell you where to send the
   money (or whatever else you want to contribute...)
