From owner-freebsd-questions Mon Dec 30 8:59:41 2002 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 19E7D37B401 for ; Mon, 30 Dec 2002 08:59:40 -0800 (PST) Received: from catflap.home.slightlystrange.org (www.slightlystrange.org [62.190.193.170]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1502343EC5 for ; Mon, 30 Dec 2002 08:59:39 -0800 (PST) (envelope-from dan@slightlystrange.org) Received: from danielby by catflap.home.slightlystrange.org with local (Exim 3.36 #1) id 18T3GC-000Mmd-00 for freebsd-questions@freebsd.org; Mon, 30 Dec 2002 16:59:28 +0000 Date: Mon, 30 Dec 2002 16:59:28 +0000 From: Daniel Bye To: freebsd-questions Subject: Re: spamassassin Message-ID: <20021230165928.GA87320@catflap.home.slightlystrange.org> Reply-To: dan@slightlystrange.org Mail-Followup-To: freebsd-questions References: <20021230163905.GA32067@nagual.st> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021230163905.GA32067@nagual.st> User-Agent: Mutt/1.4i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Dec 30, 2002 at 05:39:05PM +0100, dick hoogendijk wrote: > Spamassassin seems to work. It flags the messages the way it's supposed > to, but after that, I get my messages in my normal mailbox. > Why is procmail not running the next line? The spambox file is not being > created. > I've tried the X-Spam-Status and also the "* ^X-Spam-Flag: YES" but the > mail appears in my normal inbox and is not processed any further??? > > What must I do to have spamassassin tag the messages and then have a > further processing of the .procmailrc ?? > > =-=-=- > ## .procmailrc > > :0 > * ^Subject:.*sbin/get-news > /dev/null > :0: > * ^List-ID.*freebsd-questions > Mail/fbsd-questions > :0fw > | /usr/bin/spamassassin Are you sure this is the right path to spamassassin? If you installed from the port, it probably ended up in /usr/local/bin/, not in /usr/bin... If procmail can't process a rule because a pipeline command is not where you tell it, it does the right thing and returns the message to be processed by the next rule, rather than spitting its dummy and sending it to the bit bucket. > :0 > * ^X-Spam-Status: Yes > spambox > > =-=-=- When you get procmail to pass mails off through spamassassin, you may want to try running spamd/spamc - it is a daemonised version of spamassassin, and can help cut down the overhead incurred when you have to start perl up for each message - most of the execution phase with this setup is actually spent compiling the rules. Using the daemonised version will save this hit, as it will only have to process the rules once when spamd starts. Depends on how many mails you get, and whether you consider it acceptable to have a daemon perl running, though. Dan -- Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message