<?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: Email Overload</title>
	<atom:link href="http://www.roundpeg.biz/2009/01/email-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.roundpeg.biz/2009/01/email-2/</link>
	<description>Helping Small Business Become Big Business</description>
	<lastBuildDate>Wed, 08 Feb 2012 21:37:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Sam White</title>
		<link>http://www.roundpeg.biz/2009/01/email-2/comment-page-1/#comment-2274</link>
		<dc:creator>Sam White</dc:creator>
		<pubDate>Wed, 15 Jul 2009 14:46:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.roundpeg.biz/?p=808#comment-2274</guid>
		<description>You should check out a white paper recently released by HyperOffice.com. The whole white paper is about Email Overload, how we *try* to cope with it, and how we can overcome it. It has some great tips.
The white paper, and a corresponding slideshow, can be found at &lt;a href=&quot;http://www.hyperoffice.com/business-email-overload/&quot; rel=&quot;nofollow&quot;&gt;http://www.hyperoffice.com/business-email-overload/&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>You should check out a white paper recently released by HyperOffice.com. The whole white paper is about Email Overload, how we *try* to cope with it, and how we can overcome it. It has some great tips.<br />
The white paper, and a corresponding slideshow, can be found at <a href="http://www.hyperoffice.com/business-email-overload/" rel="nofollow">http://www.hyperoffice.com/business-email-overload/</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

