Quote:
|
Originally Posted by SmartGuy
You have a horrible example.
First of all, what I am doing will reduce the "fire" in the long run. And I am not feeding the "fire" anything, but I am simply containing it to a certain area, or e-mail address for that matter.
|
no, you are feeding it by subscribing. This subscription will end up in the hands of thousands of spam lists in a matter of hours. Kinda like painting yourself with honey and then laying down in the grass next to an ant hill.
Quote:
|
Also, this is in no way supporting spam. First, it will take up system resources on their end (Sure, a trivial amount, but still.) They have one more e-mail address, that they will sell to other companies. These companies won't sell their products to me, because I will not check the e-mail address. Therefore I am HELPING in the war on spam more than I am hampering it.
|
Your logic is flawed. Spammers work on the law of averages. But RECEIVING the spam also uses resources. And now that you've exposed your domain name ACTIVELY to them, every possible dictionary name that could be associated with your domain will be hit with spam, bogging down SURPASS servers too as they process the bogus messages - even if they just bounce them.
Quote:
Bigjohn,
What harm can exposing my domain name do? Like they can't get that anyway? Are you trying to say that spammers will scour through my site, looking for e-mail addresses? They can do that anyway, also. They can get all the domains they want from a simple whois. What would make them want to index my domain more than one of yours?
|
WHOIS requires THEM to do it, and to know the domain... you can't "whois *" and get a list of all domains ever registered...
It's like this. My way: YOU have a candy in your pocket. An ant in the grass smells it. He has to climb up your leg and into your pocket to get it.
Your Way: you toss bits of that candy down onto the ground leaving a trail to your bed.
John