DNS Blacklists Considered Harmful
draft-church-dnsbl-harmful-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Andrew Church | ||
| Last updated | 2005-08-30 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
As spam continues to grow throughout the Internet, various countermeasures have been developed. Among these is the "DNS blacklist", a DNS server configured to return a "good" or "bad" response to a query on a given IP address; mail servers can be configured to automatically query such a server and reject messages which are flagged "bad". If the blacklist is accurate, this allows mail servers to reject spam without wasting the time of the human recipient or the resources of the server. However, between delays in responding to environmental changes and arbitrary operational decisions by blacklist operators, such blocking of mail in fact causes significant harm to innocent third parties. This memo describes the issues concerning these blacklists and suggests ways to resolve the attendant problems.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)