| One possible implementation of this is the X400
'OBSOLETE' msgid - say for instance you send a message saying 'you are
all fired', and then change your mind, you could send out a mesage
saying 'You are all getting a raise !' - which would obsolete the
previous one - and the UA could then delete the original one (possibly
unread).
In physically removing them, then trying to stop it in message router is
virtually impossbile.
Secondly, if it was a local addressee, then it is delivered as soon as
it is sent in many cases. The only way you could stop it (currently)
is to delete the sender record by hand if it was sent by 2nd class mail
or by deleting it from the Pending File (again currently by hand).
Both of these are paticularly sensitive security areas..
o If the Customers need is to countermand a mail message, then I sugegst
hitting ALL-IN-1 product management to ensure that X400 functionality
is developed....
o If the customers need is to mop up a mistake, then
they haven't much of a chance ... I can only suggest that
they customize their system so they can't "Send" without
(a) Reviewing and confirming their mail
(b) Confirming the addressee list....
Winton
|
| The problems with canceling something already sent have been discussed
in detail in the past. Rather than look at the technical "difficulties", though,
I'd just like to remind those who ask for something such as this of the confusion
that such an option could provide.
When mail is sent in ALL-IN-1, much of it is *immediately* available to
the addresee -- that is, all first-class local mail, any VAXmail, etc. So
before ALL-IN-1 even returns to the sender after doing the 'S' option, the
addressees already have access to that mail. Which means that they can read it
at any time.
Canceling would have to implement some scheme, therefore, to determine
who *hadn't* yet ready their mail, and "remove" the pending message. Yet a
message sent to a list of users could be read by some, and not noticed by others,
causing great confusion.
Furthermore, mail that is *not* local ALL-IN-1 mail (e.g., network mail,
VAXmail, X.400 mail) may have already left the system (i.e., the sending node).
What does a "cancel" mean in that context?
I tend to agree with those who liken the situation to the U.S. Mail:
you can seal and stamp the envelope and leave it on your desk, and still have
total control over it (i.e., deferred send); but once you drop it in the box,
it's gone. In that situation, I'd have to follow-up (either by phone, or another
mail message) to the individual, letting them know that my first message was no
longer valid. This is probably the best approach in ALL-IN-1 as well. (In fact,
using the ALL-IN-1 Personal Assistant, the follow-up message could even be sent
with some keyword to indicate to the recipient that they ought to read this
message *first* -- just to get a plug in for APA 8^) ).
F
|