
<?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:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: My Gmail is Better Than Your Gmail</title>
	<atom:link href="http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/</link>
	<description>All the makings of a real web site, plus my stuff.</description>
	<lastBuildDate>Wed, 11 Aug 2010 20:44:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Jason Coleman</title>
		<link>http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/comment-page-1/#comment-41459</link>
		<dc:creator>Jason Coleman</dc:creator>
		<pubDate>Mon, 26 Mar 2007 21:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/#comment-41459</guid>
		<description>Thanks for the tip on using a different priority setting for old e-mail servers during the transfer. That seems like a really good way to go about doing this. I was fortunate in that I didn&#039;t seem to lose any important e-mails (that or they got so angry they don&#039;t speak to me anymore). However, in a business setting, I can see that being a huge problem.

I didn&#039;t see a lot of rhyme or reason to the priority setting values or how they related to one another. Then again, I didn&#039;t really look into it much.</description>
		<content:encoded><![CDATA[<p>Thanks for the tip on using a different priority setting for old e-mail servers during the transfer. That seems like a really good way to go about doing this. I was fortunate in that I didn&#8217;t seem to lose any important e-mails (that or they got so angry they don&#8217;t speak to me anymore). However, in a business setting, I can see that being a huge problem.</p>
<p>I didn&#8217;t see a lot of rhyme or reason to the priority setting values or how they related to one another. Then again, I didn&#8217;t really look into it much.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/comment-page-1/#comment-40107</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 24 Mar 2007 00:24:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/#comment-40107</guid>
		<description>I didn&#039;t want to say since I can&#039;t remember for sure, but I vaguely remember a colleague telling me about priority 70 &amp; 90 for old servers?  apparently more space between makes a larger difference.  not sure how much truth there is to that...</description>
		<content:encoded><![CDATA[<p>I didn&#8217;t want to say since I can&#8217;t remember for sure, but I vaguely remember a colleague telling me about priority 70 &amp; 90 for old servers?  apparently more space between makes a larger difference.  not sure how much truth there is to that&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott</title>
		<link>http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/comment-page-1/#comment-40097</link>
		<dc:creator>Scott</dc:creator>
		<pubDate>Sat, 24 Mar 2007 00:17:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.jasoncoleman.net/2007/03/23/my-gmail-is-better-than-your-gmail/#comment-40097</guid>
		<description>MX record changes (mail) can take quite some time, so yours wasn&#039;t really a fluke.  I&#039;ve seen DNS changes go almost instantaneously, though those were hosted with Network Solutions.  Godaddy&#039;s pretty fast, too.  anyway, during MX record updates, it&#039;s good to keep your old ones set, though with differing priorities, just something higher.  20 usually does it, and you keep both mail systems running temporarily.  typically, business changes like this are made over a weekend or holiday.  in 48-72 hours, you should be able to remove the old MX records as the new system should be receiving all the new mail.  keeping both mail server systems up until the MX record updates propagate helps prevent bounce messages, again, more important in business environments than for personal stuff.

just a little extra info for you there</description>
		<content:encoded><![CDATA[<p>MX record changes (mail) can take quite some time, so yours wasn&#8217;t really a fluke.  I&#8217;ve seen DNS changes go almost instantaneously, though those were hosted with Network Solutions.  Godaddy&#8217;s pretty fast, too.  anyway, during MX record updates, it&#8217;s good to keep your old ones set, though with differing priorities, just something higher.  20 usually does it, and you keep both mail systems running temporarily.  typically, business changes like this are made over a weekend or holiday.  in 48-72 hours, you should be able to remove the old MX records as the new system should be receiving all the new mail.  keeping both mail server systems up until the MX record updates propagate helps prevent bounce messages, again, more important in business environments than for personal stuff.</p>
<p>just a little extra info for you there</p>
]]></content:encoded>
	</item>
</channel>
</rss>
