Optimizing Mapped/Unc Links; Using Tcp/Ip Links Between Locations - Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT Manual

By default, the MTA waits 5 seconds for a response when trying to contact another MTA or a POA
across a TCP/IP link. If no response is received from the other MTA or the POA, the sending MTA
tries again three more times. If all four attempts fail, the MTA reports an error, then waits 10 minutes
before it tries again.
When the MTA attempts to send messages to another MTA or a POA across a TCP/IP link, the
sending MTA tries for 20 seconds before reporting an error.
On some networks, these wait intervals might not be sufficient, and the MTA might report an error
when, by waiting longer, the needed connection or data transfer would be able to take place.
Use the
waits for a response from another MTA or a POA across a TCP/IP link.
Use the
attempts to send messages to another MTA or a POA across a TCP/IP link.
MTA Web Console
You can check the current wait intervals on the
heading.

43.2 Optimizing Mapped/UNC Links

If you must use mapped or UNC links, you can fine-tune how the MTA polls its input queues.
NOTE: The Linux MTA does not use mapped or UNC links.

43.2.1 Using TCP/IP Links between Locations

TCP/IP links between domains or between a domain and its post offices are faster than mapped or
UNC links because the MTA is immediately notified whenever a new message arrives. This
eliminates the latency involved in scanning input directories for messages to process. To change
from mapped or UNC links to TCP/IP links, see
page 618
43.2.2 Adjusting MTA Polling of Input Queues in the Domain,
Post Offices, and Gateways
When using mapped or UNC links between the local domain and its post offices and other domains,
the MTA can create a lot of network traffic just scanning its input queues, especially if the message
load is light. This can be minimized by setting the scan cycle to a higher number. On the other hand,
if the scan cycle is set too high, important messages might have to wait in the input queues to be
picked up by the MTA. The MTA's scan cycle settings also control how often it communicates with
gateways installed in the domain.
676 GroupWise 7 Administration Guide
/tcpwaitconnect switch in the MTA startup file to increase the number of seconds the MTA
/tcpwaitdata switch in the MTA startup file to increase the number of seconds the MTA
Section 43.2.1, "Using TCP/IP Links between Locations," on page 676
Section 43.2.2, "Adjusting MTA Polling of Input Queues in the Domain, Post Offices, and
Gateways," on page 676
Section 43.2.3, "Adjusting the Number of MTA Scanner Threads for the Domain and Post
Offices," on page 678
and "Using TCP/IP Links between a Domain and its Post Offices" on page 623
Configuration page under the TCP/IP Settings
"Using TCP/IP Links between Domains" on