Re: exim filter + spamassassin ?

[will trillich <will@serensoft.com>]

On Fri, Jan 03, 2003 at 02:52:15PM -0600, will trillich wrote:
> according to the docs that come with spamassassin (i've got
> woddy up now, and mainly for this reason) i can get spamassassin
> working from an exim .forward file -- but i'm already using that
> as my exim filter
> 
> 	# Exim filter
> 	logfile $home/.forward.log 0600
> 	<snip>
> 
> what machinations are required to get spamassassin up even tho
> i'm already using the .forward for filtering? or, is system-wide
> a better way to go?

let me be a bit more clear. :)

i can pipe an incoming message, using the exim filter facility,
thru any script or program, including spamassassin. but exim
doesn't want any output from such a pipe; it just wants the
return status for "okay, it's been dealt with" or "much badness
occurred". spamassassin, otoh, takes a message (say, via stdin)
and scans it, adds its headers and spits it back out -- perhaps
to the spool file (bypassing the remainder of the exim filter!)
or to stdout (which exim ignores).

how to get exim filter and spamassassin to harmoniously coexist?
or is this difficult for a reason?

-- 
I use Debian/GNU Linux version 3.0;
Linux server 2.2.17 #1 Sun Jun 25 09:24:41 EST 2000 i586 unknown
 
DEBIAN NEWBIE TIP #6 from Will Trillich <will@serensoft.com>
:
How do you keep text from SCROLLING BY TOO DAMN FAST? :)
Before pressing the ENTER key of a command that you know will
generate a lot of output, "pipe" it through your pager:
	ls -lR | pager
	locate tgz | pager
	grep -r pattern /home | pager
You can also try <SHIFT>-<PAGE-UP> to scroll back. This works
both at the console and in rxvt/xterm windows.

Also see http://newbieDoc.sourceForge.net/ ...