From owner-freebsd-questions@FreeBSD.ORG Fri Apr 11 17:45:50 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E031737B401 for ; Fri, 11 Apr 2003 17:45:50 -0700 (PDT) Received: from joloxbox.joshualokken.com (12-225-249-250.client.attbi.com [12.225.249.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id D710A43FBD for ; Fri, 11 Apr 2003 17:45:49 -0700 (PDT) (envelope-from joshualokken@attbi.com) Received: from joloxbox.joshualokken.com (localhost.joshualokken.com [127.0.0.1])h3C0kRbF084120; Fri, 11 Apr 2003 17:46:30 -0700 (PDT) (envelope-from joshualokken@attbi.com) Received: (from jolok@localhost) by joloxbox.joshualokken.com (8.12.9/8.12.9/Submit) id h3C0kNhN084119; Fri, 11 Apr 2003 17:46:23 -0700 (PDT) X-Authentication-Warning: joloxbox.joshualokken.com: jolok set sender to joshualokken@attbi.com using -f Date: Fri, 11 Apr 2003 17:46:23 -0700 From: Joshua Lokken To: Dragoncrest Message-ID: <20030412004623.GA84030@joloxbox.joshualokken.com> References: <5.2.0.9.2.20030411095411.01e52ec0@pop.voyager.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="BOKacYhQ+x31HxR3" Content-Disposition: inline In-Reply-To: <5.2.0.9.2.20030411095411.01e52ec0@pop.voyager.net> User-Agent: Mutt/1.4i Organization: little to none X-OS: FreeBSD joloxbox.joshualokken.com 4.8-STABLE i386 cc: freebsd-questions@freebsd.org Subject: Re: Can someone explain how to enable spam assassin? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2003 00:45:51 -0000 --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline * Dragoncrest (dragoncrest@voyager.net) wrote: ==> I've looked through all the readme's, I've looked through the as ==> many tutorials and man pages as I can find and even the emails from this ==> list. Everyone tells me to do something different. Yet nothing seems to ==> work. Can someone please either point me to, or write out a very simple ==> how to on setting up my system from install of spam assassin to setting up ==> procmail and making sure I got everything? Thanks. I use spamassassin with procmail. Attached is the default procmailrc that is provided when spamassassin is installed. I have edited it very little. This should help you get going. -- Joshua --BOKacYhQ+x31HxR3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=".procmailrc.0" LINEBUF=4096 VERBOSE=off MAILDIR=$HOME/Mail PMDIR=$HOME/.procmail LOGFILE=$PMDIR/log INCLUDERC=$PMDIR/rc.maillists #--------------------------------------------------------------------------- # SpamAssassin sample procmailrc # # Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc' # if you use the spamc/spamd combination) # # 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. # # The lock file ensures that only 1 spamassassin invocation happens # at 1 time, to keep the load down. # :0fw: spamassassin.lock * < 256000 | spamassassin # Mails with a score of 15 or higher are almost certainly spam (with 0.05% # false positives according to rules/STATISTICS.txt). Let's put them in a # different mbox. (This one is optional.) :0: * ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\* almost-certainly-spam # All mail tagged as spam (eg. with a score higher than the set threshold) # is moved to "probably-spam". :0: * ^X-Spam-Status: Yes probably-spam # Work around procmail bug: any output on stderr will cause the "F" in "From" # to be dropped. This will re-add it. :0 * ^^rom[ ] { LOG="*** Dropped F off From_ header! Fixing up. " :0 fhw | sed -e '1s/^/F/' } --BOKacYhQ+x31HxR3--