Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!clyde!cbatt!ihnp4!alberta!ubc-vision!ubc-cs!brachman
From: brachman@ubc-cs.UUCP (Barry Brachman)
Newsgroups: comp.mail.uucp
Subject: Re: cancelling mail messages
Message-ID: <598@ubc-cs.UUCP>
Date: Tue, 2-Dec-86 15:17:10 EST
Article-I.D.: ubc-cs.598
Posted: Tue Dec  2 15:17:10 1986
Date-Received: Fri, 5-Dec-86 04:58:51 EST
References: <2718@bu-cs.BU.EDU> <3700@watmath.UUCP>
Reply-To: brachman@ubc-cs.UUCP (Barry Brachman)
Organization: UBC Department of Computer Science, Vancouver, B.C., Canada
Lines: 32


In article <3700@watmath.UUCP> atbowler@watmath.UUCP (Alan T. Bowler [SDG]) writes:
[...]
>It certainly is useful if a sender can retract an unread message
>whose content is no longer meaningful.  I know I send enough messages
>like "comming for supper?" that have no read meaning if the person
>doesn't see them soon enough.  Being able to retract them avoids
>bothering the person with unneeded mail.

X.400 allows you to specify an expiry date for a message.  The expiry date
indicates the date and time by which you consider the message
to be "no longer valid and useful".  The particular action that takes place
upon expiry is unspecified by X.400, but the message could be deleted.

A second cancellation mechanism involves deferred delivery.  Specifying a
deferred delivery time and date means that you don't want the message to be
delivered before that time and date.  After sending a message having a deferred
delivery, you can issue a deferred delivery cancellation.  The cancellation
request may not succeed.  In any case, you are informed about the results
of the cancellation attempt for each recipient.  In the event of failure
to cancel delivery to a recipient the reason is given.

-----
Barry Brachman
Dept. of Computer Science
Univ. of British Columbia
Vancouver, B.C. V6T 1W5

.. {ihnp4!alberta, uw-beaver}!ubc-vision!ubc-cs!brachman
brachman@cs.ubc.cdn
brachman%ubc.csnet@csnet-relay.arpa
brachman@ubc.csnet