Problem: The MTA has been running smoothly, but stops unexpectedly.
Action: If the MTA agent console is still displayed, exit it. If the normal exit procedure does not work, use the system procedure for terminating a program.
Action: After the MTA agent console is no longer displayed, restart the MTA as you normally would. See "Installing and Starting the MTA" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.
Action: If the MTA shuts down again, exit it again, reboot the server, then start the MTA again.
Action: Set the MTA log level to Verbose for troubleshooting. See "Using MTA Log Files" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: Occasionally, a badly damaged message file can cause the MTA to shut down.
Action: Check the contents of the MTA input queues in the domain and post offices. For the locations of the MTA input queues, see "Message Transfer/Storage Directories" in GroupWise 6.5 Troubleshooting 3: Message Flow and Directory Structure.
Move the message files out of the priority subdirectories of each input queue, start the MTA, then copy the message files back in groups, watching the MTA carefully to see if it shuts down on a particular message file. If it does, delete the problem message file so normal processing can resume.
Possible Cause: Occasionally, a damaged domain database (wpdomain.db) can cause the MTA to shut down.
Action: In ConsoleOne, perform maintenance to correct any problems with the domain database. See "Maintaining Domain and Post Office Databases" in "Databases" in the GroupWise 6.5 Administration Guide.
Possible Cause: Network connections are unstable.
Action: Make sure the connections between the server where the MTA is running and the servers where the domain database (wpdomain.db) and post office database (wphost.db) are located are stable. Repeatedly losing connections to servers can cause damage to databases.
Possible Cause: The MTA is encountering a problem with one specific aspect of its functioning.
Action: MTA startup switches are available to disable specific MTA functions while allowing other functions to continue normally. For example, the /noada switch disables the MTA admin thread. If a specific MTA function is causing the MTA to shut down, you might be able to disable that particular function with a startup switch. See "Using MTA Startup Switches" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: Another program on the server is interfering with the operation of the MTA.
Action: If the MTA continues to be unstable, eliminate other programs running on the server. If the MTA is stable when another specific program is not running on the same server with it, a conflict might exist between the two programs.