Marcin Mirosław skrev den 2015-05-05 21:21:
My goal is to configure SA to not check IP of client (in this example
31.61.129.221).
Can you elaborate about what's going on here? What do the two
hand-overs
represent? What do you mean by "real MTA"?
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. I'd like SA to check only ip which diectly connects to my
server against RBL.
please show the problem in spamassassin
are 31.61.129.221 a smtp auth user ?, in this case you should NOT add
this ip to trusted_networks since the client ip would be your server ip
in spamassassin
spamassassin -D -t sample-msg-file 2>&1 | less
in less press s to save test results, post this results headers so we
can help solve it, what mta are you using ?, and how is spamassassin
used in mta ?
Marcin
