On Mon, Mar 9, 2009 at 4:02 PM, Charles Marcus <cmar...@media-brokers.com> wrote: > 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... > > 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. > > I only said it was an interesting idea, and wondered if it could be > automated... I'm still not sure it *should* be done... :) >
yes that looks interesting; however at the moment the recall request rate is really low for my particular case so sould be enough to manually release mails from the hold queue with 'postsuper'; however i'm wondering if my proposed implementation would *really* catch not only all relayed mail but also internal clients sending mail to internal clients ?
