Nope, this doesn't work ... try sending yourself a CC'd mail message, and
you'll see what I mean ... I sent an email to a friend on my server, CC'd
it to myself, from a remote server, and here is the result that I've
received:
==============
Return-Path: <[EMAIL PROTECTED]>
X-Sieve: cmu-sieve 2.0
Received: by earth.hub.org (Postfix, from userid 65534)
id 978661037F6; Thu, 23 May 2002 10:38:16 -0300 (ADT)
Received: from garlic.acadiau.ca (garlic.acadiau.ca [131.162.138.193])
by earth.hub.org (Postfix) with ESMTP
id B03A21037E6; Thu, 23 May 2002 10:38:14 -0300 (ADT)
Received: from atelier.acadiau.ca (atelier.acadiau.ca [131.162.138.223])
by garlic.acadiau.ca (8.11.5/8.11.5) with ESMTP id g4NDcJG50301;
Thu, 23 May 2002 10:38:19 -0300 (ADT)
(envelope-from [EMAIL PROTECTED])
Date: Thu, 23 May 2002 10:39:34 -0300 (ADT)
From: "Marc G. Fournier" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: test2
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Status: No, hits=0.0 required=5.1 tests= version=2.20
X-Spam-Level:
===============
Notice the 'required=5.1'? My required is the default 5.0 ... I've never
changed from what was installed, but she has ...
This, again, will only work properly if there is only one recipient :(
On Mon, 20 May 2002, Daniel Pittman wrote:
> On Sat, 18 May 2002, Marc G. Fournier wrote:
> > On Sat, 18 May 2002, Daniel Pittman wrote:
> >> On Fri, 17 May 2002, Marc G. Fournier wrote:
>
> [...]
>
> >> The simple filtering mode of Postfix, using a shell script and piped
> >> data, can have the SMTP envelope information passed on the command
> >> line. I use that.
> >
> > can you post your config/scripts?
>
> Sure. In master.cf I have:
>
> spam unix - n n - - pipe
> flags=Rq user=mailfilter argv=/home/mailfilter/spam-filter ${user} -f ${sender} --
>${recipient}
>
> smtp inet n - - - - smtpd
> -o content_filter=spam:
>
> The second defines the mail filter script, run as an unprivileged user
> just in case someone manages to sneak something noxious into an email
> address or the like.
>
> The spam-filter script is:
>
> ---------- cut here ----------
> #!/bin/busybox sh
> #
> # Process mail through SpamAssassin, adding the results, then feed it back into
> # the PostFix process.
> user="$1"
> shift
>
> exec spamc -u "${user}" | /usr/sbin/sendmail -i $@
> ---------- cut here ----------
>
> This is pretty trivial, obviously, but gets the user thing right by
> passing it to the daemon correctly. It depends on home directories
> containing the right stuff. :)
>
> I found that using a statically linked busybox shell made a *huge*
> difference to the performance when processing high mail loads with the
> tools.
>
> Daniel
>
> --
> When the tyrant has disposed of foreign enemies by conquest or treaty, and
> there is nothing to fear from them, then he is always stirring up some war or
> other, in order that he people may require a leader.
> -- Plato
>
> _______________________________________________________________
> Hundreds of nodes, one monster rendering program.
> Now that's a super model! Visit http://clustering.foundries.sf.net/
>
> _______________________________________________
> Spamassassin-talk mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
