Novell GROUPWISE 7 - MESSAGE TRANSFERT AGENT Manual page 60

Event Logging (LOG): The event logging thread writes information into the event log files that
you can search on this page. See Section 42.3, "Using MTA Log Files," on page 665.
Dispatcher (DIS): The dispatcher thread starts other MTA threads as needed to meet the demands
being put on the MTA at any given time.
Message Transfer (MTP): The message transfer threads communicate with other MTAs and with
POAs in the local domain to transfer messages to domains and post offices to which the local MTA
is linked by way of TCP/IP. See Section , "Using TCP/IP Links between Domains," on page 618 and
Section , "Using TCP/IP Links between a Domain and its Post Offices," on page 623.
Router (RTR): The router threads process messages in the routing queue and prepare them for
transfer to the next hop in the link path to their destinations. See Section 43.3, "Optimizing the
Routing Queue," on page 680.
Admin (ADM): The admin thread updates the domain database (wpdomain.db) whenever
administrative information changes. See Section , "MTA Admin Thread Status Box," on page 648.
Scanner (SCA): The scanner threads check for incoming messages when UNC or mapped links are
in use. See Section 43.2.3, "Adjusting the Number of MTA Scanner Threads for the Domain and
Post Offices," on page 678.
The results of the search are displayed on a separate page which can be printed.
Monitoring the Routing Queue
On the MTA Web console menu, click Status, then click Router to display the contents of the routing
queue. Typically, no message files are waiting unless the MTA is down or backlogged.
MTA Web Console with the Router Queue Page Displayed
Figure 42-9
You can click any queue to view the message files it contains.
Monitoring Links
On the MTA Web console menu, click Links to monitor the direct links between the MTA and other
locations.
662 GroupWise 7 Administration Guide