Source: GroupWise Message Transfer Agent; last closure reason.
Explanation: A domain or post office is closed because the MTA cannot write files into its output queue in the closed domain or post office.
Possible Cause: The user specified with the /user switch in the MTA startup file does not have sufficient rights to create files in the domain or post office directory.
Action: Make sure the user the MTA is logging in as has sufficient rights in the domain or post office directory. See "Creating a NetWare Account for Agent Access (Optional)" in "Installing GroupWise Agents" in the GroupWise 6.5 Installation Guide.
Possible Cause: The MTA cannot write message files across a mapped or UNC link into the MTA input queue in a closed domain (domain\wpcsin directory) or a closed post office (post_office\wpcsout directory) because the directory is inaccessible or damaged.
Action: Make sure the input queue directory exists and that the MTA has sufficient rights to create files there. If necessary, and if the input queue subdirectories are empty, you can rename the original input queue directory and then manually recreate it, along with its required subdirectories.
Possible Cause: The server where the closed domain or post office is located does not have sufficient disk space for the MTA to create message files.
Action: Free up disk space.
NetWare Note: On a NetWare server, you might need to purge deleted files to free up disk space.
Possible Cause: The name of the domain directory contains more than 8 characters.
Action: Rename the domain directory. The MTA currently does not support long names. Also update the domain directory path in ConsoleOne®.
Possible Cause: The network type specified for the domain is incorrect.
Action: Check the network type selected for the domain. In ConsoleOne, right-click the Domain object, then click Properties. Make sure the Network Type field is correct for the MTA running for the domain.