<?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/"
		xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Domains with catch-alls being disabled</title>
	<atom:link href="http://www.purity.net/blog/2009/02/25/domains-with-catch-alls-being-disabled/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.purity.net/blog/2009/02/25/domains-with-catch-alls-being-disabled/</link>
	<description>Corporate blog for Purity Networks</description>
	<lastBuildDate>Sat, 21 Jan 2012 11:25:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Scott Webb</title>
		<link>http://www.purity.net/blog/2009/02/25/domains-with-catch-alls-being-disabled/comment-page-1/#comment-5609</link>
		<dc:creator>Scott Webb</dc:creator>
		<pubDate>Wed, 25 Feb 2009 22:37:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.easyantispam.com/blog/?p=137#comment-5609</guid>
		<description>Thanks George.  An email would be great.  I would rather proactively contact customers that their domains have catch-all issue and have been turned off rather than get an upset customer call.</description>
		<content:encoded><![CDATA[<p>Thanks George.  An email would be great.  I would rather proactively contact customers that their domains have catch-all issue and have been turned off rather than get an upset customer call.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Roberts</title>
		<link>http://www.purity.net/blog/2009/02/25/domains-with-catch-alls-being-disabled/comment-page-1/#comment-5608</link>
		<dc:creator>George Roberts</dc:creator>
		<pubDate>Wed, 25 Feb 2009 22:29:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.easyantispam.com/blog/?p=137#comment-5608</guid>
		<description>As a reminder, if your domain has been disabled and it&#039;s on an Exchange server, here&#039;s the knowledgebase article on how to set up Exchange properly to reject unknown users:

https://support.interjuncture.com/index.php?_m=knowledgebase&amp;_a=viewarticle&amp;kbarticleid=25</description>
		<content:encoded><![CDATA[<p>As a reminder, if your domain has been disabled and it&#8217;s on an Exchange server, here&#8217;s the knowledgebase article on how to set up Exchange properly to reject unknown users:</p>
<p><a href="https://support.interjuncture.com/index.php?_m=knowledgebase&#038;_a=viewarticle&#038;kbarticleid=25" rel="nofollow">https://support.interjuncture.com/index.php?_m=knowledgebase&#038;_a=viewarticle&#038;kbarticleid=25</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Roberts</title>
		<link>http://www.purity.net/blog/2009/02/25/domains-with-catch-alls-being-disabled/comment-page-1/#comment-5607</link>
		<dc:creator>George Roberts</dc:creator>
		<pubDate>Wed, 25 Feb 2009 21:47:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.easyantispam.com/blog/?p=137#comment-5607</guid>
		<description>They won&#039;t have for this round, but I&#039;ll see if I can add that functionality into the disable script before we do any more disables. For now, the easiest way to tell is to log in to the Account Manager, go to the Domains tab, click the &quot;all&quot; link, then click the &quot;Status&quot; column head to sort by status, which will bring all the disabled domains to the top.  You can then enable each one as you clear up the catch-all situation.</description>
		<content:encoded><![CDATA[<p>They won&#8217;t have for this round, but I&#8217;ll see if I can add that functionality into the disable script before we do any more disables. For now, the easiest way to tell is to log in to the Account Manager, go to the Domains tab, click the &#8220;all&#8221; link, then click the &#8220;Status&#8221; column head to sort by status, which will bring all the disabled domains to the top.  You can then enable each one as you clear up the catch-all situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Webb</title>
		<link>http://www.purity.net/blog/2009/02/25/domains-with-catch-alls-being-disabled/comment-page-1/#comment-5606</link>
		<dc:creator>Scott Webb</dc:creator>
		<pubDate>Wed, 25 Feb 2009 21:26:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.easyantispam.com/blog/?p=137#comment-5606</guid>
		<description>Will the easyantispam account holder receive an email indicating that a domain has been disabled?  I completely understand why you are doing it, but would like to be notified if possible when a domain has been disabled.  Sometimes when in a hurry the catch-all can be missed and I can see a nightmare of time wasted trying to figure out why the domain isn&#039;t getting email...</description>
		<content:encoded><![CDATA[<p>Will the easyantispam account holder receive an email indicating that a domain has been disabled?  I completely understand why you are doing it, but would like to be notified if possible when a domain has been disabled.  Sometimes when in a hurry the catch-all can be missed and I can see a nightmare of time wasted trying to figure out why the domain isn&#8217;t getting email&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

