Difference between revisions of "Spam Control at CCRMA"

From CCRMA Wiki
Jump to: navigation, search
(.procmailrc File)
(.procmailrc File)
Line 10: Line 10:
 
== .procmailrc File ==
 
== .procmailrc File ==
  
This file is key in your Spam control effort.  It is a hidden or 'dot' file, located in your home directory.  You will need to create this file, see below for details on how to do this.  .procmailrc gives Sendmail [http://en.wikipedia.org/wiki/Sendmail] instructions on where to route your email once it arrives at CCRMA.  The idea is to send email through SpamAssassin [http://spamassassin.apache.org] before it get's to your inbox.  SpamAssassin will run each email through its filter (filter rules are updated frequently to reflect new spam 'threats')
+
This file is key in your Spam control effort.  It is a hidden or 'dot' file, located in your home directory.  You will need to create this file, see below for details on how to do this.  .procmailrc gives Sendmail [http://en.wikipedia.org/wiki/Sendmail] instructions on where to route your email once it arrives at CCRMA.  The idea is to make Sendmail route email through SpamAssassin [http://spamassassin.apache.org] before it get's to your inbox.   
 +
 
 +
SpamAssassin will run each email through its filter (filter rules are updated frequently to reflect new spam 'threats').  SpamAssassin will add several lines to your email headers, including: X-Spam-Level, X-Spam-Checker-Version, X-Spam-Status, and X-Spam-Report.  For now, let's concentrate on '''X-Spam-Level''' since it is on this line, that you will create filter's in your email client.
  
 
== Evolution ==
 
== Evolution ==

Revision as of 19:10, 5 March 2007

This page is incomplete and under construction!

Welcome to CCRMA's Spam fighter homepage.

Having a 'Spam Free' inbox is a requires vigilence on everyone's part. In the text below, we'll describe what you can do to minimize your Spam.

First you need to determine which email client you will be using (e.g. Evolution, Thunderbird, WebMail, or Pine). Spam fighting is much more difficult if you use more than one email client. The descriptions below are for exclusive use of only one client. These solutions also assume that you will not be using client side 'intelligent email filtering' (where the your email client 'learns' about Junk mail).


.procmailrc File

This file is key in your Spam control effort. It is a hidden or 'dot' file, located in your home directory. You will need to create this file, see below for details on how to do this. .procmailrc gives Sendmail [1] instructions on where to route your email once it arrives at CCRMA. The idea is to make Sendmail route email through SpamAssassin [2] before it get's to your inbox.

SpamAssassin will run each email through its filter (filter rules are updated frequently to reflect new spam 'threats'). SpamAssassin will add several lines to your email headers, including: X-Spam-Level, X-Spam-Checker-Version, X-Spam-Status, and X-Spam-Report. For now, let's concentrate on X-Spam-Level since it is on this line, that you will create filter's in your email client.

Evolution

Inside Evolution, you will need to establish another


# error messages to a log for debugging
# LOGFILE=$HOME/mail/.procmail_log
# VERBOSE=yes
# LOGABSTRACT=all

# directory where mailboxes are located
# this is the default used by pine
MAILDIR=$HOME

# pipe the message through spamassassin in cm-home
:0fw
| spamc -d 171.64.197.138


# all stanford spam tagged email is considered extreme spam
:0:
* ^Subject: .*\[SPAM:##.*
/dev/null

# divert emails tagged as extreme spam to a different mailbox
:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
mail/spam15

# divert emails tagged as extreme spam to a different mailbox
:0:
* ^X-Spam-Level: \*\*\*\*\*
mail/spam5

# divert emails tagged as spam to a different mailbox
:0:
* ^X-Spam-Level: \*\*\*
mail/spam3