spamassassin-dev December 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6718] DNSWL whitelist corruption

[Bug 6718] DNSWL whitelist corruption

From: <bugzilla-daemon_at_nospam>
Date: Sat Dec 10 2011 - 03:07:14 GMT

--- Comment #19 from Karsten Bräckelmann <> 2011-12-10 03:07:14 UTC ---
(In reply to comment #14)
> > > I am also not basing this on nothing. This is the result of 1200 SPAM emails
> > > received in 36 hours, [...]
> >
> > WAY below any limits.
> Below any limits for an individual with a personal account?
> This is based on ONE email account.

Since you didn't get what I just stated -- Yes, way below any free usage
limits. For which you surely would apply. As stated in numerous comments
earlier, you are not yourself exceeding any limit, but way below (sic) the

The limit, AFAIR, is 100.000 queries per day, typically much more mail than
that. And action is taken only on servers *way* above that.

In a nutshell, specifically for you: You are "WAY below any limits", and should
not get these results yourself.

> Are YOU a spammer or part of DNSWL and/or receive funding for such?!

I am not a spammer. I am not affiliated with DNSWL in any way. I am a SA
developer, support guy, and PMC member. But thanks for asking.

> > Yes, this is a duplicate, original report by Darxus I believe. Yes, this is
> > using an ISP's DNS server.
> This is not a duplicate. This proves absolutely that DNSWL deliberately corrupt
> their results.


Yes. This is a duplicate of a previously raised issue. Exactly for that reason.
This is not the first issue tracking system you use, is it?

> > To the OP: It is generally highly recommended, to run your own caching,
> > recursive (non-forwarding) nameserver with SA. This will immediately fix your
> > problem.
> Maybe. Doesn't help the other millions of users.

Yes, it does. Indeed. With your current setup, you won't get any useful results
out of a number of DNSBLs SA uses by default.

That IS the answer to your problem.

Please stop ranting, and set up the local DNS as mentioned a few times. It will
not only fix this problem of yours, but help tremendously in identifying spam.

-- Configure bugmail: ------- You are receiving this mail because: ------- You are the assignee for the bug.