<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Three Steps to Knock Out Website Spam</title>
	<atom:link href="http://www.collinsinternet.com/250/three-steps-to-knock-out-website-spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.collinsinternet.com/250/three-steps-to-knock-out-website-spam/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Fri, 13 Mar 2009 17:18:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cheap Web Hosting</title>
		<link>http://www.collinsinternet.com/250/three-steps-to-knock-out-website-spam/comment-page-1/#comment-590</link>
		<dc:creator>Cheap Web Hosting</dc:creator>
		<pubDate>Fri, 02 Jan 2009 21:57:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collinsinternet.com/?p=4#comment-590</guid>
		<description>My 2 cents - Never never ever create a mailto: link that contains your email address! And never never even publish your email address in your website. There are too many spam bots out there actively crawling for email addresses.

What I suggest you guys to do is to publish your email using &#039;human readable&#039; way. What I mean is instead of publishing myemail@mysite.com, you can write as follows.

myemail AT mywebsite.com (replace AT with @)

or

myemai#mywebsite.com (replace # with @)

Which is easily understood by human but not robot. Of course it still won&#039;t stop spammer from adding your email address manually to their victim list.

Another thing to note is to use privacy protected whois for your domain name. This is to avoid spammers crawling your domain whois to get your email address.

Lastly, avoid using common email address like sales@mysite.com, support@mysite.com, webmaster@mysite.com etc. because spammers will send out spams assuming them as valid email addresses.</description>
		<content:encoded><![CDATA[<p>My 2 cents &#8211; Never never ever create a mailto: link that contains your email address! And never never even publish your email address in your website. There are too many spam bots out there actively crawling for email addresses.</p>
<p>What I suggest you guys to do is to publish your email using &#8216;human readable&#8217; way. What I mean is instead of publishing <a href="mailto:myemail@mysite.com">myemail@mysite.com</a>, you can write as follows.</p>
<p>myemail AT mywebsite.com (replace AT with @)</p>
<p>or</p>
<p>myemai#mywebsite.com (replace # with @)</p>
<p>Which is easily understood by human but not robot. Of course it still won&#8217;t stop spammer from adding your email address manually to their victim list.</p>
<p>Another thing to note is to use privacy protected whois for your domain name. This is to avoid spammers crawling your domain whois to get your email address.</p>
<p>Lastly, avoid using common email address like <a href="mailto:sales@mysite.com">sales@mysite.com</a>, <a href="mailto:support@mysite.com">support@mysite.com</a>, <a href="mailto:webmaster@mysite.com">webmaster@mysite.com</a> etc. because spammers will send out spams assuming them as valid email addresses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan Collins</title>
		<link>http://www.collinsinternet.com/250/three-steps-to-knock-out-website-spam/comment-page-1/#comment-582</link>
		<dc:creator>Allan Collins</dc:creator>
		<pubDate>Wed, 18 Jun 2008 13:44:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collinsinternet.com/?p=4#comment-582</guid>
		<description>@Michael - Thanks for the info on your service.</description>
		<content:encoded><![CDATA[<p>@Michael &#8211; Thanks for the info on your service.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Spam Blocker Michael</title>
		<link>http://www.collinsinternet.com/250/three-steps-to-knock-out-website-spam/comment-page-1/#comment-581</link>
		<dc:creator>Spam Blocker Michael</dc:creator>
		<pubDate>Wed, 18 Jun 2008 03:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collinsinternet.com/?p=4#comment-581</guid>
		<description>You also could use temporary email address from my site www.mytrashmail.com. Its completely free and will help you bigtime.</description>
		<content:encoded><![CDATA[<p>You also could use temporary email address from my site <a href="http://www.mytrashmail.com" rel="nofollow">http://www.mytrashmail.com</a>. Its completely free and will help you bigtime.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allan Collins</title>
		<link>http://www.collinsinternet.com/250/three-steps-to-knock-out-website-spam/comment-page-1/#comment-580</link>
		<dc:creator>Allan Collins</dc:creator>
		<pubDate>Wed, 18 Jun 2008 00:50:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collinsinternet.com/?p=4#comment-580</guid>
		<description>@Allen - Thanks for the info.</description>
		<content:encoded><![CDATA[<p>@Allen &#8211; Thanks for the info.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allen</title>
		<link>http://www.collinsinternet.com/250/three-steps-to-knock-out-website-spam/comment-page-1/#comment-579</link>
		<dc:creator>Allen</dc:creator>
		<pubDate>Tue, 17 Jun 2008 22:39:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.collinsinternet.com/?p=4#comment-579</guid>
		<description>As an FYI, Postini (now Google Message Security) can be set to dump all messages not sent to a protected mailbox.  This &quot;Non-Account Bounce&quot; feature eliminates all email traffic not destined for a legitimate user.</description>
		<content:encoded><![CDATA[<p>As an FYI, Postini (now Google Message Security) can be set to dump all messages not sent to a protected mailbox.  This &#8220;Non-Account Bounce&#8221; feature eliminates all email traffic not destined for a legitimate user.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
