[Ashok Subramanian <ashok@Sushi.Stanford.EDU>: MM bug]

[Mark Crispin <MRC@SIMTEL20.ARPA>]

This is an EMACS bug.  It doesn't check why the fork terminated.  MM
does not handle quota exceeded interrupts for damn good reasons.
                ---------------

   1) 10-Nov Ashok Subramanian    MM bug
   2) 10-Nov Ashok Subramanian    TOPS-20/MM bug

Message 1 -- ************************
Return-Path: <@Score.Stanford.EDU:ASHOK@Sushi.Stanford.EDU>
Received: from Score.Stanford.EDU by SIMTEL20.ARPA with TCP; Mon 10 Nov 86 11:47:20-MST
Received: from Sushi.Stanford.EDU by SU-SCORE.ARPA with TCP; Mon 10 Nov 86 10:45:54-PST
Date: Mon 10 Nov 86 10:45:23-PST
From: Ashok Subramanian <ashok@Sushi.Stanford.EDU>
Subject: MM bug
To: bug-mm@Sushi.Stanford.EDU
Message-ID: <12253864005.14.ASHOK@Sushi.Stanford.EDU>


Assume you're in EMACS, and type a ctrl-X R to invoke the mailer. Then 
you type 

R 121, 123, 126

to read three messages. After you read the first message, you type

MOV file.foo

to move the first message to a file.

One would expect that MM would return with an R> prompt. What it does, however,
is to return to EMACS, just as if an extra Q had been typed to it.

--ashok
-------

Message 2 -- ************************
Return-Path: <@Score.Stanford.EDU:ASHOK@Sushi.Stanford.EDU>
Received: from Score.Stanford.EDU by SIMTEL20.ARPA with TCP; Mon 10 Nov 86 12:14:45-MST
Received: from Sushi.Stanford.EDU by SU-SCORE.ARPA with TCP; Mon 10 Nov 86 11:13:05-PST
Date: Mon 10 Nov 86 11:12:33-PST
From: Ashok Subramanian <ashok@Sushi.Stanford.EDU>
Subject: TOPS-20/MM bug
To: bug-mm@Sushi.Stanford.EDU
Message-ID: <12253868950.14.ASHOK@Sushi.Stanford.EDU>


IF you attempt to move a message to a file, and there is no space
available in your directory, well, what happens is that a new file is 
created, with 0 pages, and everything looks like the move was completed
successfully. No complaint from MM, none from TOPS-20.  And then you do
an EXPunge on the mail file, and the message is gone forever.

ashok
-------
-------