<?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: Brightmail gateway compliance failure</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/brightmail-gateway-compliance-failure/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/brightmail-gateway-compliance-failure/</link>
	<description></description>
	<pubDate>Fri, 27 Nov 2009 11:20:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: KevinBeaver</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/brightmail-gateway-compliance-failure/#comment-62418</link>
		<dc:creator>KevinBeaver</dc:creator>
		<pubDate>Fri, 17 Apr 2009 20:34:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-62418</guid>
		<description>I get this a lot when sending PDFs to people. I think it's the binary aspect of the PDFs (especially if they're encrypted) that are triggering malware controls. The simplest solution would be to allow PDFs as attachments but I know there are some paranoid admins that just won't have any part of that.</description>
		<content:encoded><![CDATA[<p>I get this a lot when sending PDFs to people. I think it&#8217;s the binary aspect of the PDFs (especially if they&#8217;re encrypted) that are triggering malware controls. The simplest solution would be to allow PDFs as attachments but I know there are some paranoid admins that just won&#8217;t have any part of that.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->