On Fri, 2008-10-24 at 12:37 +0200, Leonardo Boselli wrote: > I think spam filter should only care about is is trusted the host that is
> passing them the message, not about the route the message has done before!
To cut a long thread short, you need to take this up with the external
host generating the error.
It's them parsing all Received: headers, so they're the ones you have a
problem with. It isn't good practice to parse all Received: headers
because they are frequently forged in spam and malware messages. If
DNSBLs are being used then they should really only reject on the IP of
the calling host; if they must check hosts in the relay chain then those
should attribute towards an overall score before taking the decision to
reject.
