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 - 18:18:09 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6718

--- Comment #24 from John Hardin <jhardin@impsec.org> 2011-12-10 18:18:09 UTC ---
(In reply to comment #20)
> Seems a waste of time trying to help with your development.
>
> I report a whitelist for deliberately corrupting their results to non-paying
> clients, as stated by the whitelist devs themselves, and this is the response I
> get?
>
> Well done.

(1) It is common practice for DNSBLs that have a combined pay and free usage
model to start returning invalid results when the usage from an unregistered
DNS exceeds the free usage limits. DNSWL is not the only service that does
this. MTA admins should be aware of this.

(2) Because of this it is a "best practice" to have a dedicated non-forwarding
DNS server for MTAs and antispam filters. I just checked the SA DNSBL wiki page
and we sadly don't explicitly mention this. I haven't checked the other SA
administrative documentation to see whether this is made clear, could someone
else do so?

(3) Yes, this is a duplicate of an existing bug. Unfortunately a bugzilla
search using the default options does not find it because it's been closed as
WONTFIX.

drmres, this comes across as filing a bug against SA because you don't know
enough about proper administration of a mail server, and then ranting at the
devs when this is pointed out.

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.