 




<?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: Empty &#8220;To:&#8221;  field in Exchange 2003 SP2</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 23:54:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: chippy088</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/#comment-91201</link>
		<dc:creator>chippy088</dc:creator>
		<pubDate>Thu, 21 Apr 2011 13:22:44 +0000</pubDate>
		<guid isPermaLink="false">#comment-91201</guid>
		<description><![CDATA[@Koohisan understood, and I hadn&#039;t actually thought about that scenario. Thank you for the explanation.]]></description>
		<content:encoded><![CDATA[<p>@Koohisan understood, and I hadn&#8217;t actually thought about that scenario. Thank you for the explanation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: koohiisan</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/#comment-91159</link>
		<dc:creator>koohiisan</dc:creator>
		<pubDate>Wed, 20 Apr 2011 19:59:37 +0000</pubDate>
		<guid isPermaLink="false">#comment-91159</guid>
		<description><![CDATA[@Chippy88

To respond to your question about why I send BCC to internal recipients: sometimes I deal with issues which may involve termination, disciplinary issues, legal correspondence, etc.  There are times when I feel that I should alert the appropriate persons of authority without compromising my communication with someone being investigated.

Perhaps it is an odd scenario, but I have done this a few times and it seemed to me to be helpful.

I can definitely see your reasons for handling those types of messages the way you do!  :)]]></description>
		<content:encoded><![CDATA[<p>@Chippy88</p>
<p>To respond to your question about why I send BCC to internal recipients: sometimes I deal with issues which may involve termination, disciplinary issues, legal correspondence, etc.  There are times when I feel that I should alert the appropriate persons of authority without compromising my communication with someone being investigated.</p>
<p>Perhaps it is an odd scenario, but I have done this a few times and it seemed to me to be helpful.</p>
<p>I can definitely see your reasons for handling those types of messages the way you do!  <img src='http://itknowledgeexchange.techtarget.com/itanswers/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chippy088</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/#comment-91148</link>
		<dc:creator>chippy088</dc:creator>
		<pubDate>Wed, 20 Apr 2011 17:13:20 +0000</pubDate>
		<guid isPermaLink="false">#comment-91148</guid>
		<description><![CDATA[@Koohisan, you are right, it is wise to review. I should have said &#039;it is sent to the spam bin and reviewed before deletion.&#039; I do want confirmation that this is not a scam email, but one  from a reputable source, but i will review it in my well secured, and locked down pc. I will not take chances.

Internal emails of this sort is a company operating procedure. I still wonder why would you not want your coleagues to know who else has recieved this information?

External emails of this type are not in my mind professional. They rank among the junk mail with the &#039;To the occupant&#039; as the (im)personal detail. Hence my sending them to the spam bin, until I am ready to read them.]]></description>
		<content:encoded><![CDATA[<p>@Koohisan, you are right, it is wise to review. I should have said &#8216;it is sent to the spam bin and reviewed before deletion.&#8217; I do want confirmation that this is not a scam email, but one  from a reputable source, but i will review it in my well secured, and locked down pc. I will not take chances.</p>
<p>Internal emails of this sort is a company operating procedure. I still wonder why would you not want your coleagues to know who else has recieved this information?</p>
<p>External emails of this type are not in my mind professional. They rank among the junk mail with the &#8216;To the occupant&#8217; as the (im)personal detail. Hence my sending them to the spam bin, until I am ready to read them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: koohiisan</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/#comment-91114</link>
		<dc:creator>koohiisan</dc:creator>
		<pubDate>Tue, 19 Apr 2011 19:42:03 +0000</pubDate>
		<guid isPermaLink="false">#comment-91114</guid>
		<description><![CDATA[But, there are really good reasons for using BCC to hide the recipients!  Sometimes we need to send a message to many persons (legitimately) and not share every address with the recipients!  Also, I&#039;ve copied my boss on a lot of correspondence that would be important for him to know, without letting the normal recipient know that this was not a private thread.

So...I would be suspect if every message did come in this way...but I would not auto-delete it 100% of the time without review. 

Just my thoughts...]]></description>
		<content:encoded><![CDATA[<p>But, there are really good reasons for using BCC to hide the recipients!  Sometimes we need to send a message to many persons (legitimately) and not share every address with the recipients!  Also, I&#8217;ve copied my boss on a lot of correspondence that would be important for him to know, without letting the normal recipient know that this was not a private thread.</p>
<p>So&#8230;I would be suspect if every message did come in this way&#8230;but I would not auto-delete it 100% of the time without review. </p>
<p>Just my thoughts&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chippy088</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/#comment-91080</link>
		<dc:creator>chippy088</dc:creator>
		<pubDate>Tue, 19 Apr 2011 09:29:54 +0000</pubDate>
		<guid isPermaLink="false">#comment-91080</guid>
		<description><![CDATA[RamsayB makes a good point. We often do not need to see the email address of everyone else the message is being sent to, but  it does seem a bit weird the first time we get an email without a &#039;To&#039; addressee.

I am aware of this &#039;apparent&#039; problem through private clients. It has been mentioned to me, as i also warn users of spammers and scammers tricks. They are also using this method because it hides the other addresses from the potential &#039;target&#039;. It is a reason for concern, if the other addressees are no-one you know, or look strange.

It is potentially dangerous to allow this type of email to come into the company system, especially if the sender is unknown, as is often the case. Once opened, it can let in all sorts of unwanted problem software.

Personally, if I don&#039;t see my name in the &#039;To&#039; box I send it to the spam bin.]]></description>
		<content:encoded><![CDATA[<p>RamsayB makes a good point. We often do not need to see the email address of everyone else the message is being sent to, but  it does seem a bit weird the first time we get an email without a &#8216;To&#8217; addressee.</p>
<p>I am aware of this &#8216;apparent&#8217; problem through private clients. It has been mentioned to me, as i also warn users of spammers and scammers tricks. They are also using this method because it hides the other addresses from the potential &#8216;target&#8217;. It is a reason for concern, if the other addressees are no-one you know, or look strange.</p>
<p>It is potentially dangerous to allow this type of email to come into the company system, especially if the sender is unknown, as is often the case. Once opened, it can let in all sorts of unwanted problem software.</p>
<p>Personally, if I don&#8217;t see my name in the &#8216;To&#8217; box I send it to the spam bin.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ramseyb</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/empty-to-field-in-exchange-2003-sp2/#comment-80262</link>
		<dc:creator>ramseyb</dc:creator>
		<pubDate>Thu, 12 Aug 2010 16:21:51 +0000</pubDate>
		<guid isPermaLink="false">#comment-80262</guid>
		<description><![CDATA[I am assuming that this is not happening with every email when presenting my answer.  Some companies are now implementing protocols that intentionally leave this field empty.  The reason is so the receiver cannot gather all the other email addresses the sender sent too.  Their thought is that Joe Blow does not need to know Jane Doe&#039;s email address or that she received the same email.  Their is nothing you can do about this and it is not on your end at all.  If this is not the case sorry for wasting your time.]]></description>
		<content:encoded><![CDATA[<p>I am assuming that this is not happening with every email when presenting my answer.  Some companies are now implementing protocols that intentionally leave this field empty.  The reason is so the receiver cannot gather all the other email addresses the sender sent too.  Their thought is that Joe Blow does not need to know Jane Doe&#8217;s email address or that she received the same email.  Their is nothing you can do about this and it is not on your end at all.  If this is not the case sorry for wasting your time.</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 3/10 queries in 0.027 seconds using memcached
Object Caching 341/347 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-24 00:05:50 -->