9.0 Message Delivery Is Slow

Select the configuration where message flow is slow:

Message Delivery Is Slow in the Local Post Office

Problem: Message delivery between GroupWise users in the same post office is slower than desired.
Action: Review the stages of message flow within the local post office. See Message Delivery in the Local Post Office in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.
Possible Cause: The POA has been installed on a server with insufficient system resources.
Action: Check the utilization and memory on the server where the POA is running to see if other programs are taking more resources than usual. If the POA has fewer resources than usual, it can take longer to deliver messages. Make sure the server still meets the system requirements for running the POA. See Agent System Requirements in Installing GroupWise Agents in the GroupWise 2012 Installation Guide.
Possible Cause: The POA is not configured optimally.
Action: Go to the server where the POA is running. Check the POA server console or Web console to see how busy the POA is. If the POA is very busy, it can take longer to deliver messages. If the POA needs to handle the current load on a permanent basis, see Optimizing the POA in Post Office Agent in the GroupWise 2012 Administration Guide.
Action: TCP/IP links between the GroupWise client and the post office can be faster than mapped drive connections. If you are currently using mapped drive connections and have TCP/IP available, you could change the configuration of the client and POA to use TCP/IP links instead. See Using Client/Server Access to the Post Officein Post Office Agent in the GroupWise 2012 Administration Guide.

Message Delivery Is Slow between Post Offices

Problem: Message delivery between GroupWise users in different post offices in the same domain is slower than desired.
Action: Review the stages of message flow between post offices. See Message Delivery to a Different Post Office in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.
Action: If message delivery between users in the same post office is also slower than desired, see Message Delivery Is Slow in the Local Post Office. Resolve problems in local post offices first before troubleshooting problems between post offices.
Possible Cause: The MTA has been installed on a server with insufficient system resources.
Action: Check the utilization and memory on the server where the MTA is running to see if other programs are taking more resources than usual. If the MTA has fewer resources than usual, it can take longer to deliver messages between post offices. Make sure the server still meets the system requirements for running the MTA. See Agent System Requirements in Installing GroupWise Agents in the GroupWise 2012 Installation Guide.
Possible Cause: The MTA is not configured optimally.
Action: Go to the server where the MTA is running. Check the MTA server console or Web console to see how busy the MTA is. If the MTA is very busy, it can take longer to deliver messages between post offices. If the MTA needs to handle the current load on a permanent basis, see Optimizing the MTA in Message Transfer Agent in the GroupWise 2012 Administration Guide.
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 post offices.
Possible Cause: If the MTA has received a large number of administrative messages, user messages might be delayed because administrative messages are of higher priority.
Action: Check the MTA log file to see what types of messages the MTA is currently processing. See Using MTA Log Files in Message Transfer Agent in the GroupWise 2012 Administration Guide. After high priority administrative messages are processed, user messages are processed.

Message Delivery Is Slow between Domains

Explanation: Message delivery between GroupWise users in different domains is slower than desired.
Action: Review the stages of message flow between domains. See Message Delivery to a Different Domain in GroupWise 2012 Troubleshooting 3: Message Flow and Directory Structure.
Action: If message delivery between users in the same post office is also slower than desired, see Message Delivery Is Slow in the Local Post Office. Resolve problems in local post offices first before troubleshooting problems between post offices or domains.
Action: If message delivery between users in different post offices in the same domain is also slower than desired, see Message Delivery Is Slow between Post Offices. Resolve problems between post offices before troubleshooting problems between domains.
Possible Cause: The MTA has been installed on a server with insufficient system resources.
Action: Check the utilization and memory on the server where the MTA is running to see if other programs are taking more resources than usual. If the MTA has fewer resources than usual, it can take longer to deliver messages between domains. Make sure the server still meets the system requirements for running the MTA. See Agent System Requirements in Installing GroupWise Agents in the GroupWise 2012 Installation Guide.
Possible Cause: The MTA is not configured optimally.
Action: Go to the server where the MTA is running. Check the MTA server console or Web 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 Optimizing the MTA in Message Transfer Agent in the GroupWise 2012 Administration Guide.
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 to design a more efficient route for messages between domains. See Understanding Link Configuration in Domains in the GroupWise 2012 Administration Guide.