# junkfilter
# a junk e-mail filter system for procmail
# Copyright 1997-98, Gregory Sutter <gsutter@pobox.com>
#
# $Id: junkfilter.config,v 1.3 1999/03/31 11:02:23 gsutter Exp $
#
# Please read the file "junkfilter.readme" and the page
# http://www.pobox.com/~gsutter/junkfilter/ before using
# junkfilter.  junkfilter is copyright 1997-98 Gregory
# Sutter and is licensed under the terms of the GNU
# General Public License, version 2.  See the file
# junkfilter.readme for details.

# Here are the options.  Set each to "0" or "1", with
# zero being "off", and one being "on", as desired; 
# insert your own information where necessary.

# JF_USER: user-defined recipes.  I suggest using this
# file to house INCLUDERC statements to your own junk
# recipes and files.
JF_USER=0

# JF_ONE: 100% certainty spam catchers.  None of these
# rules should *ever* catch a legitimate message.
JF_ONE=1

# JF_TWO: 85%-99% certainty spam catchers.  I use them,
# but you might not want to.  These may catch a small
# amount of legit mail.  Test it to see!
JF_TWO=1

# JF_THREE: Recipes which are good at catching spam,
# but also have a tendency to capture legit mail from
# certain sources.  
JF_THREE=1

# JF_FOUR: Recipes which are in beta-test.  If you wish
# to help test new recipes, enable this.  Be careful! 
# There might be a mistake in these recipes.
JF_FOUR=1

# JF_WHITE: Implements a whitelist.  Anything matching
# a string or regexp listed in your whitelist will not
# be processed further by junkfilter.  This allows you
# to have a set of people who can always reach you,
# without fear of being caught in a spam filter.
JF_WHITE=1

# JF_DOMAINS: This recipe checks a huge list of domains.
# If any of them match any reasonable header of the mail,
# the mail is flagged.  Good for spam warehouses, etc,
# but is slow due to the long list.  If you get many
# ( > 150 ) messages per day, you might not want to use
# this section.
# JF_DOMAINS_USER: if you have your own
# personal domain list, enable this option and give the
# file location in JF_DOMAINS_USER_LOC by setting
# JF_DOMAINS_USER_LOC=$PMDIR/yourdomainsfile
JF_DOMAINS=1
JF_DOMAINS_USER=0
JF_DOMAINS_USER_LOC=$JFDIR/jf-domains-user

# JF_ADDRESSES: Similar to JF_DOMAINS, this checks a
# list of e-mail addresses.  The list is _much_ smaller,
# though, so this recipe is not a resource hog.  The USER
# and USER_LOC are as above.
JF_ADDRESSES=1
JF_ADDRESSES_USER=0
JF_ADDRESSES_USER_LOC=$JFDIR/jf-addresses-user

# JF_DIALUPS: Similar to JF_DOMAINS.  Checks a list of
# dial-up domain names.  People should have a better
# name to use than a spam-ridden dialup.  Small list.
# This is getting a bit draconic, but sometimes such
# measures are necessary...
JF_DIALUPS=1
JF_DIALUPS_USER=0
JF_DIALUPS_USER_LOC=$JFDIR/jf-dialups-user

# JF_IP: Very similar to JF_DOMAINS; checks a list of IP
# addresses and ranges.  This is a very small list and 
# won't take much time.
JF_IP=1
JF_IP_USER=0
JF_IP_USER_LOC=$JFDIR/jf-ip-user

# JF_HEADERS: Yet another list, this one of certain
# random headers (e.g. X-Advertisement:) that spammers
# insert into their messages.  It's an analogue to the
# JF_BODYCHK section.
JF_HEADERS=1
JF_HEADERS_USER=0
JF_HEADERS_USER_LOC=$JFDIR/jf-headers-user

# JF_BODYCHK: Similar to the above two, this checks the
# body of the message for any of a list of phrases and
# characters.  While phrases in the body can come from
# legitimate sources, it is still extremely valuable
# at catching spam, especially MMF and MLM schemes.
JF_BODYCHK=1
JF_BODYCHK_USER=0
JF_BODYCHK_USER_LOC=$JFDIR/jf-bodychk-user

# JFLREC is the number of times, after the first, that
# a mail message bounces around through machines at your
# local domain.  Total all Received: headers on an
# incoming email that match "Received: from [insert your
# domain(s)]".  
JFLREC=3

# JFMAILDOM: A variable containing the domain name of
# your mail host.  Be as specific (x.y.z.com) or as
# general (z.com) as necessary. Be sure to OR (|) the
# different domains if you have more than one.
JFMAILDOM=(pobox.com|psu.edu|zer0.org)

# JFMAILADDRESS: A variable containing your e-mail
# addresses.  Be sure to put in all the addresses
# where you receive mail via this copy of procmail
# and junkfilter!
JFMAILADDRESS=(gsutter@$JFMAILDOM|gss115@psu.edu)

# OPTIONS: These options enable/disable individual
# recipes throughout junkfilter.

# JF_OPT_60RECIP: the "60 recipient" rule.  Enable it
# to flag all recipes with more than 60 visible
# recipients.  (Bcc: is the proper place to put this
# many recipients.)
JF_OPT_60RECIP=1

# JF_OPT_NOTRECIP: If the address(es) in
# JFMAILADDRESS are not in the To: or Cc: header,
# the mail will be junked. This rule is really 
# only good if you're not on any mailing lists 
# or you filter them away before using junkfilter.
JF_OPT_NOTRECIP=0

# JF_OPT_XUIDL: If an X-UIDL: header is present, the
# mail will be junked.  If you download your mail via
# POP _before_ procmail processes it, you need to
# check to see if an X-UIDL header is normally
# added by the POP server.  If it is, you must keep
# this option disabled.
JF_OPT_XUIDL=1

# JF_OPT_MSN: If the message passed through the
# Microsoft Network (which generally means that it
# originated at msn), junk it.  MSN is a spammer
# haven, especially for those nasssty sex spammers.
JF_OPT_MSN=1

# JF_OPT_SENDBACK: If you wish to send messages which
# elude junkfilter back to junk@pobox.com for analysis
# so junkfilter can be improved, you _must_ enable this
# variable.  Mail sent to junk@pobox.com without the 
# header tag that this option inserts will be forwarded
# to the bit bucket.  Also, if you're doing this (and I
# appreciate it very much), you may have to specify
# where "formail" resides on your system.  If it doesn't
# work as is, use the command "which formail" or ask
# your system administrator, then insert the path to
# formail here.
JF_OPT_SENDBACK=1
JFFORMAIL="formail"

# EOF junkfilter.config