The MTA console enables you to monitor the MTA from any location where you have access to a web browser and the Internet. This provides substantially more flexible access than the MTA server console, which can only be accessed from the server where the MTA is running.
The MTA console provides several pages of information to help you monitor the performance of the MTA. The title bar at the top of the MTA console displays the name of the MTA and its domain. Below the title bar appears the MTA console menu that lists the pages of information available in the MTA console. Online help throughout the MTA console helps you interpret the information being displayed and use the links provided.
When you first access the MTA console, the Status page is displayed. Online help throughout the MTA console helps you interpret the information being displayed and use the links provided.
Click the Router link to display details about the MTA routing queue (gwinprog). You can quickly determine how many messages are awaiting processing, how large they are, and how long they have been waiting in the routing queue.
Click a closed location to display its holding queue to see how many messages are waiting for transfer.
On the MTA console menu, click Status, and then click Router to display the contents of the routing queue. Typically, no message files are waiting unless the MTA is down or backlogged.
You can click any queue to view the message files it contains.
On the MTA console menu, click Links to monitor the direct links between the MTA and other locations.
Click a location to view its holding queue. Click View Link Configuration to determine the address of each location and access the agent consoles of other domains and of post offices that belong to the local domain. Click View TCP/IP Connections to view incoming and outgoing TCP/IP links. Click View Gateways to restrict the list to just gateways.
Before you can track messages at the MTA console, you must enable message logging for MTAs throughout your system. See Enabling MTA Message Logging. When you enable MTA message logging, the MTA stores data about GroupWise message traffic as it processes messages. The stored data is then available for use from the MTA console.
To track a specific message, have the sender check the Sent Item Properties for the message in the GroupWise client. The Mail Envelope Properties field displays the message ID of the message; for example, 3AD5EDEB.31D : 3 : 12763. To track all messages sent by a particular user, make a note of the user’s GroupWise user ID.
On the MTA console menu, click Message Tracking.
Fill in one of the fields, depending on what you want to track, and then click Submit. The results of the search are displayed on a separate page which can be printed.