Q. Who maintains SpamBouncer?
A. Locally, Bill Sebok is responsible for fetching the latest
versions. The SpamBouncer recipes themselves
are maintained gratis by Catherine Hampton of spambouncer.org.
Q. What is the difference between /local/pkg/spambouncer/sb
and /local/pkg/spambouncer/sb-new? Which should I use?
A. /local/pkg/spambouncer/sb contains the latest release
version, /local/pkg/spambouncer/sb-new contains the latest stable beta version.
Generally, stick with the release version.
Depending on which you want to use, set the appropiate variables
in $HOME/.procmailrc:
Release:
SBDIR=/local/pkg/spambouncer/sb
INCLUDERC=${SBDIR}/sb.rc
Beta:
SBDIR=/local/pkg/spambouncer/sb-new
INCLUDERC=${SBDIR}/sb-new.rc
Q. Do I have to name my mail directory "Mail"?
A. No, just make sure that the MAILDIR variable
in $HOME/.procmailrc points to your mail directory.
Q. Why was this particular email message filtered?
A. Don't ask Marc. Look at the full header of the email.
SpamBouncer writes information there as to why an email was filtered. EXAMPLE:
From: "Gary Tobin" <ttzg60@yahoo.com>
Reply-To: "Gary Tobin" <ttzg60@yahoo.com>
To: mbarker@astro.umd.edu
Subject: New wholesale medications
Date: Wed, 17 Sep 2003 01:44:49 -0200
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="D.CE5.B69280.9A9AA16B"
X-Priority: 3
X-SpamBouncer: 1.7 beta (8/18/03)
X-SBRule: Pattern Match (Drug/Pharmacy) (Score: 900)
X-SBRule: Free Email site
X-SBScore: 7 (Spam Threshold: 10) (Block Threshold: 5)
X-SBClass: Blocked
Status: RO
Content-Length: 1661
Lines: 39
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable
[-- text/html is unsupported (use 'v' to view this part) --]
You can also look at $MAILDIR/procmail.log.
Q. Spam is still getting through! What can I do?
A. Don't ask Marc. First, realize SpamBouncer is not perfect.
If it reduces to a few the spam email that get to your inbox, declare
victory and go home. Second, you can write simple recipes to do
extra sorting and/or filtering (see next page). I usually wait until
I see the same spam a number of times before writing a recipe to filter it.
Q. I've written a recipe. How do I get procmail to use it?
A. Put it in a file called, e.g., $HOME/MyRecipes.rc, then
uncomment the line in $HOME/.procmailrc
INCLUDERC=${HOME}/MyRecipes.rc
(Of course, change this line if you use a different file name!)
Q. My recipe doesn't seem to be working! What's wrong?
A. Don't ask Marc. Look at $MAILDIR/procmail.log which
will contain any error messages from parsing a particular recipe. EXAMPLE:
procmail: Invalid regexp "(^From:.*usairways.com*|\"
procmail: Skipped "^From:.*americawest.com.com|\ "
procmail: Skipped "^From:.*jetblue.com*)"
procmail: Skipped "| ${FORMAIL} -A"X-MyRecipe: Airline crap" >>${BULKFOLDER}"
Q. What does IFS= in $HOME/.forward mean?
A.
IFS=' ' sets the shell's "internal field separator" to a single
space. This is mostly just in order to prevent some old Sendmail
hacks which were based on setting the IFS to something else.