On Wed, 08 Jun 2016 07:22:19 +0100, jimimaseye
<groachmail-stopspammin...@yahoo.com> wrote:
1, You can see that Spamassassin considered and evaluated the IP address
195.26.90.72 (as reported in its report). Now this is the SECOND
received
header in the list. And yet it doesnt evaluate the most recent (first on
list) [195.26.90.113] which is also from the same range (only the final
numbers differ). Why is this? Why one and not the other? (I note that
in
all cases this final/most recent relay is never checked by SA actually.
Not
a problem, very glad of it, but dont know why).
This is because of how you're retrieving your mail - that header states it
is an authenticated user and therefore SA automatically treats that relay
as trusted.
2, I also note that it didnt say anything about [2.25.50.35]. (It
should
also have found it in the Spamhaus BL just like the MTA did).
Given the PBL listing is only the last external IP the fact that SA is
testing headers in your internal network explains why it's not testing an
IP one hop further out. Essentially it seems as if your internal_networks
is incorrectly set. Or, as your pasted config shows, not set at all. You
set that correctly in your MTA but SA won't pick up on that so you need to
add:
internal_networks 195.26.90.
You may also want to try the following in your local.cf:
add_header all Relays-Untrusted _RELAYSUNTRUSTED_
add_header all Relays-External _RELAYSEXTERNAL_
They'll add headers doing pretty much what they say on the tin - listing
external relays and untrusted relays. They can be very helpful for
debugging things like this. They should tell you pretty much exactly what
I just did.
