<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Ethos Business Law &#187; email</title>
	<atom:link href="http://ethoslaw.com/blog/tag/email/feed/" rel="self" type="application/rss+xml" />
	<link>http://ethoslaw.com/blog</link>
	<description></description>
	<lastBuildDate>Thu, 17 Jun 2010 20:56:00 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Whose Email Is It?</title>
		<link>http://ethoslaw.com/blog/2009/11/20/whose-email-is-it/</link>
		<comments>http://ethoslaw.com/blog/2009/11/20/whose-email-is-it/#comments</comments>
		<pubDate>Fri, 20 Nov 2009 19:48:28 +0000</pubDate>
		<dc:creator>David Baer</dc:creator>
				<category><![CDATA[Corporate Governance]]></category>
		<category><![CDATA[Employer/Employee]]></category>
		<category><![CDATA[Professional]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[Business Law]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[Employee]]></category>
		<category><![CDATA[Professionals]]></category>

		<guid isPermaLink="false">http://ethoslaw.com/blog/?p=304</guid>
		<description><![CDATA[According to a recent article from the Wall Street Journal, some new cases have begun to erode the long-standing view that personal emails sent from a work computer can be monitored by employers. In the past, most courts have treated corporate computers, and anything on them, as company property. However, in recent rulings, courts have [...]]]></description>
			<content:encoded><![CDATA[<p>According to a recent <a href="http://online.wsj.com/article/SB125859862658454923.html" target="_blank">article</a> from the Wall Street Journal, some new cases have begun to erode the long-standing view that personal emails sent from a work computer can be monitored by employers.</p>
<p>In the past, most courts have treated corporate computers, and anything on them, as company property.  However, in recent rulings, courts have begun to investigate the circumstances around disclosure of policies to employees and other factors.  For example:</p>
<ul>
<li>In New Jersey, an appeals court ruled that an employee of a home health-care company had a reasonable expectation that email sent on a personal account wouldn&#8217;t be read.</li>
<li>In San Francisco, a federal appeals court ruled that employers that contract with an outside business to transmit text messages can&#8217;t read them unless the worker agrees.</li>
</ul>
<p>While it is probably too early to make any sweeping generalizations about this trend, it certainly suggests that employers need to review their policies, practices and training to make sure they do not run afoul of this evolving issue.</p>
]]></content:encoded>
			<wfw:commentRss>http://ethoslaw.com/blog/2009/11/20/whose-email-is-it/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Death of &#8216;Reply All&#8217;</title>
		<link>http://ethoslaw.com/blog/2009/06/05/the-death-of-reply-all/</link>
		<comments>http://ethoslaw.com/blog/2009/06/05/the-death-of-reply-all/#comments</comments>
		<pubDate>Fri, 05 Jun 2009 16:10:11 +0000</pubDate>
		<dc:creator>David Baer</dc:creator>
				<category><![CDATA[Professional]]></category>
		<category><![CDATA[Resources]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[Professionals]]></category>
		<category><![CDATA[Reply All]]></category>
		<category><![CDATA[Services]]></category>

		<guid isPermaLink="false">http://ethoslaw.com/blog/?p=131</guid>
		<description><![CDATA[Email is a powerful tool for business.  However, the ease of using email can also be a curse when mistakes are made.  In my experience, one of the most seemingly innocent, yet problematic tools in email is the &#8216;Reply All&#8217; feature. How many times have you received an email that you probably should not have [...]]]></description>
			<content:encoded><![CDATA[<p>Email is a powerful tool for business.  However, the ease of using email can also be a curse when mistakes are made.  In my experience, one of the most seemingly innocent, yet problematic tools in email is the &#8216;Reply All&#8217; feature.<span id="more-131"></span></p>
<p>How many times have you received an email that you probably should not have seen, only because the sender hit Reply All instead of just Reply.  In my practice, I have seen this time after time and on some occasions, the message sent has been very detrimental to the relationship or the transaction.  For example, while working on a contentious transaction, one of the parties on the other side intended to send an email to his colleague, but instead hit Reply All and broadcast his disgust for the seller to the entire working group.  On another occasion, I saw an email chain where an employee, intending only to reply to certain coworkers, hit Reply All and shared his critical comments on his boss with his boss and the rest of the company.</p>
<p>In addition to all the possible mistakes, how flooded is your in-box with multiple replies from a group email with a message like &#8220;Thanks.&#8221;  These seemingly simple (and unnecessary) responses can bog down an email system and frustrate an email user having to delete endless emails.</p>
<p>I believe that the &#8216;Reply All&#8217; button should be removed from most if not all email devices.  In my opinion, the potential harm outweighs the benefit and I think a little thought going into replying to an email is a good thing.</p>
]]></content:encoded>
			<wfw:commentRss>http://ethoslaw.com/blog/2009/06/05/the-death-of-reply-all/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
