jdow wrote:
From: "Marc Perkel" <[EMAIL PROTECTED]>
Rob McEwen (PowerView Systems) wrote:
Marc,
First, you should make a design decision up front... Are you going
to allow IP addresses of valid hotmail and yahoo DNS servers (for
example) which spew out a very high percentage of spams (especially
nigeria scams) on your list, or not?
The only IPs I intend to list are going to be 100% spammers. So no
Yahoo servers will be on it.
Gedanken Experiment....
Something I have noticed is that the various RBLs encode some properties
of the hits in the address returned. You might consider experimenting
with a beige list that pegs large ISPs like Yahoo, GMail, and AOL
who seem to be somewhat indiscriminate about signups. The return would
indicate whether there is current spam activity. Then the account name
could be looked up as a secondary request, name.reversedip.dnsbl. At
least these sites make it awkward to perform mass signups. And this
would tend to stifle the names right away.
(Might there be some way to use the additional information part of a
DNS return to cite active spam accounts directly?)
{^_^}
Here's what I'm trying. I'm using MyDNS but added a few fields.
Basically I'm createing a white list and a black list. The while list
merely prevents an IP from getting on the black list. An IP gets on the
whitelist for 12 hours and on the blacklist for 4 hours. The idea being
to prevent any source that sends any good email from accidentally being
blacklisted.
