<?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: Whitelisting Made Easy</title>
	<atom:link href="http://mail2web.com/blog/2006/12/whitelisting-made-easy/feed/" rel="self" type="application/rss+xml" />
	<link>http://mail2web.com/blog/2006/12/whitelisting-made-easy/</link>
	<description>Your source for mobile device, smartphone, tablet and email information</description>
	<lastBuildDate>Tue, 22 May 2012 00:19:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: sam45</title>
		<link>http://mail2web.com/blog/2006/12/whitelisting-made-easy/comment-page-1/#comment-353200</link>
		<dc:creator>sam45</dc:creator>
		<pubDate>Wed, 28 Sep 2011 10:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://mail2web.com/blog/2006/12/whitelisting-made-easy/#comment-353200</guid>
		<description>if an innocent user gets blocked by whitelisting, that&#039;s too bad, but not as bad as something malicious getting through!</description>
		<content:encoded><![CDATA[<p>if an innocent user gets blocked by whitelisting, that&#8217;s too bad, but not as bad as something malicious getting through!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SoftCom Corporate Blog &#187; Semi-Automated Whitelisting</title>
		<link>http://mail2web.com/blog/2006/12/whitelisting-made-easy/comment-page-1/#comment-1706</link>
		<dc:creator>SoftCom Corporate Blog &#187; Semi-Automated Whitelisting</dc:creator>
		<pubDate>Wed, 05 Dec 2007 17:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://mail2web.com/blog/2006/12/whitelisting-made-easy/#comment-1706</guid>
		<description>[...] to part 3 of my series on Anti-Spam and Whitelisting.Â My lastÂ postÂ referred to a method which makes it easier for email senders and recipients to [...]</description>
		<content:encoded><![CDATA[<p>[...] to part 3 of my series on Anti-Spam and Whitelisting.Â My lastÂ postÂ referred to a method which makes it easier for email senders and recipients to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Attwood</title>
		<link>http://mail2web.com/blog/2006/12/whitelisting-made-easy/comment-page-1/#comment-1655</link>
		<dc:creator>Tim Attwood</dc:creator>
		<pubDate>Thu, 22 Feb 2007 15:08:31 +0000</pubDate>
		<guid isPermaLink="false">http://mail2web.com/blog/2006/12/whitelisting-made-easy/#comment-1655</guid>
		<description>Hi Darryl,

Unfortunately there&#039;s not a lot you can do to prevent that.  The analogy would be someone sending a letter and using your address as the return-address on the envelope.  Even though they don&#039;t live at your house, there&#039;s nothing really stopping them from using any address in the return address.  Then, if the recipient doesn&#039;t exist and the letter is &quot;Returned to Sender&quot;, it will end up in your mailbox.

However, as with snail mail, there are clues which will indicate the true origin of the mail.  But for these return receipts, theres not much more that you can do other than continue to delete them.  If you prefer, you can create a filter in your EmailAdmin or in your Email Client to trash them for you.

Hope this helps,
Tim</description>
		<content:encoded><![CDATA[<p>Hi Darryl,</p>
<p>Unfortunately there&#8217;s not a lot you can do to prevent that.  The analogy would be someone sending a letter and using your address as the return-address on the envelope.  Even though they don&#8217;t live at your house, there&#8217;s nothing really stopping them from using any address in the return address.  Then, if the recipient doesn&#8217;t exist and the letter is &#8220;Returned to Sender&#8221;, it will end up in your mailbox.</p>
<p>However, as with snail mail, there are clues which will indicate the true origin of the mail.  But for these return receipts, theres not much more that you can do other than continue to delete them.  If you prefer, you can create a filter in your EmailAdmin or in your Email Client to trash them for you.</p>
<p>Hope this helps,<br />
Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: darryl palmer</title>
		<link>http://mail2web.com/blog/2006/12/whitelisting-made-easy/comment-page-1/#comment-1657</link>
		<dc:creator>darryl palmer</dc:creator>
		<pubDate>Wed, 21 Feb 2007 18:40:04 +0000</pubDate>
		<guid isPermaLink="false">http://mail2web.com/blog/2006/12/whitelisting-made-easy/#comment-1657</guid>
		<description>my problem spam email has been going on for 2 months now.  some spammer is sending emails all around the world with a return-address saying it is from my website at softcom myhosting.  so all these emails are rejected and come back to my inbox, dozens per day.
is there a way to stop this?  right now i just delete them, what else can you do?</description>
		<content:encoded><![CDATA[<p>my problem spam email has been going on for 2 months now.  some spammer is sending emails all around the world with a return-address saying it is from my website at softcom myhosting.  so all these emails are rejected and come back to my inbox, dozens per day.<br />
is there a way to stop this?  right now i just delete them, what else can you do?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JohnPearson</title>
		<link>http://mail2web.com/blog/2006/12/whitelisting-made-easy/comment-page-1/#comment-1656</link>
		<dc:creator>JohnPearson</dc:creator>
		<pubDate>Thu, 25 Jan 2007 04:34:36 +0000</pubDate>
		<guid isPermaLink="false">http://mail2web.com/blog/2006/12/whitelisting-made-easy/#comment-1656</guid>
		<description>Nice Post.

That was well said. Always appreciate your indepth views. Keep up the great work!

John</description>
		<content:encoded><![CDATA[<p>Nice Post.</p>
<p>That was well said. Always appreciate your indepth views. Keep up the great work!</p>
<p>John</p>
]]></content:encoded>
	</item>
</channel>
</rss>

