Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 79

domains. Make sure the server still meets the system requirements for running
the MTA. See
Agents" in the
Possible Cause: The MTA is not configured optimally.
Action: Go to the server where the MTA is running. Check the MTA agent console to
see how busy the MTA is. If the MTA is very busy, it can take longer to deliver
messages between domains. If the MTA needs to handle the current load on a
permanent basis, see
the GroupWise 7 Administration
Possible Cause: The network itself is busy.
Action: Check network traffic between the servers where the POA and MTA are
running. Heavy network traffic can slow down the transfer of GroupWise
messages between domains. Also check general network configuration,
looking for slow links, congested hubs, and busy subnets that lie along the
route GroupWise messages must take between domains.
Possible Cause: Links between domains are not configured optimally.
Action: Check the number of hops the message must travel between domains. You can
view this information for a message in the mailbox of a user who has problems
with slow message delivery. If messages are being routed through a large
number of domains, use the Link Configuration Tool in ConsoleOne
design a more efficient route for messages between domains. See
"Understanding Link
Administration
"Agent System Requirements" in
"GroupWise 7 Installation
"Optimizing the MTA" in
Guide.
Configuration" in "Domains" in the
Guide.
"Installing GroupWise
Guide".
"Message Transfer
GroupWise 7
Message Delivery Is Slow
Agent" in
®
to
79