Gerd von Egidy wrote:
Do you see any problems (e.g. holes for spammers) with this logic?
The only problem I see is split-DNS configurations where there's an
internal server (ie: exchange) being used as the MX in the internal
view. As a result, SpamAssassin might see a completely different host as
the MX than the outside world.
Do you think this will help reducing the need to configure trusted_networks by
hand?
No, I think it would, yet again, make it a different set of people who
need it.
Personally, I think a better way to go would be to have a config option
that selects whether the first public is trusted or not. This way the
end user could choose which of the two guessing methods to use.
