Re: ATTENTION: DNSWL to be disabled by default.

> I expect a good number of „unconsious overusers“ behind the large 
> resolvers (eg a typical Spamassassin admin with misguided DNS setup), 
> but there are likely also „conscious overusers“ trying to blend into 
> that group. The number of organisations can hardly be estimated with 
> meaningful accuracy.

I was an unconscious over-user for some time.

The problem is that there is no info/hint anywhere that you hit a limit. 
I was not aware about any limits at all. I started to analyze what is 
wrong after some spam started to kick in. Then it give me a lot of time 
to figure out what is going on. From admin point of view DNSWL in 
spamassassin started to behave randomly. Sometimes I get "BLOCKED" 
response, sometimes 127.0.10.3 (listed HI as "some special cases" 
category).  Back in 2021 google search did not provide me any useful 
hints what was wrong, or I was not able to enter correct keywords for 
this problem. I eventually fixed my config and even tried to help others [1]

It should not work that way.

For my case, the solution should be:

An option DNSWL_ENABLED="off/on/auto" in spamassassin config (auto is 
default).

"auto" mode:
enable DNSWL if host resolver is set to 127.0.0.1 or eventually to DNS 
with IP in the same domain as a host where spamassassin runs. Every 
other DNS configuration should disable DNSWL at startup and then log an 
ERROR in log file with a link to documentation.

"on" will force spamassassin to use DNSWL no matter how DNS is set up. 
You have to set it manually, so it eliminates all unconsious overusers 
like me.

Regards,
Łukasz

[1] 
https://www.mail-archive.com/[email protected]/msg108935.html