RedHat 8 and RedHat 9 have begun including SpamAssassin as a stock RPM.  While
our company's attitude is to run critical applications compiled by hand, SpamAssassin
might not be as critical to your operation as it is to ours.

Therefore, this document is the beginnings of a How-To Get SpamAssassin configured
and running on a RedHat 9 box using a standard installation.

AUTHOR: Kevin A. McGrail (kevin@mcgrail.com)
REVISION: Revised Working Draft as of 5/16/03


1. Switch to Postfix

	Use the mail transport switching utility to get the system using postfix. 

        	Under X11, go to <menu> -> system tools -> more system tools -> mail transport 
		agent switcher or run redhat-switch-mail from a shell. 

2. Properly configure Postfix to work
	
	This step is really beyond the scope of this how-to.  The assumption is that
	your DNS and email work before continuing with SpamAssassin.

	Possible Sources of Information:

  		http://www.redhat.com/support/resources/howto/RH-postfix-HOWTO/book1.html

3. Go to services and add spamassassin to services to run 

	Under X11, go to <menu> -> system settings -> server settings -> services and click 
	SpamAssassin to run status.  Alternately, you can run serviceconf from a shell      

4. Configure Postfix to use Procmail

	Edit the postfix config file to use procmail by uncommenting the line

           mailbox_command = /usr/bin/procmail


5. Create a Procmailrc file

	In /etc/ create or edit the file procmailrc.  Need to confirm that this is a 
        good procmailrc for a RH9.


An example procmailrc file is:

DROPPRIVS=yes
#Uncomment the following lines to allow for logging
#
#LOGFILE=/var/log/procmail
#VERBOSE=ON

# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.

:0fw
* < 256000

      | /usr/bin/spamassassin -P

      :0e
      {
         EXITCODE=$?
      } 


Thanks go to many people but Jason R. Wright was the main impetus behind getting this
How-To started.