<?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: Recall, Unsend and Retract Sent Email in IBM Lotus Notes/Domino with Fetch Retriever</title>
	<atom:link href="http://www.mydigitallife.info/2007/03/06/recall-unsend-and-retract-sent-email-in-ibm-lotus-notesdomino-with-fetch-retriever/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mydigitallife.info/2007/03/06/recall-unsend-and-retract-sent-email-in-ibm-lotus-notesdomino-with-fetch-retriever/</link>
	<description>Living Digitally and Electronically</description>
	<lastBuildDate>Fri, 18 Dec 2009 06:46:58 +0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ken Gartner</title>
		<link>http://www.mydigitallife.info/2007/03/06/recall-unsend-and-retract-sent-email-in-ibm-lotus-notesdomino-with-fetch-retriever/comment-page-1/#comment-511081</link>
		<dc:creator>Ken Gartner</dc:creator>
		<pubDate>Tue, 03 Jun 2008 02:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/03/06/recall-unsend-and-retract-sent-email-in-ibm-lotus-notesdomino-with-fetch-retriever/#comment-511081</guid>
		<description>Domino now includes a message Recall Request in the 8.0 offering.  Honestly, I have only seen it work once or twice so I can appreciate how hard the problem of recall must be.  No matter how good the recall, forwarded messages, reply chains and so on are not recallable without undue effort so it is better to recall quickly if you must.

Of course, it is better to be careful to begin with.  We deal with Enterprise customers a lot and some very serious mail etiquette issues routinely occur using overly broad recipient lists, the omnipresent CC list and Reply-to-All.  Someone with a heavy hand on the  Send button can repair some damage with a fast recall, but you don&#039;t know pain and suffering until a corporate secretary mails a 1MB newsletter to 20,000 employees.  I contributed to a research paper about 6 best practices that   would make IT&#039;s job a lot easier -- way better than recalling a message is simply to prevent it to begin with. {Free - http://www.permessa.com/whitepapers/Email_Best_Practices]

We were asked to provide a solution to the Reply-to-All (and its evil cousin, Reply-to-All-with-Attachment!) and the various other major resource wastes in a Domino mail environment.  By enforcing email policy close to the sender and alerting them of specific violations (with recourse to release or discard quarantined message that were flagged), the issue of sender&#039;s remorse  is easier to deal with *and* the sender is dynamically trained as to the current policies in effect.

Regards,

Ken Gartner
Director of Software Development
http://www.permessa.com</description>
		<content:encoded><![CDATA[<p>Domino now includes a message Recall Request in the 8.0 offering.  Honestly, I have only seen it work once or twice so I can appreciate how hard the problem of recall must be.  No matter how good the recall, forwarded messages, reply chains and so on are not recallable without undue effort so it is better to recall quickly if you must.</p>
<p>Of course, it is better to be careful to begin with.  We deal with Enterprise customers a lot and some very serious mail etiquette issues routinely occur using overly broad recipient lists, the omnipresent CC list and Reply-to-All.  Someone with a heavy hand on the  Send button can repair some damage with a fast recall, but you don&#8217;t know pain and suffering until a corporate secretary mails a 1MB newsletter to 20,000 employees.  I contributed to a research paper about 6 best practices that   would make IT&#8217;s job a lot easier &#8212; way better than recalling a message is simply to prevent it to begin with. {Free &#8211; <a href="http://www.permessa.com/whitepapers/Email_Best_Practices" rel="nofollow">http://www.permessa.com/whitepapers/Email_Best_Practices</a></p>
<p>We were asked to provide a solution to the Reply-to-All (and its evil cousin, Reply-to-All-with-Attachment!) and the various other major resource wastes in a Domino mail environment.  By enforcing email policy close to the sender and alerting them of specific violations (with recourse to release or discard quarantined message that were flagged), the issue of sender&#8217;s remorse  is easier to deal with *and* the sender is dynamically trained as to the current policies in effect.</p>
<p>Regards,</p>
<p>Ken Gartner<br />
Director of Software Development<br />
<a href="http://www.permessa.com" rel="nofollow">http://www.permessa.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IBM Lotus Notes and Domino 8 Beta Free Download with Email Recall and Recent Contacts Features &#187; My Digital Life</title>
		<link>http://www.mydigitallife.info/2007/03/06/recall-unsend-and-retract-sent-email-in-ibm-lotus-notesdomino-with-fetch-retriever/comment-page-1/#comment-156863</link>
		<dc:creator>IBM Lotus Notes and Domino 8 Beta Free Download with Email Recall and Recent Contacts Features &#187; My Digital Life</dc:creator>
		<pubDate>Mon, 12 Mar 2007 05:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.mydigitallife.info/2007/03/06/recall-unsend-and-retract-sent-email-in-ibm-lotus-notesdomino-with-fetch-retriever/#comment-156863</guid>
		<description>[...] previously lack in Lotus Notes and Domino, but available in most other corporate email system. Only Fetch Retriever manages to savage IBM Lotus collaboration system from lack of ability to unsend an email. Th final [...]</description>
		<content:encoded><![CDATA[<p>[...] previously lack in Lotus Notes and Domino, but available in most other corporate email system. Only Fetch Retriever manages to savage IBM Lotus collaboration system from lack of ability to unsend an email. Th final [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
