Return-Path: Received: from [65.200.169.35] (HELO TNT.AsiaFrontPage.com) by mail.stalker.com (CommuniGate Pro SMTP 4.3c5) with SMTP id 32226210 for SIMS@mail.stalker.com; Mon, 25 Apr 2005 18:20:35 -0700 Received-SPF: error receiver=mail.stalker.com; client-ip=65.200.169.35; envelope-from=CountZeroI@CipherSpace.org.in Received: from 10.9.8.129 ([10.9.8.129] verified) by TNT.AsiaFrontPage.com (Stalker SMTP Server 1.8b9d14) with ESMTP id S.0000032980; Tue, 26 Apr 2005 01:19:56 +0000 Subject: Re: e-mail recall? Date: Mon, 25 Apr 2005 21:19:53 -0400 x-mailer: Claris Emailer 2.0v3, January 22, 1998 Return-Receipt-To: Disposition-Notification-To: From: The Count of CipherSpace To: "SIMS Discussions" , "Stefan Jeglinski" Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Message-Id: Stefan Jeglinski at 2005-04-25 18:02 from jeglin@4pi.com wrote: >I just got 3 e-mails in a row from a hapless Outlook (I assume) user. >The first was the message. The second was just a message that said > > The sender would like to recall the message, "". > >where "" is just the name of the subject header in the first e-mail. > >The 3rd was obviously the edited e-mail she had intended to send. > >All of it came was sent out via their Exchange server. The time >stamps were the same on all three, to the minute anyway, so there >appeared to be some degree of automation to it. > >What is Outlook trying to do here? Is it supposed to be able to reach >into recipient's e-mail boxes and delete ("recall") certain e-mails >and replace them with others after the fact? Sounds far-fetched but I Yes. The Exchange/Outlook combination allows this; but, let me assure it (a) only works if everyone is on the same Exchange server *_and_* is using Outlook *_in_* corporate/workgroup mode (b) it doesn't work very well. A small point, it doesn't "replace" what it "takes out", basically it removes and then you send another message. >put nothing past Microsoft. Warren Michelsen at 2005-04-25 18:57 from Warren@MDCCLXXVI.com wrote: >it can recall sent messages before they are read (leaving a note to the >recipient that a message was recalled). It is also possible to recall a message "silently". Then again it is also possible to ensure that the person thinks that they have successfully recalled the message; but, you still end up with a copy of it. It is also possible that Exchange/Outlook just screws up.