🚀 go-pugleaf

In a previous article, madison@tgv.com wrote:
>Date: Tue, 6 Oct 1992 17:34:06 GMT
>From: madison@tgv.com
>Subject: RE: Entries with size 0 in MX queue
>Reply-To: MX-List@WKUVX1.BITNET
>
>In article <00961A80.2DCDDA80.21303@WKUVX1.BITNET>, Hunter Goatley
> <goathunter@WKUVX1.BITNET> writes:
>>>Does anybody know why we keep getting entries like the following in our MX
>>>message queue? They seem to go away eventually, but I would like to know what
>>>they are.
>>>
>>>Entry: 18523, Origin: [code=0]
>>>  Status: IN-PROGRESS, size: 0 bytes
>>>  Created:  1-OCT-1992 22:41:59.85, expires 31-OCT-1992 22:41:59.85
>>>  Last modified  1-OCT-1992 22:41:59.85
>>>    Recipient #1: <RNSPANE@ceride.bitnet>
>>>
>>[...]
>>These are left whenever a user aborts a message.  For example, if a
>
>Under normal circumstances, cancelling a message in VMS Mail should result
>
Would they not also be there whilst the process is actually preparing a mail
message.. Ie: Don't go killing them as soon as you see them...

>-Matt
>--
>Matthew Madison | madison@tgv.com    | +1 408 427 4366
>TGV, Inc.       | 603 Mission Street | Santa Cruz, CA 95060 USA
>

                                                  Chris.

+ J.C. Higgins, Sys Admin  +  If you love something, set it free. If it doesn't
+ CHRIS@csvax1.ucc.ie      +  come back to you, hunt it down and KILL it. If
+ SCCS6002@iruccvax.ucc.ie +  that doesn't work, then GIVE UP peacefully.