<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.7" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: New spambot set - powerstorm.ai.net</title>
	<link>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Tue, 02 Dec 2008 13:54:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.7</generator>

	<item>
		<title>by: Alkemisten</title>
		<link>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-61074</link>
		<pubDate>Sat, 11 Nov 2006 21:08:52 +0000</pubDate>
		<guid>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-61074</guid>
					<description>Often, a spammer uses only a few nameservers to be responsable for hundreds or even thousands of domain names that are used to generate spam. If you can locate the common nameservers and target those, you can effectively shut down all the dependent domains (and thus e-mail spam / fraudulant websites).

As a registrar can only act to suspend a domain name if the Whois information is inaccurate or incomplete, you can take direct action by filing an official complaint (ex. http://rip.gandi.net)  with the registrar where the domain name of the nameserver is registered. If indeed the Whois information is inaccurate or fradulent, and if the registrar cannot contact the registrant of the domain name, than the registrar can put the offending domain name on "Hold" status, effectively shutting down all the spamming e-mail addresses.

Thererfore, the most efficient way to truly compat spammers is to:

1. Locate the nameservers
2. See if the Whois information (registration information) is accurate
3. If that data is inaccurate, file an official complaint where the domain name of the nameserver is registered.

Do not:
1. reply to e-mails
2. trouble yourself with the domain name of the actual website or e-mail sender
3. waste time with subdomains</description>
		<content:encoded><![CDATA[<p>Often, a spammer uses only a few nameservers to be responsable for hundreds or even thousands of domain names that are used to generate spam. If you can locate the common nameservers and target those, you can effectively shut down all the dependent domains (and thus e-mail spam / fraudulant websites).</p>
<p>As a registrar can only act to suspend a domain name if the Whois information is inaccurate or incomplete, you can take direct action by filing an official complaint (ex. <a href="http://rip.gandi.net" rel="nofollow">http://rip.gandi.net</a>)  with the registrar where the domain name of the nameserver is registered. If indeed the Whois information is inaccurate or fradulent, and if the registrar cannot contact the registrant of the domain name, than the registrar can put the offending domain name on &#8220;Hold&#8221; status, effectively shutting down all the spamming e-mail addresses.</p>
<p>Thererfore, the most efficient way to truly compat spammers is to:</p>
<p>1. Locate the nameservers<br />
2. See if the Whois information (registration information) is accurate<br />
3. If that data is inaccurate, file an official complaint where the domain name of the nameserver is registered.</p>
<p>Do not:<br />
1. reply to e-mails<br />
2. trouble yourself with the domain name of the actual website or e-mail sender<br />
3. waste time with subdomains
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: darth_maul</title>
		<link>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-50007</link>
		<pubDate>Tue, 10 Oct 2006 04:09:32 +0000</pubDate>
		<guid>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-50007</guid>
					<description>Wow, I bet you are so proud of yourself.  Exactly what did you just accomplish?  Oh, that's right...nothing.</description>
		<content:encoded><![CDATA[<p>Wow, I bet you are so proud of yourself.  Exactly what did you just accomplish?  Oh, that&#8217;s right&#8230;nothing.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: A Daily Rant</title>
		<link>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-49830</link>
		<pubDate>Mon, 09 Oct 2006 13:22:16 +0000</pubDate>
		<guid>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-49830</guid>
					<description>&lt;strong&gt;Advice on AI.NET...&lt;/strong&gt;

OK, here&#8217;s a tip. Do not email AI.NET about their user&#8217;s abuse. They are more than likely part of the whole problem.
Today, shortly after sending 2 emails to AI about a bogus sub-domain of AI (powerstorm.ai.net), I got a bunch of spam attem...</description>
		<content:encoded><![CDATA[<p><strong>Advice on AI.NET&#8230;</strong></p>
<p>OK, here&#8217;s a tip. Do not email AI.NET about their user&#8217;s abuse. They are more than likely part of the whole problem.<br />
Today, shortly after sending 2 emails to AI about a bogus sub-domain of AI (powerstorm.ai.net), I got a bunch of spam attem&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: WillMacc</title>
		<link>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-49829</link>
		<pubDate>Mon, 09 Oct 2006 13:22:09 +0000</pubDate>
		<guid>http://spamhuntress.com/2006/10/09/new-spambot-set-powerstormainet/#comment-49829</guid>
					<description>I had only started my blog in June. I had actually seen them months before.</description>
		<content:encoded><![CDATA[<p>I had only started my blog in June. I had actually seen them months before.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
