Error messages and other information about MTA functioning are written to log files as well as displaying on the MTA server console. Log files can provide a wealth of information for resolving problems with MTA functioning or message flow. This section covers the following subjects to help you get the most from MTA log files:
The following aspects of logging are configurable:
You can configure the log settings in the following ways:
Using ConsoleOne to establish defaults (see Section 41.1.8, Adjusting the MTA Logging Level and Other Log Settings)
Using startup switches to override ConsoleOne settings (see Section 44.0, Using MTA Startup Switches)
Using the MTA server console to override log MTA settings for the current session (see Adjusting MTA Log Settings
Using the MTA Web console to override other MTA settings for the current MTA session (see Section 42.2.4, Controlling the MTA from the MTA Web Console)
You can view the contents of the MTA log file from the MTA server console and Web console. See the following tasks:
On startup, the MTA records the MTA settings currently in effect. Thereafter, it logs events that take place, including errors. To look up error messages that appear in MTA log files, see GroupWise 7 Troubleshooting 1: Error Messages.
Because the MTA consists of multiple threads, you might find it useful to retrieve the log file into an editor and sort it on the thread ID that follows the date and time information. Sorting will group all messages together for the same MTA thread. At the MTA Web console, you can search through multiple log files. See Viewing and Searching MTA Log Files. You can also use the search capability of the MTA Web console to gather information about a specific MTA thread. See Viewing and Searching MTA Log Files.