 




<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Categorizing Outgoing Mail</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/categorizing-outgoing-mail/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/categorizing-outgoing-mail/</link>
	<description></description>
	<lastBuildDate>Sat, 18 May 2013 17:13:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: gilliansclater</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/categorizing-outgoing-mail/#comment-64287</link>
		<dc:creator>gilliansclater</dc:creator>
		<pubDate>Mon, 08 Jun 2009 11:04:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-64287</guid>
		<description><![CDATA[Thank you so much for respondng.  I am aware of the admin controls available, but I am required to actually allow the user in real time to select one of the security options (Restricted...Top Secret etc) which I have done by intercepting the SEND action and forcing a selection.  On the basis of the selection, script in the Querysend checks the sendTo field and matchs the email addresses against predefinded lists of allowed addresses.  If an email is not allowed to be sent, then the user is notified and the email saved in drafts.  Sounds OK, but actually - it is extemely shaky and keeps falling over.  Becasue I am not an administrator, I do not know the effect this will have on the mail routing either.  What I would like to do is use the inbuilt process that you describe to halt a send (server configuration doc), but base the determination of this on the security level the user has selected.  I am not sure how this could be (if at all) achieved - there would have to be away for the server rules to recognize the categorization on the mail before it is actually sent.]]></description>
		<content:encoded><![CDATA[<p>Thank you so much for respondng.  I am aware of the admin controls available, but I am required to actually allow the user in real time to select one of the security options (Restricted&#8230;Top Secret etc) which I have done by intercepting the SEND action and forcing a selection.  On the basis of the selection, script in the Querysend checks the sendTo field and matchs the email addresses against predefinded lists of allowed addresses.  If an email is not allowed to be sent, then the user is notified and the email saved in drafts.  Sounds OK, but actually &#8211; it is extemely shaky and keeps falling over.  Becasue I am not an administrator, I do not know the effect this will have on the mail routing either.  What I would like to do is use the inbuilt process that you describe to halt a send (server configuration doc), but base the determination of this on the security level the user has selected.  I am not sure how this could be (if at all) achieved &#8211; there would have to be away for the server rules to recognize the categorization on the mail before it is actually sent.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.015 seconds using memcached
Object Caching 267/270 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-18 18:18:13 -->