<?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: look  fax in OWA</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/look-fax-in-owa/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/look-fax-in-owa/</link>
	<description></description>
	<pubDate>Mon, 09 Nov 2009 08:29:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: jcan123</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/look-fax-in-owa/#comment-36427</link>
		<dc:creator>jcan123</dc:creator>
		<pubDate>Tue, 18 Apr 2006 09:34:30 +0000</pubDate>
		<guid isPermaLink="false">#comment-36427</guid>
		<description>If you use a traditional product like GFIFax that integrates into exchange server, then the faxes will be seen as traditional emails in the users (fax-users) inbox. Otherwise you'll probably have to create your own HTML code to access Faxes elsewhere.</description>
		<content:encoded><![CDATA[<p>If you use a traditional product like GFIFax that integrates into exchange server, then the faxes will be seen as traditional emails in the users (fax-users) inbox. Otherwise you&#8217;ll probably have to create your own HTML code to access Faxes elsewhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->