<?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/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
	>
<channel>
	<title>Comments on: Loose E-mail, Fast E-mail</title>
	<atom:link href="http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/</link>
	<description>Information, Law, and the Law of Information</description>
	<lastBuildDate>Tue, 24 Nov 2009 00:08:14 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Wilson Murphy</title>
		<link>http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/comment-page-1/#comment-104437</link>
		<dc:creator>Wilson Murphy</dc:creator>
		<pubDate>Tue, 24 Nov 2009 00:07:46 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=414#comment-104437</guid>
		<description>Simply, admirable what you have done here. It is charming to see you speak from the heart and your clarity on this significant subject can be easily seen. Wonderful post and will look forward to your future update.</description>
		<content:encoded><![CDATA[<p>Simply, admirable what you have done here. It is charming to see you speak from the heart and your clarity on this significant subject can be easily seen. Wonderful post and will look forward to your future update.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: wilderness guides</title>
		<link>http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/comment-page-1/#comment-104430</link>
		<dc:creator>wilderness guides</dc:creator>
		<pubDate>Tue, 24 Nov 2009 00:03:20 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=414#comment-104430</guid>
		<description>It is very obvious you are an expert on this topic! I am setting in motion a website soon, and your information will be very useful for me.. Thanks for all your help and bidding you all the success in your business concern.</description>
		<content:encoded><![CDATA[<p>It is very obvious you are an expert on this topic! I am setting in motion a website soon, and your information will be very useful for me.. Thanks for all your help and bidding you all the success in your business concern.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Business Email Solution India</title>
		<link>http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/comment-page-1/#comment-64851</link>
		<dc:creator>Business Email Solution India</dc:creator>
		<pubDate>Thu, 18 Sep 2008 06:42:54 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=414#comment-64851</guid>
		<description>Now thats funny, One-to -many was supposed to be a solution.  I think there should be a confirmation check to ensure that the sender really wants to opt for one to many or one to one before any mail is sent.</description>
		<content:encoded><![CDATA[<p>Now thats funny, One-to -many was supposed to be a solution.  I think there should be a confirmation check to ensure that the sender really wants to opt for one to many or one to one before any mail is sent.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek Bambauer</title>
		<link>http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/comment-page-1/#comment-63629</link>
		<dc:creator>Derek Bambauer</dc:creator>
		<pubDate>Tue, 09 Sep 2008 01:09:13 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=414#comment-63629</guid>
		<description>I&#039;ve also sent the occasional accidental e-mail. It&#039;s even better than coffee as far as stimulants go.

Kent, I think that&#039;s an interesting idea. The one-to-many system initially introduced in RFC821 is the cause of a lot of problems (as well as offering tremendous efficiency, of course). It&#039;d be neat to have an algorithm implemented by the server-side MTA that held the message. The challenge might be implementing functionality that would provide the retract mechanism - I think Domino still uses the mail-tracking system to do this, and it creates a fair bit of overhead.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve also sent the occasional accidental e-mail. It&#8217;s even better than coffee as far as stimulants go.</p>
<p>Kent, I think that&#8217;s an interesting idea. The one-to-many system initially introduced in RFC821 is the cause of a lot of problems (as well as offering tremendous efficiency, of course). It&#8217;d be neat to have an algorithm implemented by the server-side MTA that held the message. The challenge might be implementing functionality that would provide the retract mechanism &#8211; I think Domino still uses the mail-tracking system to do this, and it creates a fair bit of overhead.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kent Komeri</title>
		<link>http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/comment-page-1/#comment-63517</link>
		<dc:creator>Kent Komeri</dc:creator>
		<pubDate>Mon, 08 Sep 2008 11:23:22 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=414#comment-63517</guid>
		<description>Cool off period would be a nice addition, but it comes with a few drawbacks as mentioned. The instantaneous message transfer gets interrupted. Having set up quite a few internal and external mail systems, I&#039;ve often come across delays in transfers that could essentially be used for a retraction, but that wouldn&#039;t really solve the problem.

Maybe one needs to look at this slightly differently - introduce a delay on multiple reciepients or mailing lists. This would probably be much more productive but would require each and every client to be updated with this feature as it is often the clients that have the list of reciepients. Of course this could or should also be applied to server side MTA&#039;s when sending to lists handled by these.
This approach would leave the instantant message to one person live and prosper but limit the broadcasting facility with an option to retract. You essentially get the best of both worlds.</description>
		<content:encoded><![CDATA[<p>Cool off period would be a nice addition, but it comes with a few drawbacks as mentioned. The instantaneous message transfer gets interrupted. Having set up quite a few internal and external mail systems, I&#8217;ve often come across delays in transfers that could essentially be used for a retraction, but that wouldn&#8217;t really solve the problem.</p>
<p>Maybe one needs to look at this slightly differently &#8211; introduce a delay on multiple reciepients or mailing lists. This would probably be much more productive but would require each and every client to be updated with this feature as it is often the clients that have the list of reciepients. Of course this could or should also be applied to server side MTA&#8217;s when sending to lists handled by these.<br />
This approach would leave the instantant message to one person live and prosper but limit the broadcasting facility with an option to retract. You essentially get the best of both worlds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: N. Brown</title>
		<link>http://blogs.law.harvard.edu/infolaw/2008/09/04/loose-e-mail-fast-e-mail/comment-page-1/#comment-62921</link>
		<dc:creator>N. Brown</dc:creator>
		<pubDate>Fri, 05 Sep 2008 12:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.law.harvard.edu/infolaw/?p=414#comment-62921</guid>
		<description>I am one of those idiots who accidentally used the reply all when I should have used reply.  While the result was mild amusement on the part of the recipients, it was nevertheless a &quot;close call,&quot; as I had added a humorous social note to a business email.

Since that time, I&#039;ve adopted a distinctly low tech solution to the problem.  It requires no software upgrades or server setting changes.  I simply try to avoid sending e-mails that I would be unhappy to see on the front of the World Weekly News.</description>
		<content:encoded><![CDATA[<p>I am one of those idiots who accidentally used the reply all when I should have used reply.  While the result was mild amusement on the part of the recipients, it was nevertheless a &#8220;close call,&#8221; as I had added a humorous social note to a business email.</p>
<p>Since that time, I&#8217;ve adopted a distinctly low tech solution to the problem.  It requires no software upgrades or server setting changes.  I simply try to avoid sending e-mails that I would be unhappy to see on the front of the World Weekly News.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
