"Jared Hall via users" <users@spamassassin.apache.org> writes:
> Here's the actual use case: > > 1) Stefan's a web guy. He hosts his stuff at ScalaHosting. > 2) ScalaHosting provides a one-click install of SpamAssassin. > 3) Stefan doesn't know what DNS that SpamAssassin instance (think like > a CloudWays App, or Digital Ocean droplet) is using. It could be a > public DNS; could be ScalaHosting's DNS. The big point to me is that if ScalaHosting is selling "SpamAssassin as a Service" then they are responsible for doing it correctly which includes DNS routing to comply with reasonable query limits. Basically, if you set it up yourself, you have to run your own resolver, and if someone does it for you, it's on them to set it up right. I see the point of unhappiness with incorrect data being returned, but I'm ok with that as long as it's not automated and a last resort for IP addresses that don't answer complaints via whois channels.
