<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	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/"
	>

<channel>
	<title>Blackberry=Whackberry &#187; exchange active sync</title>
	<atom:link href="http://www.whackberry.com/archives/tag/exchange-active-sync/feed" rel="self" type="application/rss+xml" />
	<link>http://www.whackberry.com</link>
	<description>BlackBerries are Whack....</description>
	<lastBuildDate>Thu, 10 Sep 2009 19:33:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>iPhone OS 3.0.1 released&#8230; GMM around the corner!</title>
		<link>http://www.whackberry.com/archives/32</link>
		<comments>http://www.whackberry.com/archives/32#comments</comments>
		<pubDate>Mon, 03 Aug 2009 14:35:40 +0000</pubDate>
		<dc:creator>TCS</dc:creator>
				<category><![CDATA[Apple iPhone]]></category>
		<category><![CDATA[Good Mobile Messaging]]></category>
		<category><![CDATA[Mobile OSX]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[exchange active sync]]></category>
		<category><![CDATA[GMM]]></category>
		<category><![CDATA[Goog Mobile Messaging]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[os 3.0.1]]></category>
		<category><![CDATA[os 3.1]]></category>
		<category><![CDATA[Security Issues]]></category>

		<guid isPermaLink="false">http://www.whackberry.com/?p=32</guid>
		<description><![CDATA[iPhone OS 3.0.1 was released to &#8220;fix&#8221; the infamous text message vulnerability.  This was expected and should have been done quite some time ago, but better late than never.  While this patch doesn&#8217;t really change too much if anything else, it does move us one step closer to Mobile OSX 3.1&#8230;. With that comes buzz [...]]]></description>
			<content:encoded><![CDATA[<p><img class="aligncenter size-full wp-image-37" title="iPhone-OS-3.0.1-Software-Update" src="http://www.whackberry.com/wp-content/uploads/2009/08/iPhone-OS-3.0.1-Software-Update1.jpg" alt="iPhone-OS-3.0.1-Software-Update" width="500" height="363" />iPhone OS 3.0.1 was released to &#8220;fix&#8221; the infamous text message vulnerability.  This was expected and should have been done quite some time ago, but better late than never.  While this patch doesn&#8217;t really change too much if anything else, it does move us one step closer to Mobile OSX 3.1&#8230;. With that comes buzz about background applications and a slew of other major impovements.</p>
<p><span id="more-32"></span>Another hot tidbit is that GMM is officially in the roadmap for Good Mobile Messaging support.  The enterprise class messaging platform is initially going to use the push notifications currently in use by select iPhone applications.  One amazing feature of this will be the ability to have two&#8230; count &#8216;em 1+1&#8230; enterprise based messaging suites.  One will utilize Good and the other will use Exchange ActiveSync.  Who should this be huge news for?  IT admins who need to monitor a test environment as well as their production environment, sniveling assistants who manage their master&#8217;s contacts, calendar, and mailbox size, and plain old people who might be running a home/personal exchange server but also need access to their corporate mailbox.</p>
<p>Now for a feature request if I may&#8230; How about Good Messaging integrating a client which has the ability to sync only one aspect of the mailbox, ie, calendar only&#8230;  This way, the super busy executive won&#8217;t have to compromise their mail to have some one wirelessly manage their calendar.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.whackberry.com/archives/32/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
