<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" 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:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>Ferris Research » Blog</title>
	
	<link>http://ferris.com</link>
	<description>Messaging. Collaboration. Compliance.</description>
	<lastBuildDate>Wed, 20 Apr 2011 22:07:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<feedburner:info uri="ferris/ferris-research-blog" /><feedburner:info uri="ferris/ferris-research-blog" /><feedburner:info uri="ferris/ferris-research-blog" /><feedburner:info uri="ferris/ferris-research-blog" /><feedburner:info uri="ferris/ferris-research-blog" /><feedburner:info uri="ferris/ferris-research-blog" /><feedburner:info uri="ferris/ferris-research-blog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/ferris/ferris-research-blog" /><feedburner:info uri="ferris/ferris-research-blog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>Gartner Wants $$ to Improve Magic Quadrant Position?</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/1tACyI4tGrg/</link>
		<comments>http://ferris.com/2010/12/09/gartner-wants-to-improve-magic-quadrant-position/#comments</comments>
		<pubDate>Thu, 09 Dec 2010 19:43:34 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=326499</guid>
		<description><![CDATA[An Open Letter to Vendors Analyst giant Gartner is defending itself against an interesting lawsuit (see links at the end of this message). In a nutshell, ZL Technologies, an archiving firm, asserts that its low ranking on the Magic Quadrant is a result of never spending money with Gartner. Gartner denies that its reviews are [...]]]></description>
			<content:encoded><![CDATA[<p>An Open Letter to Vendors</p>
<p>Analyst giant Gartner is defending itself against an interesting lawsuit (see links at the end of this message). In a nutshell, ZL Technologies, an archiving firm, asserts that its low ranking on the Magic Quadrant is a result of never spending money with Gartner. Gartner denies that its reviews are affected by fees paid to it.</p>
<p>Surprisingly, Gartner also says its opinions aren&#8217;t based on fact, but are merely assertions of opinion. This itself is potentially explosive, because Gartner normally claims its findings are based on factual and objective assessment.</p>
<p>Many vendors feel that Gartner&#8217;s assessments are a dirty business, but due to Gartner&#8217;s dominant position, they feel powerless to do anything about the situation. If they protest, Gartner will punish them. They view a Gartner subscription like a tax, something that has to be paid if you are to be a player.</p>
<p>If ZL&#8217;s contentions are correct, now is a good time for the industry to provide supporting evidence. So if you are a vendor, here are some questions we&#8217;d like to hear from you on:</p>
<ul>
<li>Did a Gartner sales person ever allude to the ability to alter a Gartner review if you paid for services from Gartner? If so, can you recall any specifics about what was said?</li>
<li>Did you notice any change in Gartner’s opinion of you after meeting with the salesperson and either paying or not paying for services?</li>
<li>Do you believe that Gartner reports are pure opinion? Or do you believe that the reports are based on fact?</li>
</ul>
<p>Please respond to me at  either <a href="mailto: david.ferris@ferris.com">david.ferris@ferris.com</a>, or +1 415 367 3436. You need to identify yourself to me, but I will not reveal your name/organization to any third party without your permission.</p>
<p>If appropriate, we may try to testify to the Federal Trade Commission. This in turn would likely trigger e-discovery at Gartner. If this confirms that Gartner&#8217;s views can be bought, this would confirm ZL&#8217;s assertions, and would be very damaging to Gartner. Your identity would be kept entirely anonymous and no-one, including Gartner, will ever know you&#8217;ve testified.</p>
<p>Hope to hear from you!</p>
<p><a href="mailto: david.ferris@ferris.com">David Ferris</a></p>
<p>1 415 367 3436</p>
<p>Court Documents:</p>
<p>* <a href="http://www.scribd.com/doc/42785566/Appellant-s-Corrected-Opening-Brief-Case-No-10-16061">Appellant’s (ZL’s) Opening Brief</a><br />
* <a href="http://www.scribd.com/doc/42785578/ZL-v-Gartner-Appellee-s-Brief">Appellee’s (Gartner’s) Opposition</a><br />
* <a href="http://www.scribd.com/doc/42785570/Appellant-s-Reply-Brief">ZL’s Reply</a></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/P5A1JeFK8FY" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/6mZgNO6Vfyg" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/k9pEERP7irI" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/zuRTQdOfGNQ" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/Tilc-2hw-EI" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/ypEIxJmNTuI" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/-zrOksbMPlU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/1tACyI4tGrg" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/12/09/gartner-wants-to-improve-magic-quadrant-position/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/12/09/gartner-wants-to-improve-magic-quadrant-position/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/P5A1JeFK8FY/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/6mZgNO6Vfyg/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/k9pEERP7irI/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/zuRTQdOfGNQ/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/Tilc-2hw-EI/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/ypEIxJmNTuI/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/-zrOksbMPlU/</feedburner:origLink></item>
		<item>
		<title>Symantec To Acquire LiveOffice?</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/Li_p_MXnaO4/</link>
		<comments>http://ferris.com/2010/09/28/symantec-to-acquire-liveoffice/#comments</comments>
		<pubDate>Tue, 28 Sep 2010 16:47:54 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Archiving & eDiscovery]]></category>
		<category><![CDATA[Gossip Threads]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=326146</guid>
		<description><![CDATA[We hear strong rumors to the effect that Symantec is about to acquire LiveOffice. We believe them to be reliable. This wouldn&#8217;t be surprising: Symantec is building its cloud-based offering It has a strong on-premises archiving product (Enterprise Vault) LiveOffice provides a strong cloud-based archiving offering Nick Mehta, CEO, was in charge of Symantec&#8217;s Enterprise [...]]]></description>
			<content:encoded><![CDATA[<p>We hear strong rumors to the effect that Symantec is about to acquire LiveOffice. We believe them to be reliable.</p>
<p>This wouldn&#8217;t be surprising:</p>
<ul>
<li>Symantec is building its cloud-based offering</li>
<li>It has a strong on-premises archiving product (Enterprise Vault)</li>
<li>LiveOffice provides a strong cloud-based archiving offering</li>
<li>Nick Mehta, CEO, was in charge of Symantec&#8217;s Enterprise Vault business until 2007</li>
</ul>
<p>On  the downside, the LiveOffice archiving capability is very different  from that of Enterprise Vault. Only limited integration between the two  would seem practical.</p>
<p><a href="mailto:david@ferris.com">david.ferris@ferris.com </a></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/GqEFeNG6uY8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/j2N_QmHIKKs" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/RefRqRFczVQ" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/9WlQTo38hgM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/ORdUn_xqH4Q" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/fZfa9GHwxoU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/T36OMgH2sVw" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/Li_p_MXnaO4" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/09/28/symantec-to-acquire-liveoffice/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/09/28/symantec-to-acquire-liveoffice/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/GqEFeNG6uY8/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/j2N_QmHIKKs/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/RefRqRFczVQ/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/9WlQTo38hgM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/ORdUn_xqH4Q/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/fZfa9GHwxoU/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/T36OMgH2sVw/</feedburner:origLink></item>
		<item>
		<title>Here You Have Virus Wreaks Havoc</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/hQZeqaBd7f8/</link>
		<comments>http://ferris.com/2010/09/09/here-you-have-virus-wreaks-havoc/#comments</comments>
		<pubDate>Fri, 10 Sep 2010 03:01:58 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=326013</guid>
		<description><![CDATA[A new &#34;Here You Have&#34; virus is wreaking havoc on email servers around the globe. Early reports suggest users in at least 90% of all government departments and the majority of companies have been hit. It&#8217;s too early to understand the full scale of the damages, but if playing with Google&#8217;s logo can cause millions [...]]]></description>
			<content:encoded><![CDATA[<p>A new &quot;Here You Have&quot; virus is wreaking havoc on email servers around the globe. Early reports suggest users in at least 90% of all government departments and the majority of companies have been hit. It&#8217;s too early to understand the full scale of the damages, but if playing with <a href="http://www.digitaljournal.com/pr/108040%20">Google&#8217;s logo</a> can cause millions in lost productivity, then deleting dozens of &quot;here you have&quot; e-mails from in-boxes everywhere will incur similar damages.</p>
<p><font face="Arial, Helvetica, sans-serif" size="-1">Until the dust settles our advice is simple. If it looks suspicious, don&#8217;t click, forward or otherwise open the e-mail. There you have it.</font></p>
<p><font face="Arial, Helvetica, sans-serif" size="-1"><br />
  <a href="mailto:david@ferris.com">david.ferris@ferris.com </a></font></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/NY6f33HWing" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/DFQVy-6t3DU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/lkqfaQPuNik" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/lg-mbGse24I" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/G--JjOG8rp8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/9s2oExMZmQo" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/vhAFZaVywyg" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/hQZeqaBd7f8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/09/09/here-you-have-virus-wreaks-havoc/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/09/09/here-you-have-virus-wreaks-havoc/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/NY6f33HWing/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/DFQVy-6t3DU/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/lkqfaQPuNik/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/lg-mbGse24I/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/G--JjOG8rp8/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/9s2oExMZmQo/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/vhAFZaVywyg/</feedburner:origLink></item>
		<item>
		<title>Sponsorship Opportunity: Practical Advice on Setting Retention Policy</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/QXJp9zS0LHw/</link>
		<comments>http://ferris.com/2010/09/01/sponsorship-opportunity-practical-advice-on-setting-retention-policy/#comments</comments>
		<pubDate>Wed, 01 Sep 2010 15:03:08 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Webinars]]></category>
		<category><![CDATA[Archiving & eDiscovery]]></category>
		<category><![CDATA[Free Reports]]></category>
		<category><![CDATA[Member Reports]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325954</guid>
		<description><![CDATA[Vendors: Don&#8217;t miss this opportunity to sponsor an important and influential project. Ferris Research is close to completion of a white paper and webcast on how long electronic material should be kept until it&#8217;s deleted. The project will generate significant interest: This is the first time the overall electronic retention landscape has been presented. Other [...]]]></description>
			<content:encoded><![CDATA[<p>Vendors: Don&#8217;t miss this opportunity to sponsor an important and influential project.</p>
<p>Ferris  Research is close to completion of a white paper and webcast on how  long electronic material should be kept until it&#8217;s deleted. The project  will generate significant interest:</p>
<ul>
<li>This is the first time  the overall electronic retention landscape has been presented. Other  work on electronic retention limits itself, narrowly, to email</li>
<li>It provides very valuable advice on how to decide and implement retention policy. Actionable advice isn&#8217;t available elsewhere</li>
<li>It  provides a clear vision of how electronic retention will be done in ten  years time. They are invaluable for IT strategic planning</li>
</ul>
<p>The table of contents and executive summary can be seen <a href="http://dl.dropbox.com/u/10235922/832-Ret-Pols-Best-Practices-09df-TOC-ES-1.pdf/" class="broken_link">here</a>. The final white paper will be published on September 29, on the same day that we&#8217;ll hold the webcast.</p>
<p>An inexpensive sponsorship program, starting at $2,495, is available to vendors: see <a href="http://ferris.com/2010/09/01/services/ret-pol-sponsorship" class="broken_link">here</a> for details. This is a great marketing opportunity:</p>
<ul>
<li>Electronic retention is a complex and hot topic, confusion abounds</li>
<li>The content of the paper and webcast are important</li>
<li>The  content of the paper and webcast help your prospects decide what to do  about retention. That speeds sales, and deployment, and thus revenues</li>
<li>The  paper and webcast will be widely disseminated and discussed, because of  their importance. You will want to have your name and logo on it. You  won&#8217;t want to have your competitors&#8217; names and logos there and be missed  out</li>
<li>Sponsor PR staff will be promoting the white paper and  webcast heavily. The material is a good opportunity for you to be seen  as a thought leader</li>
<li>The material can be used for lead generation programs</li>
</ul>
<p>For further information, or a copy of the full draft white paper, contact David Ferris at +1 415 367 3436, or <a href="mailto:david.ferris@ferris.com">david.ferris@ferris.com</a>.</p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/CNf17n4pZrU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/6CONXscICZo" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/pz9CeQ2iLso" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/ien4b40oTwg" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/MMto6eYryJs" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/SlTb3NavJbc" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/jnN0DH2bk6I" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/QXJp9zS0LHw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/09/01/sponsorship-opportunity-practical-advice-on-setting-retention-policy/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/09/01/sponsorship-opportunity-practical-advice-on-setting-retention-policy/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/CNf17n4pZrU/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/6CONXscICZo/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/pz9CeQ2iLso/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/ien4b40oTwg/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/MMto6eYryJs/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/SlTb3NavJbc/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/jnN0DH2bk6I/</feedburner:origLink></item>
		<item>
		<title>Google Wave High and Dry</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/bqBRc9-rlkU/</link>
		<comments>http://ferris.com/2010/08/10/google-wave-high-and-dry/#comments</comments>
		<pubDate>Tue, 10 Aug 2010 17:36:01 +0000</pubDate>
		<dc:creator>David Sengupta</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[MS Exchange]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325855</guid>
		<description><![CDATA[Google quietly announced the end of Google Wave on its blog earlier this week. The reason given was that adoption rates were too low. Just over a year ago we wrote about Google’s big splash around Google Wave. One of the things we pointed out at the time was Wave’s suitability for third-party developers to [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://googleblog.blogspot.com/2010/08/update-on-google-wave.html">Google quietly announced</a> the end of Google Wave on its blog earlier this week. The reason given was that adoption rates were too low.</p>
<p>Just over a year ago <a href="../2009/07/21/a-belated-take-on-google-wave/" class="broken_link">we wrote about Google’s big splash around Google Wave</a>.  One of the things we pointed out at the time was Wave’s suitability for  third-party developers to write applications to take advantage of this  platform. In order for a large vendor to be successful at introducing a  new development platform – such as Google Wave – a substantial partner  ecosystem needs to be developed and nurtured to adopt the new platform.  Good technology alone is never sufficient to ensure success in the  marketplace.</p>
<p>As our friend Dana Blankenhorn has <a href="http://www.zdnet.com/blog/open-source/lessons-from-google-wave-failure/7025">alluded</a>,  simply going it alone, tossing great technology out there, and hoping  that the market will converge around any given technology is no  replacement for a solid business model. At least Google had the good  sense to recognize the problem and do something about it. That takes  guts.</p>
<p>Google Wave was cool. But in business there’s more to surfing than simply finding a cool wave.</p>
<p><em>&#8230;<a href="mailto:david.sengupta@ferris.com">David Sengupta</a>.</em> <em>In  addition to his role as Ferris analyst, David is chief architect for  Quest Software, and has been a Microsoft Exchange MVP since 1998.</em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/SuXmMGUC0wY" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/rclboOzp3UQ" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/hlvS0sEHFGo" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/gwbjMHtTzV0" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/P7h9ZTO8hms" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/szsMO1uESfo" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/IZeWtVw38Rs" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/bqBRc9-rlkU" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/08/10/google-wave-high-and-dry/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/08/10/google-wave-high-and-dry/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/SuXmMGUC0wY/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/rclboOzp3UQ/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/hlvS0sEHFGo/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/gwbjMHtTzV0/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/P7h9ZTO8hms/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/szsMO1uESfo/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/IZeWtVw38Rs/</feedburner:origLink></item>
		<item>
		<title>BlackBerry Bans: A Question of Business, or Ethics?</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/UkFf4pC3Tgw/</link>
		<comments>http://ferris.com/2010/08/09/blackberry-bans-a-question-of-business-or-ethics/#comments</comments>
		<pubDate>Mon, 09 Aug 2010 17:00:03 +0000</pubDate>
		<dc:creator>David Sengupta</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[MS Exchange]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325848</guid>
		<description><![CDATA[Research in Motion (RIM) has been in the news a lot lately because countries like the UAE, Saudi Arabia, and others plan to ban BlackBerry services from their citizens. Specifically Messenger, Web browsing, and email are deemed a security threat by the governments of these countries, for various reasons. In the majority of cases, governments [...]]]></description>
			<content:encoded><![CDATA[<p>Research in Motion (RIM) has been in the news a lot lately because  countries like the UAE, Saudi Arabia, and others plan to ban BlackBerry  services from their citizens. Specifically Messenger, Web browsing, and  email are deemed a security threat by the governments of these  countries, for various reasons. In the majority of cases, governments  are concerned by their inability to eavesdrop into BlackBerry  communications.</p>
<p>Yet, according to RIM, “the BlackBerry enterprise  solution was designed to preclude RIM&#8211;or any third party&#8211;from reading  encrypted information under any circumstances since RIM does not store  or have access to the encrypted data” (source: <a href="http://www.zdnet.co.uk/news/mobile-it/2010/08/04/rim-denies-security-kowtowing-to-governments-40089733/">ZDNet</a>). Thus, blocking governments’ ability to tap into RIM communications is by design.</p>
<p>Isn’t  it interesting that many of the countries threatening to ban the  BlackBerry are some of the worst proponents of Internet censorship? RIM  President and co-CEO Mike Lazaridis got it right when he stated to the  WSJ: <a href="http://online.wsj.com/article/SB10001424052748704017904575409093226146722.html">“If they can&#8217;t deal with the Internet, they should shut it off.”</a> Technologies such as BlackBerry, Twitter, Facebook, and the Internet  itself are all just tools that can be used for good or evil. Being able  to communicate securely can provide great benefits for democracy, as  seen in Iran during the uprisings last year following the election.  Terrorists can, of course, also use these technologies for evil.</p>
<p>RIM  has done a great job providing a solid infrastructure that is used by  millions around the globe for reliable and secure communications. RIM  services have withstood large-scale power outages, 9/11, <a href="http://www.alaskajournal.com/stories/041506/loc_20060415019.shtml">Hurricane Katrina</a>,  and numerous other natural disasters. Kudos to RIM for standing in the  face of opposition. Our hope is that RIM will not back down and enable  back doors for surveillance such as those <a href="http://blogs.skype.com/en/2008/10/skype_president_addresses_chin.html">found in Skype clients distributed in China.</a></p>
<p>Just  because the BlackBerry can be a tool for evil does not mean that its  effectiveness should be compromised for the rest of the world. If some  governments can’t live with that, they should go ahead with their bans.</p>
<p><em>&#8230;<a href="mailto:david.sengupta@ferris.com">David Sengupta.</a></em> <em>In  addition to his role as Ferris analyst, David is chief architect for  Quest Software, and has been a Microsoft Exchange MVP since 1998.</em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/9r_NVXXQ__M" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/_aETGD5Zlz8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/6wOXZdsk7bM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/0QylNwd5NRI" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/JcvU7xfV7EU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/gQVItfUVDMs" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/PQdRgFz-Ua8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/UkFf4pC3Tgw" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/08/09/blackberry-bans-a-question-of-business-or-ethics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/08/09/blackberry-bans-a-question-of-business-or-ethics/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/9r_NVXXQ__M/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/_aETGD5Zlz8/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/6wOXZdsk7bM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/0QylNwd5NRI/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/JcvU7xfV7EU/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/gQVItfUVDMs/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/PQdRgFz-Ua8/</feedburner:origLink></item>
		<item>
		<title>IMAP Support in Outlook 2010</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/qtevvu5C0RE/</link>
		<comments>http://ferris.com/2010/08/06/imap-support-in-outlook-2010/#comments</comments>
		<pubDate>Fri, 06 Aug 2010 15:57:00 +0000</pubDate>
		<dc:creator>kille</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Archiving & eDiscovery]]></category>
		<category><![CDATA[MS Exchange]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325838</guid>
		<description><![CDATA[Microsoft Outlook can be used to access email using the Internet Standard IMAP protocols, and the older POP protocol. In Outlook 2010, Microsoft made a number of improvements to IMAP support. Both the descriptions of what has been done and the extensive comment in this blog are interesting. Broadly, IMAP in Outlook 2010 works reasonably, [...]]]></description>
			<content:encoded><![CDATA[<p>Microsoft Outlook can be used to access email using the Internet  Standard IMAP protocols, and the older POP protocol. In Outlook 2010,  Microsoft made a number of <a href="http://blogs.msdn.com/b/outlook/archive/2010/02/06/better-imap-in-outlook-2010.aspx">improvements to IMAP support</a>. Both the descriptions of what has been done and the extensive comment in this blog are interesting.</p>
<p>Broadly,  IMAP in Outlook 2010 works reasonably, and performance against IMAP  accounts feels slightly better than Outlook 2007. However, we have  observed client hangs (needing product restart) and slowness interacting  with IMAP servers.</p>
<p>The improvements to deletion, by moving  messages to a &#8220;trash&#8221; folder on the server, are good. This deletion also  works cleanly with Outlook rules set up to delete selected messages as  they arrive.</p>
<p>The async download of messages is a good thing. It is  a pity that they don&#8217;t also download the message structure so that the  user can select attachments to download, which would be helpful with  large attachments on a slow link. It is disconcerting to see a message  start off without an attachment and then have the attachment appear  later. There is a bug with calendar items, whereby you can only see the  message as a calendar item the second time it is opened (after the  attachment is downloaded).</p>
<p>For IMAP users, there seems to be a  regression in using TNEF (the Microsoft internal format, that  non-Exchange users see as &#8220;winmail.dat&#8221; attachments) rather than MIME,  and it does not appear possible to suppress this for message forwarding  as attachment and at some other times.</p>
<p>For use in a mobile  environment, where links are not always as fast as they should be, it is  a pity that Outlook is not making more use of advanced IMAP and  LEMONADE features to improve the user experience.</p>
<p>IMAP support in Outlook 2010 has improved, but Microsoft could do very much more.</p>
<p><em>&#8230;Steve  Kille. Steve is a periodic contributor to Ferris Research. He is also  CEO of Isode, a messaging and directory server software vendor.</em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/3mENQNQ6gpA" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/uAyZzRZwmJ8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/bNR4CRo_nyA" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/bGJ_bDKN5k8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/W9B-TfRlZ0g" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/UQ83H5P0fy8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/IiOu0nN-Re8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/qtevvu5C0RE" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/08/06/imap-support-in-outlook-2010/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/08/06/imap-support-in-outlook-2010/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/3mENQNQ6gpA/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/uAyZzRZwmJ8/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/bNR4CRo_nyA/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/bGJ_bDKN5k8/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/W9B-TfRlZ0g/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/UQ83H5P0fy8/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/IiOu0nN-Re8/</feedburner:origLink></item>
		<item>
		<title>Clearswift Update</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/qnG-yEZeDj8/</link>
		<comments>http://ferris.com/2010/07/29/clearswift-update-2/#comments</comments>
		<pubDate>Thu, 29 Jul 2010 15:53:38 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Malware]]></category>
		<category><![CDATA[Mergers & Acquisitions]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325795</guid>
		<description><![CDATA[We&#8217;ve just been briefed by Clearswift&#8216;s new COO, Andrew Wyatt. It&#8217;s always a pleasure to hear from this firm. We have known them since 1995, when Content Technologies (the company that originally developed MIMEsweeper) became a client. The technology has taken a lot of battering over the last 10 years. First it was bought out [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve just been briefed by <a href="http://www.clearswift.com/home">Clearswift</a>&#8216;s  new COO, Andrew Wyatt. It&#8217;s always a pleasure to hear from this firm.  We have known them since 1995, when Content Technologies (the company  that originally developed MIMEsweeper) became a client.</p>
<p>The  technology has taken a lot of battering over the last 10 years. First it  was bought out for $1 billion by Baltimore Technologies. We are not  normally given to hyperbole, but in this case will make an exception.  YES, AN INCREDIBLE $1 BILLION!!! This was at the height of the dot.com  boom in 2000. The acquisition and its price made no real sense, but the  price was naturally irresistible for the selling stockholders. The  Baltimore merger was a great distraction.</p>
<p>In 2002 the technology  was bought by NET-TEL, an X.400-based messaging firm, for a suitably  post-crunch sum vastly less than $1 billion. The MIMEsweeper part of  NET-TEL&#8217;s business was by far the most important, but the new owners  took a long time to get fully behind their acquisition. That did further  damage. Along the way, NET-TEL renamed itself Clearswift.</p>
<p>For the  last three years, Clearswift has been focusing hard on its core  MIMEsweeper business. Despite the numerous distractions of the last  decade, many MIMEsweeper customers have stayed in the fold, so there&#8217;s  been a reliable revenue stream. MIMEsweeper and Clearswift’s new Web and  Email Gateway products are quite sticky, because of investment  customers make in their custom-policy definitions. The main message we  hear now from Clearswift is: &#8220;Content inspection is our core business  and we&#8217;re 100% committed to it.&#8221;</p>
<p>Product line summary:</p>
<ul>
<li>Scans Web and email data streams</li>
<li>Scans for spam, viruses, spyware, other malware</li>
<li>Powerful  and highly recursive policy definition language (mainly boolean logic  plus regular expression matching) used, among other things, for  compliance and data loss prevention</li>
<li>Policy-based encryption, either through strong encryption or by standard password-based ZIP files</li>
<li>Plenty of compliance filters provided</li>
<li>Policy management system works across both Web and email channels</li>
</ul>
<p>The  technology is sold into organizations of all sizes, including very  large ones. Nevertheless, its greatest success is with medium-size  organizations, with 100 to 3,000 employees. As you&#8217;d expect, the company  sells a lot through value-added channels, and has invested  significantly to build out its channel and support programs.</p>
<p>Clearswift  doesn&#8217;t disclose its revenues. Ferris Research estimates these at $40  million annually. A series of venture fundings allowed Clearswift to  invest ahead of revenues for an extended period. We&#8217;re glad to learn  that the company was profitable for the second half of the last fiscal  year and plans to be fully profitable this year.</p>
<p>&#8230; <em><a href="mailto:david.ferris@ferris.com">David Ferris</a></em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/135eyQl_yNU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/-9bd96_XmEQ" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/t7b4-_oc_6c" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/Bw2eYgkxRgA" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/tn7Ru1iLCE4" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/b6VFF8M7G1Y" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/-R_97yYB3HA" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/qnG-yEZeDj8" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/07/29/clearswift-update-2/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/07/29/clearswift-update-2/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/135eyQl_yNU/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/-9bd96_XmEQ/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/t7b4-_oc_6c/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/Bw2eYgkxRgA/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/tn7Ru1iLCE4/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/b6VFF8M7G1Y/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/-R_97yYB3HA/</feedburner:origLink></item>
		<item>
		<title>IMAP Enhancements in iPhone OS Update (iOS 4)</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/N2Jz1vtWVZY/</link>
		<comments>http://ferris.com/2010/07/28/imap-enhancements-in-iphone-os-update-ios-4/#comments</comments>
		<pubDate>Wed, 28 Jul 2010 17:42:11 +0000</pubDate>
		<dc:creator>kille</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325777</guid>
		<description><![CDATA[Apple&#8217;s recent update to the iPhone operating system (iOS 4) contains some updates to the IMAP (the Internet Standard Internet Message Access Protocol) support. Details here. The RFCs now supported are: COMPRESS (4978) ESEARCH (4731) CHUNKING (3030) 8BITMIME (1652) ENHANCEDSTATUSCODES (3463) BINARYMIME (3030) CONDSTORE (4551) These standards are also supported by Apple&#8217;s Mobile Me email [...]]]></description>
			<content:encoded><![CDATA[<p>Apple&#8217;s recent update to the iPhone operating system (iOS 4) contains  some updates to the IMAP (the Internet Standard Internet Message Access  Protocol) support. Details <a href="http://developer.apple.com/iphone/library/navigation/index.html">here</a>. The RFCs now supported are:</p>
<ul>
<li>COMPRESS (4978)</li>
<li>ESEARCH (4731)</li>
<li>CHUNKING (3030)</li>
<li>8BITMIME (1652)</li>
<li>ENHANCEDSTATUSCODES (3463)</li>
<li>BINARYMIME (3030)</li>
<li>CONDSTORE (4551)</li>
</ul>
<p>These standards are also supported by Apple&#8217;s Mobile Me email service.</p>
<p>We  have previously argued that mobile email will drive adoption of new  IMAP standards, and in particular those defined in the LEMONADE Profile,  described in Isode&#8217;s white paper, <a href="http://www.isode.com/whitepapers/lemonade-profile.html">&#8220;LEMONADE Profile: The Key Standard for Mobile Messaging.&#8221;</a></p>
<p>This  change has certainly not come as a revolution, but these developments  in the iPhone suggest that these changes are coming gradually as an  evolution and improvement. Support for two of these standards (both  edited by Isode engineers) is of particular interest:</p>
<ul>
<li>CONDSTORE  (described in the white paper) is a complex specification that is key  to fast reconnect, which we have not seen supported in an email client  designed for a mobile device until now. Thunderbird 3 supports  CONDSTORE.</li>
<li>ESEARCH (extended search) allows a client to  efficiently search very large mailboxes. This is included in the second  LEMONADE Profile, <a href="http://www.rfc-editor.org/rfc/rfc5550.txt">RFC 5550</a>, and is not described in the white paper.</li>
</ul>
<p>Since  the LEMONADE work started, typical network bandwidth has increased  significantly and so it is much easier to work without these extensions.  However, use of these capabilities will improve performance for the end  user, and differentiate iPhone email performance. LEMONADE capabilities  will give a faster user experience, and will also reduce network  traffic, which will improve battery performance and may reduce network  usage charges.</p>
<p>We hope that this is the start of a trend for improved IMAP support in other email clients and mobile devices.</p>
<p><em>&#8230;Steve Kille.</em> <em>Steve is a periodic contributor to Ferris Research. He is also CEO of Isode, a messaging and directory server software vendor.</em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/IiXlLcgDL5M" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/LtrQfeWHInE" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/UXzPDK3kLQU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/_IRNlvbp0AM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/mUYWUsxLBp8" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/paU-MoMAGRM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/F1u3vlZScyE" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/N2Jz1vtWVZY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/07/28/imap-enhancements-in-iphone-os-update-ios-4/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/07/28/imap-enhancements-in-iphone-os-update-ios-4/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/IiXlLcgDL5M/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/LtrQfeWHInE/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/UXzPDK3kLQU/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/_IRNlvbp0AM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/mUYWUsxLBp8/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/paU-MoMAGRM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/F1u3vlZScyE/</feedburner:origLink></item>
		<item>
		<title>Red Gate Announces Exchange Server Archiver V3</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/hr2zdrIGjYo/</link>
		<comments>http://ferris.com/2010/07/27/red-gate-announces-exchange-server-archiver-v3/#comments</comments>
		<pubDate>Tue, 27 Jul 2010 18:14:51 +0000</pubDate>
		<dc:creator>bspurzem</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Archiving & eDiscovery]]></category>
		<category><![CDATA[MS Exchange]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325770</guid>
		<description><![CDATA[We ran into the Red Gate team at the recent Microsoft TechEd show and learned about the new release of Exchange Server Archiver V3. The major new change with version 3 is support for Exchange 2010. In addition, version 3 provides improved performance and a new simplified storage architecture. Exchange Server Archive V3 continues its [...]]]></description>
			<content:encoded><![CDATA[<p>We ran into the Red Gate team at the recent Microsoft TechEd show and  learned about the new release of Exchange Server Archiver V3. The major  new change with version 3 is support for Exchange 2010. In addition,  version 3 provides improved performance and a new simplified storage  architecture.</p>
<p>Exchange Server Archive V3 continues its tradition  of easy installation and simple operation. End users will like the  Outlook interface, which displays archived email and attachments in  their native format. Admins will like the easy-to-use setup, archive  policy manager, and PST archiving tool. You can view product screen  shots <a href="http://www.red-gate.com/products/Exchange/gallery.htm">here</a>.</p>
<p>Red  Gate is targeting the small to midsize enterprise market (50-1,000  mailboxes) and pricing is very reasonable. For example, the price for  250 mailboxes according to <a href="http://www.red-gate.com/products/Exchange/pricing.htm">the online pricing calculator</a> is $5,597.50 plus support and maintenance.</p>
<p>Red  Gate is perhaps a name you have not heard of in the crowded email  archiving market, but we like the look of its technology and the overall  product seems very well thought out. We recommend you take a look if  you are in the market for email archiving. A <a href="http://www.red-gate.com/products/Exchange/index.htm?source=ferris10">free 30-day trial</a>, with full technical support, is available as a download from the Web site, as well as online demos and webinars.</p>
<p>&#8230; <em><a href="mailto:bob.spurzem@ferris.com">Bob Spurzem </a></em>- In addition to his role as Ferris analyst, Bob is director of product marketing at Permabit, which offers a grid-based disk storage system.</p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/Y8tJN6ecaTQ" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/n3IpN8XxQpY" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/NhhQXTii5zE" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/MDxiNMdQbRk" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/goH180NZXMw" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/5vSAKpphEcc" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/nVC7sYKG7Pc" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/hr2zdrIGjYo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/07/27/red-gate-announces-exchange-server-archiver-v3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/07/27/red-gate-announces-exchange-server-archiver-v3/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/Y8tJN6ecaTQ/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/n3IpN8XxQpY/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/NhhQXTii5zE/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/MDxiNMdQbRk/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/goH180NZXMw/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/5vSAKpphEcc/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/nVC7sYKG7Pc/</feedburner:origLink></item>
		<item>
		<title>Unify Merges with Daegis: Transaction Comments</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/AxoaGXxWEJY/</link>
		<comments>http://ferris.com/2010/06/30/unify-merges-with-daegis-transaction-comments/#comments</comments>
		<pubDate>Thu, 01 Jul 2010 02:55:46 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Archiving & eDiscovery]]></category>
		<category><![CDATA[Mergers & Acquisitions]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325652</guid>
		<description><![CDATA[On June 22, 2010, Unify announced it would merge with Daegis, an e-discovery review firm. Here are some thoughts on the transaction: According to Kurt Jensen, CEO of Daegis, revenues for calendar years 2007/8/9 were approximately $16M, $21M, and $23M, respectively, with profitability consistently between 25% and 35%. Unify paid some $37M for Daegis. Of [...]]]></description>
			<content:encoded><![CDATA[<p>On June 22, 2010, Unify announced it would <a href="http://www.unify.com/News-Events/pressReleases.aspx?ReleaseID=169719">merge  with Daegis</a>, an e-discovery review firm. Here are some thoughts on  the transaction:</p>
<ul>
<li>According to Kurt Jensen, CEO of Daegis,  revenues for calendar years 2007/8/9 were approximately $16M, $21M, and  $23M, respectively, with profitability consistently between 25% and 35%.</li>
<li>Unify  paid some $37M for Daegis. Of this, $24M is paid cash (debt financing  from Hercules Technology Growth Capital). The balance is in Unify stock.</li>
<li>This  is a price/TTM revenue ratio of around 1.5. This strikes us as a  remarkably low price. Todd Wille, Unify CEO, comments that &#8220;Daegis is  receiving a significant portion of the proceeds in Unify stock which is  perceived to be undervalued and represents tremendous upside to the  sellers.&#8221; All the same, the ratio should please Unify shareholders.</li>
<li>Corporate  legal departments want to bring as much of the e-discovery work  in-house as they can, because of the high costs of outsourcing this  work. There is thus intense pressure on review firms to reduce their  charges. Generally, expect plenty of case management firms to be  acquired over the next couple of years.</li>
<li>The strong profitability  reported by Daegis is all the more striking given the price pressure.  Partly this is because most of Daegis&#8217; software is home brewed, not  licensed. Daegis believes additional factors are the breadth of the  e-discovery processes that its software encompasses, and the provision  of high-margin professional services.</li>
<li>In principle, Unify gains  substantially by the merger:
<ul>
<li>Gets a position in the legal world,  and the ability to market to the legal world.</li>
<li>Can get an  interesting competitive edge by tightly integrating case management  information and archiving. Such integration is hard and could end in  tears.</li>
<li>It helps corporate legal departments bring more  e-discovery work in-house.</li>
</ul>
</li>
</ul>
<p>&#8230; <em><a href="mailto:david.ferris@ferris.com">David Ferris</a></em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/2aei4mKiCRg" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/5vm5V3ijQ40" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/zUwStTQ6nbA" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/22lfn7o0GAQ" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/vkgjT7K5Vkw" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/ELKbxTbbLLg" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/MU7ls-UFjaE" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/AxoaGXxWEJY" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/06/30/unify-merges-with-daegis-transaction-comments/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/06/30/unify-merges-with-daegis-transaction-comments/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/2aei4mKiCRg/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/5vm5V3ijQ40/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/zUwStTQ6nbA/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/22lfn7o0GAQ/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/vkgjT7K5Vkw/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/ELKbxTbbLLg/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/MU7ls-UFjaE/</feedburner:origLink></item>
		<item>
		<title>Unify Merges with e-Disco Review Firm Daegis</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/4jEtg_0rs9o/</link>
		<comments>http://ferris.com/2010/06/30/unify-merges-with-e-disco-review-firm-daegis/#comments</comments>
		<pubDate>Wed, 30 Jun 2010 16:32:03 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Mergers & Acquisitions]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325646</guid>
		<description><![CDATA[Unify is a database tools company that acquired archiving software vendor AXS-One in June 2009. On June 22, 2010, Unify announced it would merge with Daegis, an e-discovery review firm: Daegis has a matter review SaaS that culls down a corpus of ESI. It also provides manpower to plan the initial collection process and the [...]]]></description>
			<content:encoded><![CDATA[<p>Unify is a database tools company that <a href="../2009/05/05/unify-buys-axs-one/" class="broken_link">acquired  archiving software vendor AXS-One</a> in June 2009. On June 22, 2010,  Unify announced it would <a href="http://www.unify.com/News-Events/pressReleases.aspx?ReleaseID=169719">merge  with Daegis</a>, an e-discovery review firm:</p>
<ul>
<li>Daegis has a  matter review SaaS that culls down a corpus of ESI. It also provides  manpower to plan the initial collection process and the actual  review/culling.</li>
<li>Unify&#8217;s AXS-One archiving software will be  integrated tightly with Daegis&#8217; <a href="http://www.daegis.com/dochunter/">DocHunter eDiscovery system</a>.</li>
<li>Unify&#8217;s  archiving and e-discovery group will adopt the Daegis name.</li>
</ul>
<p>Today,  ESI archives are wholly separate from e-discovery systems. Data is  extracted from the archive and put into an e-discovery system. Thus, the  following types of information are normally not included in the  archive:</p>
<ul>
<li>How valuable the material is for e-discovery.</li>
<li>Who  has reviewed the material.</li>
<li>Who is the custodian of the  material.</li>
<li>Cases that have used the material.</li>
</ul>
<p>In a  novel step, Unify/Daegis plans to change all this. The archive will be  enhanced so that it now contains e-discovery information.</p>
<p>Comments:</p>
<ul>
<li>Unify will now be able to offer technology plus a proven  professional services team that produces relevant e-discovery material,  all in one organization. That&#8217;s a significant differentiator in the  archiving world.</li>
<li>Unify will also be able to let general counsel  bring much of the e-discovery work in-house. This would be extremely  attractive to many organizations, due to the significant cost of  outsourcing this work.</li>
<li>The idea of building case management data  into an archive is very interesting. E-discovery is now the major  driver for archiving purchases, and e-discovery is very expensive.  Adding case management information to the archive should, in principle,  translate to substantially better searches, and substantial reductions  in legal costs.</li>
<li>On the other hand, e-discovery is simply one  application of an archive. You could argue that an archive should be  more application-independent.</li>
<li>It makes sense to use the Daegis  name. Daegis is known in the legal world, and e-discovery is a major  driver for archiving; Unify&#8217;s name is only known in the database tools  world.</li>
<li>Integrating the AXS-One and Daegis code sets and data  structures will be challenging, all the more so because Daegis&#8217; system  is hosted, while Unify&#8217;s software resides on the customer&#8217;s premises.  Many organizations fail at such integration. The roadmap should be  viewed with appropriate caution.</li>
<li>Daegis staff have a lot of  experience extracting material from archiving solutions. However, they  have relatively little experience with AXS-One archiving. That may be a  problem.</li>
<li>It&#8217;s good to see Unify investing further in its AXS-One  acquisition.</li>
</ul>
<p>&#8230; <em><a href="mailto:david.ferris@ferris.com">David Ferris</a></em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/n6t2ppxhnXg" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/9rLuEb43ot4" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/9f5l4DblCLM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/lEWbGBVtv-o" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/qQz7YQ3pHoc" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/PAGK5d1ohvY" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/OaV23Br5MuA" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/4jEtg_0rs9o" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/06/30/unify-merges-with-e-disco-review-firm-daegis/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/06/30/unify-merges-with-e-disco-review-firm-daegis/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/n6t2ppxhnXg/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/9rLuEb43ot4/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/9f5l4DblCLM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/lEWbGBVtv-o/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/qQz7YQ3pHoc/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/PAGK5d1ohvY/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/OaV23Br5MuA/</feedburner:origLink></item>
		<item>
		<title>File Archiving Goes Mainstream</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/IsycAfExRmM/</link>
		<comments>http://ferris.com/2010/06/29/file-archiving-goes-mainstream/#comments</comments>
		<pubDate>Tue, 29 Jun 2010 18:07:00 +0000</pubDate>
		<dc:creator>bspurzem</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Archiving & eDiscovery]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325631</guid>
		<description><![CDATA[Recently at the Gartner IT Infrastructure Expo in Orlando, I witnessed a seminal change in IT thinking. Nine out of 10 IT decision makers I spoke with told me that they have active general-purpose file archiving projects. Hitherto, email archiving has been at the fore, with file archiving always on the back burner. The general [...]]]></description>
			<content:encoded><![CDATA[<p>Recently at the Gartner IT Infrastructure Expo in Orlando, I witnessed a seminal change in IT thinking. Nine out of 10 IT decision makers I spoke with told me that they have active general-purpose file archiving projects.</p>
<p>Hitherto, email archiving has been at the fore, with file archiving always on the back burner. The general thinking on file archiving was to just add more disk capacity.</p>
<p>The new emphasis on file archiving is driven by the total cost of disk storage. Disk hardware may be cheap, but the real cost is in disk management. Daily backup and provisioning can consume 50% of an administrator’s total time. Simply adding more disk capacity is too expensive.</p>
<p>The proper solution is to consider a true storage tier that is optimized for cost-effective, long-term storage. New storage solutions are being announced by all the leading storage vendors that include not only high-capacity SATA disk drives, but grid architectures for scalability without expensive provisioning, and object-based storage designs that are self-healing and do not require old-fashioned tape backup. And finally, data optimization (both compression and deduplication) is being introduced as a further means to optimize storage costs.</p>
<p>Archive storage will become a mainstream storage solution for all organizations by 2012.</p>
<p>&#8230; Bob Spurzem</p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/odBxsbDfTm0" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/ISDbesRsQWs" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/i5JuAjWSQYI" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/e7_XLRhanls" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/g-yp0OH_CWM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/s0Eif4hKW2U" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/n6LyPR93AL4" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/IsycAfExRmM" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/06/29/file-archiving-goes-mainstream/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/06/29/file-archiving-goes-mainstream/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/odBxsbDfTm0/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/ISDbesRsQWs/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/i5JuAjWSQYI/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/e7_XLRhanls/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/g-yp0OH_CWM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/s0Eif4hKW2U/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/n6LyPR93AL4/</feedburner:origLink></item>
		<item>
		<title>Migrating Email and Archives to the Cloud</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/iQdbpWSYKYo/</link>
		<comments>http://ferris.com/2010/06/28/migrating-email-and-archives-to-the-cloud/#comments</comments>
		<pubDate>Mon, 28 Jun 2010 18:17:51 +0000</pubDate>
		<dc:creator>bspurzem</dc:creator>
				<category><![CDATA[Blog]]></category>
		<category><![CDATA[Archiving & eDiscovery]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325606</guid>
		<description><![CDATA[There are many factors to consider when moving email and email archives to the cloud. Three important ones are: Do you presently have on-premise email archiving? If so, then you must consider how to move the email archiving storage to the cloud. The cost of this move can be considerable, in terms of load fees, [...]]]></description>
			<content:encoded><![CDATA[<p>There are many factors to consider when moving email and email  archives to the cloud. Three important ones are:</p>
<ul>
<li>Do you  presently have on-premise email archiving? If so, then you must consider  how to move the email archiving storage to the cloud. The cost of this  move can be considerable, in terms of load fees, disrupted user time,  and support staff time.</li>
<li>Do you plan to archive email in the  cloud? If so, what archiving capabilities are offered by your cloud  email provider? Will they meet your needs for e-discovery and mailbox  management? What is the additional cost?</li>
<li>Do you plan to postpone  cloud email for two to three years, but begin email archiving now? If  so, then consider how you will move potentially terabytes of email  archives to the cloud later. You may wish to begin cloud archiving now  to lessen the future impact.</li>
</ul>
<p>They key factor to remember is  the size of email archive storage. Even a couple years of email can be  terabytes of storage. Moving terabytes of email storage from on-premise  to the cloud is a formidable and costly task. Keep this important issue  in mind as you consider the benefits of cloud email.</p>
<p>&#8230; <em><a href="mailto:bob.spurzem@ferris.com">Bob  Spurzem</a></em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/xcq64KrXu-U" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/fKACV2Wen_M" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/dLdFDqkfHIU" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/WDZpZnT1Gr4" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/tnpqTc80wqM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/G9USDNaxdws" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/sfHS14VlazE" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/iQdbpWSYKYo" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/06/28/migrating-email-and-archives-to-the-cloud/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/06/28/migrating-email-and-archives-to-the-cloud/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/xcq64KrXu-U/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/fKACV2Wen_M/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/dLdFDqkfHIU/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/WDZpZnT1Gr4/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/tnpqTc80wqM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/G9USDNaxdws/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/sfHS14VlazE/</feedburner:origLink></item>
		<item>
		<title>Royal Email Deleted to Obstruct Justice</title>
		<link>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/0txTnqXGeTI/</link>
		<comments>http://ferris.com/2010/06/26/royal-email-deleted-to-obstruct-justice/#comments</comments>
		<pubDate>Sat, 26 Jun 2010 13:08:36 +0000</pubDate>
		<dc:creator>David Ferris</dc:creator>
				<category><![CDATA[Blog]]></category>

		<guid isPermaLink="false">http://www.ferris.com/?p=325597</guid>
		<description><![CDATA[Nice bit of gossip arising from a London court case. It is said that: A British UK property developer was working with a partner (Middle Eastern royalty). They wanted to develop a part of central London. The UK&#8217;s Prince of Wales objected to the development, and contacted the partner. There&#8217;s a nice email record of [...]]]></description>
			<content:encoded><![CDATA[<p>Nice bit of gossip arising from a London court case. It is said that:</p>
<ul>
<li>A British UK property developer was working with a partner  (Middle Eastern royalty).</li>
<li>They wanted to develop a part of  central London.</li>
<li>The UK&#8217;s Prince of Wales objected to the  development, and contacted the partner.</li>
<li>There&#8217;s a nice email  record of the interaction.</li>
<li>As a result, the partner backed out.</li>
<li>The  partner deleted the email correspondence with the Prince of Wales, so  it wouldn&#8217;t have to pay around $120 million in compensation to the  developer.</li>
<li>The partner then lied to the UK courts about its  reason for backing out.</li>
</ul>
<p>More <a href="http://news.bbc.co.uk/2/hi/england/london/10310638.stm">here</a>.</p>
<p>&#8230;  <em><a href="mailto:david.ferris@ferris.com">David  Ferris</a></em></p>
<img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/qGF5lvfHZV4" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/QwWh3l9sJaY" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/ygQLFf1ojGI" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/5JS7hkg6nxM" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/vk9PCf3Mo8w" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/boInJ_geTWA" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/QHsrnEHbwwc" height="1" width="1"/><img src="http://feeds.feedburner.com/~r/ferris/ferris-research-blog/~4/0txTnqXGeTI" height="1" width="1"/>]]></content:encoded>
			<wfw:commentRss>http://ferris.com/2010/06/26/royal-email-deleted-to-obstruct-justice/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://ferris.com/2010/06/26/royal-email-deleted-to-obstruct-justice/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/qGF5lvfHZV4/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/QwWh3l9sJaY/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/ygQLFf1ojGI/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/5JS7hkg6nxM/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/vk9PCf3Mo8w/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/boInJ_geTWA/</feedburner:origLink><feedburner:origLink>http://feedproxy.google.com/~r/ferris/ferris-research-blog/~3/QHsrnEHbwwc/</feedburner:origLink></item>
	</channel>
</rss>
