Novell Doc: GroupWise 8 Administration Guide - Cross-Platform Issues between Domains and Post Offices

40.7 Cross-Platform Issues between Domains and Post Offices

Domains can be located on the following platforms:

Novell NetWare
Windows Server
Linux

The GroupWise agents can run on the following platforms:

Novell NetWare
Windows Server
Linux

In general, GroupWise is most efficient if you match the agent platform with the network operating system. Ideally, the MTA as well as the domain and post offices should be on the same platform. However, those with mixed networks may wonder what combinations are possible. You have several alternatives.

40.7.1 MTA Platform Dependencies Because of Direct Access Requirements to Post Offices

The MTA must always have direct access to the domain directory. In addition, if using mapped or UNC links to post offices, the MTA must have direct access to each post office directory as well. If the MTA is installed on a remote server, it must be able to log in to servers where the post offices are located.

The table below summarizes the various combinations of MTA and post office platforms, and indicates which combinations work for direct access and which ones do not:

Table 40-1 MTA Platforms and Post Office Platforms

	NetWare MTA	Linux MTA	Windows MTA
Post Office on NetWare	Yes	No¹	Yes
Post Office on Linux	No¹	No¹	No¹
Post Office on Windows	No²	No¹	Yes
Post Office on Macintosh	No³	No³	No³

¹ TCP/IP links are required between the MTA and the POA on Linux. Direct access to post offices is not available.
² The NetWare MTA cannot service a domain or post office on a Windows server because Windows does not support the required cross-platform connection.
³ Domains and post offices cannot be created on Macintosh computers.

40.7.2 MTA/Post Office Platform Independence through TCP/IP Links

To overcome platform dependencies for post offices, create a TCP/IP link for any post office located on a platform where the domain MTA cannot gain direct access. See Using TCP/IP Links between a Domain and its Post Offices.

40.7.3 MTA Platform Dependencies Because of Direct Access Requirements to the Domain

If using mapped or UNC links between domains, the source domain MTA must have direct access to its input queues in the destination domain directory. If the MTA is installed on a remote server, it must be able to log in to the server where its domain located.

The table below summarizes the various combinations of the platform of MTA for the source domain and the platform where the destination domain is located, and indicates which combinations work for direct access and which ones do not:

Table 40-2 MTA Platforms and Domain Platforms

	NetWare MTA for Source Domain	Linux MTA for Source Domain	Windows MTA for Source Domain
Destination Domain on NetWare	Yes	No¹	Yes
Destination Domain on Linux	No¹	No¹	No³
Destination Domain on Windows	No²	No¹	Yes
Destination Domain on Macintosh	No³	No³	No³

¹ TCP/IP links are required between MTAs in GroupWise 7 and later. Direct access to other domains is not available.
² The NetWare MTA cannot write message files into its output queue in a destination domain on a Windows server because Windows does not support the required cross-platform connection.
³ Domains cannot be created on Macintosh computers.

40.7.4 MTA/Domain Platform Independence through TCP/IP Links

To overcome platform dependencies between domains, use TCP/IP links between domains. See Using TCP/IP Links between Domains.

40.7.5 MTA/Domain Platform Independence through the Transfer Pull Configuration

If TCP/IP is not available, another alternative for overcoming platform dependencies is a transfer pull configuration.

By default the MTA “pushes” message files out to destination domains by writing them into its output queue in each destination domain. One situation where this method does not work is for the NetWare MTA on a NetWare server to write message files to its input queue in a destination domain located on a Windows server.

As an alternative, you can have the Windows MTA for the destination domain “pull” the message files from the source domain on the NetWare server. This is called a transfer pull configuration. See Section 41.3.3, Using a Transfer Pull Configuration for setup instructions.