At the MTA server console or Web console, check to see if all links between the new Linux MTA and other domains and post offices are open.
If you have closed links, see GroupWise 7 Troubleshooting 2: Solutions to Common Problems.
If the domain has gateways, start each gateway.
If the domain has an Internet Agent that is running on the same NetWare or Windows server where the domain directory was previously located, migrate the Internet Agent to the Linux server where the domain directory is now located, as described in Section 22.0, Manually Migrating the Internet Agent to Linux.
After the domain has been migrated to Linux, the NetWare or Windows Internet Agent can continue receiving and queuing Internet messages, but it cannot pass them into the GroupWise system until the Internet Agent has been migrated to Linux along with its domain and MTA.
If the domain has a WebAccess Agent that is running on the same NetWare or Windows server where the domain directory was previously located, consider migrating the WebAccess Agent to the Linux server where the domain directory is now located, as described in Section 23.0, Manually Migrating WebAccess to Linux.
Because it is common for the WebAccess Agent to run on a different server from where its domain is located, there is no urgency about migrating it to Linux.
When the Linux MTA is running smoothly for the new domain location, and other GroupWise agents belonging to the domain have been migrated to Linux as needed, delete the old domain directory structure (and if applicable, the mslocal directory structure) from the NetWare or Windows server.