It doesn't. It's a client-side function.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brian Eaton Sent: Thursday, April 13, 2006 7:34 PM To: [email protected] Subject: Re: [Full-disclosure] Recall: Oracle read-only user caninsert/update/delete data On 4/13/06, Michael Holstein <[EMAIL PROTECTED]> wrote: > > In my experience, it doesn't even work in an Exchange environment. > > The user gets a message that the message should be recalled, but the > > original is still there, even if it hasn't been read yet. I've heard > > people say that at one time it would auto-delete the message if it > > hadn't been read, but I've never seen that. > > It does, provided you read the "recall" message first -- but since > Outlook (by default) displays in reverse chronological order, and most > people read email in the order received, it does little good. Anybody understand how MS Exchange implements the "recall" functionality? I could see nothing in the e-mail headers that appeared to prove the sender of the original message was the sender of the recall request. - Brian _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/ _______________________________________________ Full-Disclosure - We believe in it. Charter: http://lists.grok.org.uk/full-disclosure-charter.html Hosted and sponsored by Secunia - http://secunia.com/
