🚀 go-pugleaf

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
>user enters an MX "To:" address, but then QUITs out of the editor or
>types ^C to cancel the message, the 0-byte entry is left in the MX
>queue.  The entries were made as soon as the "To:" address was
>processed.  MX is not called again after the user cancels the message,
>hence the left-over queue entry.  They go away when the expiration
>date is reached or when you issue an MCP QUEUE CANCEL command.

Under normal circumstances, cancelling a message in VMS Mail should result
in a zero-length queue entry with status = CANCELLED.  A zero-length entry
with status = IN-PROGRESS probably means that message entry was interrupted
in a somewhat more violent nature (like the process was deleted or the
system crashed).

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