🚀 go-pugleaf

I recently managed to get my MX components hung up while attempting to update
the MX logicals to match my new registered domain name. I noticed there was a
problem when I discovered that my messages to  test the new address were not
being delivered. A STATUS command to MCP resulted in the error  'no such agent
processes are running',  while a show system did show that the MX processes
existed. Attempting to restart the MX components resulted in errors such as

	%MX-F-AGENTALRDY, agent MX_UUCP is already running
	-SYSTEM-F-IVBUFLEN, invalid buffer length

Restoring MX_logicals.dat to its original state solved the above
problem. However, messages posted during the time that MX was not
running correctly now appear in my queue in a READY state and have
for several days. Other messages posted after I got MX running again
are delivered correctly and promptly.

What steps should I perform to cause these pending entries to be 
delivered. I can find nothing in the trace logs that indicates any
MX component is attempting to process these entries.

I have attempted a QUEUE READY command to no affect.
 
Thanks for any helpful hints.


MCP>show version
MX version is is: MX V3.1C
MCP>que show /all/full

Entry: 577, Origin: [VMSmail] CAMPBELLL    "Laura @Forty Two Ten"
  Status: READY, size: 1498 bytes
  Created: 11-DEC-1992 16:05:45.16, expires 10-JAN-1993 16:05:45.16
  Last modified 15-DEC-1992 16:21:29.57
    Recipient #1: <joeys@esipdx>

Entry: 578, Origin: [VMSmail] RONNINGK    
  Status: READY, size: 254 bytes
  Created: 14-DEC-1992 09:02:15.11, expires 13-JAN-1993 09:02:15.11
  Last modified 15-DEC-1992 16:32:18.49
    Recipient #1: <dougk@esipdx>


Chuck Lewis                         |  UUCP        esimis!lewisc
Electro Scientific Ind.             |              lewisc@elcsci.com
13900 NW Science Park, Portland Or  |  Compuserve  71140,2271