<?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: MailCo: More horsepower!</title>
	<atom:link href="http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/feed/" rel="self" type="application/rss+xml" />
	<link>http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/</link>
	<description></description>
	<lastBuildDate>Sat, 27 Feb 2010 21:34:56 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Rich Heimlich</title>
		<link>http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/comment-page-1/#comment-60750</link>
		<dc:creator>Rich Heimlich</dc:creator>
		<pubDate>Fri, 29 Feb 2008 06:00:58 +0000</pubDate>
		<guid isPermaLink="false">http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/#comment-60750</guid>
		<description>There are many things TB is falling behind in these days. So many people I show it to find it lacking in countless areas. For example, why can&#039;t it be the hub of your mail and have plug-ins for things like cell phone access (including reading and text) so that I can easily access my mail at any time but not have to run countless confusing setups to keep it all straight?</description>
		<content:encoded><![CDATA[<p>There are many things TB is falling behind in these days. So many people I show it to find it lacking in countless areas. For example, why can&#8217;t it be the hub of your mail and have plug-ins for things like cell phone access (including reading and text) so that I can easily access my mail at any time but not have to run countless confusing setups to keep it all straight?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Kuo</title>
		<link>http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/comment-page-1/#comment-60414</link>
		<dc:creator>Eric Kuo</dc:creator>
		<pubDate>Wed, 23 Jan 2008 12:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/#comment-60414</guid>
		<description>Thank goodness!  I am so tired of crappy IMAP support, crashes from outlook, etc.  Granted Thunderbird isn&#039;t too great in those department atm.  I have been proposing developing a mail client at our local linux user group as a group project.  As I was doing my presentation for it, it dawned on me that Thunderbird&#039;s main users will be business users.  I got quoted recently in a computerWorld article for my work on Firefox enterprise deployment. Other people interviewed in the article also came to the same conclusion as me about the enterprise/business users.  And that is there really isn&#039;t too much demand.  As much as Firefox is popular, we are just not seeing mass adoption by business users.  Other than that, I do like to work on a better mail client.</description>
		<content:encoded><![CDATA[<p>Thank goodness!  I am so tired of crappy IMAP support, crashes from outlook, etc.  Granted Thunderbird isn&#8217;t too great in those department atm.  I have been proposing developing a mail client at our local linux user group as a group project.  As I was doing my presentation for it, it dawned on me that Thunderbird&#8217;s main users will be business users.  I got quoted recently in a computerWorld article for my work on Firefox enterprise deployment. Other people interviewed in the article also came to the same conclusion as me about the enterprise/business users.  And that is there really isn&#8217;t too much demand.  As much as Firefox is popular, we are just not seeing mass adoption by business users.  Other than that, I do like to work on a better mail client.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Pritchard</title>
		<link>http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/comment-page-1/#comment-60400</link>
		<dc:creator>Jon Pritchard</dc:creator>
		<pubDate>Sun, 20 Jan 2008 20:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/#comment-60400</guid>
		<description>I can&#039;t wait for progress on Thunderbird to ramp up, finally having the manpower to do some amazing things. Even more so, I can&#039;t wait until you announce the hire of some interface designers David.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t wait for progress on Thunderbird to ramp up, finally having the manpower to do some amazing things. Even more so, I can&#8217;t wait until you announce the hire of some interface designers David.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Kirsch</title>
		<link>http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/comment-page-1/#comment-60385</link>
		<dc:creator>Brian Kirsch</dc:creator>
		<pubDate>Fri, 18 Jan 2008 00:51:43 +0000</pubDate>
		<guid isPermaLink="false">http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/#comment-60385</guid>
		<description>Welcome aboard Dan!

I am excited to see the new
direction for Thunderbird and 
MailCo.</description>
		<content:encoded><![CDATA[<p>Welcome aboard Dan!</p>
<p>I am excited to see the new<br />
direction for Thunderbird and<br />
MailCo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amsterdammer</title>
		<link>http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/comment-page-1/#comment-60368</link>
		<dc:creator>Amsterdammer</dc:creator>
		<pubDate>Wed, 16 Jan 2008 08:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://ascher.ca/blog/2008/01/15/mailco-more-horsepower/#comment-60368</guid>
		<description>Your work on MailCo is fine, thanks for doing this difficult job. But who works on Thunderbird 3? When does community get the first alpha?</description>
		<content:encoded><![CDATA[<p>Your work on MailCo is fine, thanks for doing this difficult job. But who works on Thunderbird 3? When does community get the first alpha?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
