 




<?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: email assessibility</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/email-assessibility/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/email-assessibility/</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 14:21:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: sonyfreek</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/email-assessibility/#comment-40375</link>
		<dc:creator>sonyfreek</dc:creator>
		<pubDate>Mon, 27 Mar 2006 19:56:22 +0000</pubDate>
		<guid isPermaLink="false">#comment-40375</guid>
		<description><![CDATA[As Cherie said, it&#039;s nit a good practice from a security standpoint.

It can be done simply by creating a contact in ADUC and setting the delivery options to both the contact and the users account.  

You&#039;re best to use OWA so that you have accountability and control.

SF]]></description>
		<content:encoded><![CDATA[<p>As Cherie said, it&#8217;s nit a good practice from a security standpoint.</p>
<p>It can be done simply by creating a contact in ADUC and setting the delivery options to both the contact and the users account.  </p>
<p>You&#8217;re best to use OWA so that you have accountability and control.</p>
<p>SF</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tedrizzi</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/email-assessibility/#comment-40376</link>
		<dc:creator>tedrizzi</dc:creator>
		<pubDate>Mon, 27 Mar 2006 15:09:02 +0000</pubDate>
		<guid isPermaLink="false">#comment-40376</guid>
		<description><![CDATA[This is done from with in outlook itself. you need to create a rule that either forwards or re-directs the email to the users home email account..
first thing to do is create a contact in the users contacts folder that contains his home email address, then using the rules wizard you can create a rule to forward or redirect to that address.. this is something that each user can do for themselves. I would recommend writing up a proceedure document and pass it out to those who wish to do it.. or you could be spending a lot of time creating rules for users.]]></description>
		<content:encoded><![CDATA[<p>This is done from with in outlook itself. you need to create a rule that either forwards or re-directs the email to the users home email account..<br />
first thing to do is create a contact in the users contacts folder that contains his home email address, then using the rules wizard you can create a rule to forward or redirect to that address.. this is something that each user can do for themselves. I would recommend writing up a proceedure document and pass it out to those who wish to do it.. or you could be spending a lot of time creating rules for users.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cherie</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/email-assessibility/#comment-40377</link>
		<dc:creator>cherie</dc:creator>
		<pubDate>Mon, 27 Mar 2006 10:49:00 +0000</pubDate>
		<guid isPermaLink="false">#comment-40377</guid>
		<description><![CDATA[I&#039;m not sure about the specifics around your company, but I would highly recommend against allowing your users to forward their corporate email to there home email accounts.  That could be potentially be a gaping security hole.  Your best bet would be to implement an Outlook Web Access (OWA) server.  But given your time constraint, I would say that&#039;s more of a long-term solution.

For the short term, if you want to do this at the server it&#039;s a two-step process.  First you have to add the user&#039;s home email account as a Contact on your mail server (an entry in the address book that points to an external email address).  Then you set that user&#039;s account to forward to that address.  Go to that user&#039;s account, and go to the Exchange General tab.  There you select Delivery Options.  In the Forwarding Address area, select Forward To then add the Contact you just created.  Be sure to select the box for &quot;Deliver messages to both...&quot; so their email will continue to go to their Exchange mailbox.

Most importantly, don&#039;t forget to turn it off when they return.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure about the specifics around your company, but I would highly recommend against allowing your users to forward their corporate email to there home email accounts.  That could be potentially be a gaping security hole.  Your best bet would be to implement an Outlook Web Access (OWA) server.  But given your time constraint, I would say that&#8217;s more of a long-term solution.</p>
<p>For the short term, if you want to do this at the server it&#8217;s a two-step process.  First you have to add the user&#8217;s home email account as a Contact on your mail server (an entry in the address book that points to an external email address).  Then you set that user&#8217;s account to forward to that address.  Go to that user&#8217;s account, and go to the Exchange General tab.  There you select Delivery Options.  In the Forwarding Address area, select Forward To then add the Contact you just created.  Be sure to select the box for &#8220;Deliver messages to both&#8230;&#8221; so their email will continue to go to their Exchange mailbox.</p>
<p>Most importantly, don&#8217;t forget to turn it off when they return.</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.014 seconds using memcached
Object Caching 296/299 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-21 14:37:03 -->