On Wed, 08 Jun 2016 13:49:17 +0100, jimimaseye
<groachmail-stopspammin...@yahoo.com> wrote:
Regarding the range: the range belongs to our mail host provider who
receive the emails then pass them amongst their own servers (doing their
own teats no doubt). Plus they dont have just the one address - an
incoming emial can land at any of several servers (load balancing). I
dont know the EXACT range of addresses they use but I know they are all
within 195.26.90.x range (hence the cross-the-board approach to cover
all eventualities).
On 08.06.16 13:59, Kevin Golding wrote:
Try them as trusted_networks instead. From what you describe they're
not what I would classify as internal, a third party manages them.
You trust that third party so trusted_networks is fine, but
internal_networks is more for... well, internal networks.
note that if a server acts as your MX, it should be listed in
internal_networks, no matter if other company manages it.
checks like SPF dynamic IP are done on internal network boundary, not
including MX relays causes troubles
That applies for backup MX servers for your domain, or, even primary MX if
you fetch mail from it e.g. via pop3.
(yes, I know it's mentioned in the wiki, but I find it important ennough to
mention it here)
But given you've proved that SA is still viewing that rely as both
external and untrusted it comes down to tuning your trust path:
https://wiki.apache.org/spamassassin/TrustPath - don't forget to
restart spamd/however you call SA. You've basically narrowed it down
to either using old config, using a different config, or a typo in
your config. But it's definitely trust path related.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Due to unexpected conditions Windows 2000 will be released
in first quarter of year 1901
