From owner-freebsd-questions@FreeBSD.ORG Sun Dec 21 06:03:34 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 3136716A4CE for ; Sun, 21 Dec 2003 06:03:34 -0800 (PST) Received: from dire.bris.ac.uk (dire.bris.ac.uk [137.222.10.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10DDF43D58 for ; Sun, 21 Dec 2003 06:03:32 -0800 (PST) (envelope-from Jan.Grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk by dire.bris.ac.uk with SMTP-PRIV with ESMTP; Sun, 21 Dec 2003 14:03:27 +0000 Received: from cmjg (helo=localhost) by mail.ilrt.bris.ac.uk with local-esmtp (Exim 3.16 #1) id 1AY4B4-0007DQ-00; Sun, 21 Dec 2003 14:03:26 +0000 Date: Sun, 21 Dec 2003 14:03:26 +0000 (GMT) From: Jan Grant X-X-Sender: cmjg@mail.ilrt.bris.ac.uk To: Lowell Gilbert In-Reply-To: <44oeu2gtsz.fsf@be-well.ilk.org> Message-ID: References: <20031220145118.6671A484C5@wastegate.net> <44oeu2gtsz.fsf@be-well.ilk.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: Jan Grant cc: freebsd-questions@freebsd.org Subject: Re: spamassassin 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: Sun, 21 Dec 2003 14:03:34 -0000 On Sun, 21 Dec 2003, Lowell Gilbert wrote: > "Doug Reynolds" writes: > > > I've been trying to setup spamassassin on my freebsd box with postfix. > > I was reading the other thread about spamassassin. What i couldn't > > figure out, was how it got the mail from the mail system. I looked at > > spamd but it didn't look like the program. I googled and still > > couldn't find a good tutorial. If someone knows of a good tutorial and > > could give me a quick explaination, i'd be greatful. Oh, I am running > > 5.1-RELEASE. thanx > > My preferred method is by filtering through procmail. It's a simple > procmail recipe: > # pass through spamassassin > :0fw: spamassassin.lock > | /usr/local/bin/spamassassin > > (where the "w" flag tells it to continue procmail processing after > running the message through spamassassin) This is ok on workstations but it's hard to manage the load on a multiuser system, since procmail is effectively a final delivery. There's also a port for MailScanner, which operates prior to final delivery on mail spools. It can integrate SpamAssassin and the virus scanner(s) of your choice; as a plus, the load generated is far more predictable. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287088 Fax +44 (0)117 9287112 http://ioctl.org/jan/ Rereleasing dolphins into the wild since 1998.