128
GroupWise 8 Administration Guide
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
Figure 8-9
MTA Access Using TCP/IP Links
When using TCP/IP links, the MTA does not write message files into message queues in the post
office directory structure. Instead, the MTA communicates the information to the POA by way of
TCP/IP and then the POA uses its direct network access to write the information.
Cross-Platform Access Issues
In most cases, it is most efficient if you match the MTA platform with the network operating system
where the domain resides. For example, if you create a new domain on a NetWare server, use the
NetWare MTA.
If you decide not to run the MTA on the same platform as the domain, the MTA must still have
direct network access to the domain directory so that it can write to the domain database
(
wpdomain.db
). For example, you could set up the new domain on a NetWare server and run the
Windows MTA on a Windows server to service it.
Figure 8-10
A Domain on a NetWare Server and the MTA on a Windows Server
However, the NetWare MTA could not service a domain located on a Windows server because
Windows does not support the required cross-platform connection.
If you are using mapped or UNC links to post offices, the MTA must also have direct network access
to the post office directories so that it can write messages files into the post office message queues.
You could, for example, run the agents on an Windows server while domains and post offices were
located on NetWare servers.
Figure 8-11
Agents on a Windows Server and Domains and Post Offices on a NetWare Server
Again, the opposite combination of NetWare agents servicing domains and post offices on Windows
servers is not an option because Windows does not support the required cross-platform connection.
To avoid these cross-platform access issues, use TCP/IP links between a domain and its post offices.
POA
Dev-Dom
Dev-PO1
POA
MTA
MTA
Acct-Dom
Acct-PO1
Dev-Dom
Dev-PO1
POA
MTA
Windows
NetWare
POA
Dev-Dom
Dev-PO1
POA
MTA
MTA
Acct-Dom
Acct-PO1
