GWMTA: Cannot attach to server or volume

Source:  GroupWise Message Transfer Agent; last closure reason.

Explanation:  A domain or post office is closed because the NetWare® MTA cannot access the server or volume where the domain or post office is located.

Possible Cause:  The domain or post office is located on a different server from where the MTA is running and the MTA has not been configured with user information to enable it to log in.

Action:  Make sure the MTA startup file includes the /user and /password, or /dn switches, so the MTA can log into the remote server. Make sure the user and password information is correct and current. Make sure the information is formatted correctly. In some configurations, you might need to specify a distinguished name (for example, user.org_unit.org) for the /user switch, rather than just a simply user ID. In some configurations, you might need to include the type (for example, .CN=user.org_unit.org).

Action:  If the MTA still cannot log in to the remote server after appropriate user information has been supplied, start the MTA with /tracelogin-2 to display NetWare® error codes. Look up the error codes at Novell Error Codes.

Possible Cause:  The NetWare MTA cannot log into the server where a domain or post office is located because all available NetWare licenses are already in use.

Action:  Increase the number of licenses on the server.