Re: [exim] mangling received headers in incoming mail.

On Sun, 11 Oct 2009, Phil Pennock wrote:
> On 2009-10-11 at 18:24 +0200, Leonardo Boselli wrote:
>> With this arrangemente there is a problem: the secondary mx just refuse
>> e-mail for non-existing users, but pass all the other one to the main one.
>> The latter then cannot test on the receive headers for ill-behaving [aka:
>> spam sender] hosts.
>> Is there a way to telle exim not to add an header if the message is
>> received from one of secondary mx , that is now there is:
> You need to scan during the SMTP transaction, so that you can reject the
> message. If you accept and then scan, then either you will just be
> discarding spam, as a black hole, or generating backscatter. Both are
> sufficiently bad ideas that I won't assist with those.

No, probably i did not properli communicated the idea:
spam messages are always accepted, then passed to spamassassin that filter
and eventually sort in a spam directory. deleting spam is up to final
user.
The thing i wish is to avoid spamassassin (that runs on the lower mx) to
consider in the weighting the fact that the message came from a
"trusted" local machine.
so a
received from mx20 by mx10
received from remote by mx20
should become for spamassassin:
received from remote by mx10
I can modify both exim.conf of all mxs, of course.

> If you're using a "spam" condition in an ACL on DATA, then write the ACL
> logic such that if the connection is from one of your own machines, you
> don't do invoke the "spam" condition.

example ?