Source: GroupWise Message Transfer Agent.
Explanation: The MTA is not accepting inbound connections on its TCP/IP link.
Possible Cause: The MTA has been manually suspended.
Action: Resume the MTA for the domain. See "Suspending/Resuming MTA Processing for a Location" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.
Possible Cause: If you are running multiple MTAs on the same server, the same TCP port might be in use by more than one MTA.
NetWare Note: On a NetWare server, you would see the message "Waiting for busy listen socket to become available."
Action: Check the setup of the MTAs. Make sure each MTA is using a unique port. See "Configuring the MTA for TCP/IP" in "Message Transfer Agent" in the GroupWise 6.5 Administration Guide.