J D Falk wrote:
Matthias Leisi wrote:
* Large portions of this document apply equally to black- and
Therefore it may make sense to enlarge the scope to explictly cover
whitelists as well. The general notion of "DNS-Based Reputation
would profit even more if whitelists would be explicitly included.
Call it "DNS-Based Binary Reputation Systems," and I'd agree. The full
range of reputation systems in use today is much too broad to fit into
DNS, or into this document.
* 2.2.1 Listings SHOULD be temporary: IMO this section should be
- - it describes a certain policy which may or may not fit the purpose
of a particular DNSBL.
It fits most DNSBLs, though, as a best practice.
Aside from certain types of static DNSBLs, it's always best practise.
Don't forget the document explicitly says that listings can be
* 2.2.3 Removals SHOULD be prompt: Similar to the item above,
automated removals may or may not be a good idea. Considering an
Spamhaus-SBL-type list, this SHOULD for automated removals does not
make much sense.
Most DNSBLs aren't the Spamhaus SBL. This is a best practice for just
about everything else.
SBL removals are prompt. Who said anything about automated?
Asrg mailing list