Re: Ignoring Received: header added by real MTA

[Reindl Harald]

Am 05.05.2015 um 21:38 schrieb Marcin Mirosław:

W dniu 2015-05-05 o 21:28, Reindl Harald pisze:

Am 05.05.2015 um 21:21 schrieb Marcin Mirosław:

Thanks for both answers. I'll try to describe it using ascii art:
------------------------------            --------------------------
|random user sending email   |sends email |89.161.182.208 from this |
|(in my case: 31.61.129.221) |----------->|MTA I'm getting email    |
------------------------------            --------------------------

      --------------------------
--->|my MTA -poczta.cibet.pl |
      --------------------------

So it's not important for my if address 31.61.129.221 is on any rbl
because I'm not getting email directly from this ip. It's important for
me if server 89.161.182.208 (which directly connects to my mta) is in
any RBL

and who's MTA is 89.161.182.208?

It's not mine MTA. It is MTA used by someone on the world.

if it's a known machine realying mail for you it *is* important if
31.61.129.221 is on a RBL - hence put 89.161.182.208 in trusted_networks

then fix your internal_networks and trusted_networks settings

https://spamassassin.apache.org/full/3.4.x/doc/Mail_SpamAssassin_Conf.html

I'm thinking about removing all Received headers from email except added
by my MTA, storing it, sending email to spamd and restoring headers. But
it looks like using a sledgehammer to crack a nut:)

there is no reason to do so, a correctly configured SA would not to ddep-header inspection over all received headers - this all sounds like a config problem and until now AFAIK it's not clear hwo did you glue SA into your mailserver

signature.asc
Description: OpenPGP digital signature