Charles Marcus a écrit : > On 3/9/2009, Jorey Bump (l...@joreybump.com) wrote: >> Isn't this best implemented at the MUA level? At the very least, a user >> can simply save drafts of all composed email, then review & send >> messages periodically. Not only does this address the problem, it is >> more convenient for everyone, including the user, who can edit the >> message in place before finally sending. > > It will never fail that the user will decide right after clicking the > send button that they want to recall it, no matter how long they wait > prior to sending... >
and they will also decide to recall it after it was "released" ;-p > I can't tell you how many times I've had to explain to one of our users > why we cannot recall their message - whcih usually ends up with me > describing how this exchange capability works, and why it only works > under certain limited circumstances, which does NOT include any > destinations that are NOT exchange servers configured to cooperate with > these requests. > next time: insult him, then "recall the insult", and see if he accepts ;-p or if he is stronger than you, ask him how to recall a phone call ;--p > I only said it was an interesting idea, and wondered if it could be > automated... I'm still not sure it *should* be done... :) > it can be automated. the hard part is to define the criteria (when to keep, when to "release") and how to recall (how does user tell the system that he wants to recall a message, and in particular, how to authenticate the user). all these can be solved, but I'm not sure it's worth the trouble...
