<?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"
	>
<channel>
	<title>Comments on: Exchange Interoperability - Solved?</title>
	<atom:link href="http://www.symphonious.net/2007/04/28/exchange-interoperability-solved/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.symphonious.net/2007/04/28/exchange-interoperability-solved/</link>
	<description>Living in a state of accord.</description>
	<pubDate>Wed, 03 Dec 2008 01:53:02 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.symphonious.net/2007/04/28/exchange-interoperability-solved/#comment-73754</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sat, 28 Apr 2007 07:32:45 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/04/28/exchange-interoperability-solved/#comment-73754</guid>
		<description>I can't comment on how reliable they are but as I mentioned, Outlook itself is connecting via Outlook Web Access with the exact same settings (just hidden under a million sub dialogs).</description>
		<content:encoded><![CDATA[<p>I can&#8217;t comment on how reliable they are but as I mentioned, Outlook itself is connecting via Outlook Web Access with the exact same settings (just hidden under a million sub dialogs).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: caleb racey</title>
		<link>http://www.symphonious.net/2007/04/28/exchange-interoperability-solved/#comment-73743</link>
		<dc:creator>caleb racey</dc:creator>
		<pubDate>Sat, 28 Apr 2007 06:46:28 +0000</pubDate>
		<guid isPermaLink="false">https://www.symphonious.net/2007/04/28/exchange-interoperability-solved/#comment-73743</guid>
		<description>Beware of connecting to owa via entourage. We tried branding our login screen with university logo and tidying up the html so it was css based and wasn't nested tables etc. We left the login fields alone. However this still broke owa screen scrapers like entourage and evolution.   I'm not sure if they will work if microsoft upgrades the owa login page in the next release/upgrade/patch.</description>
		<content:encoded><![CDATA[<p>Beware of connecting to owa via entourage. We tried branding our login screen with university logo and tidying up the html so it was css based and wasn&#8217;t nested tables etc. We left the login fields alone. However this still broke owa screen scrapers like entourage and evolution.   I&#8217;m not sure if they will work if microsoft upgrades the owa login page in the next release/upgrade/patch.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
