6.3 MTA Local Queue Directory
|
|
|
|
|
|
|
|
|
|
|
MTA local working directory
6.3.1 mslocal directory
The mslocal directory is the MTA local working directory. The --work switch of the MTA specifies the location of the mslocal directory. It must be located on the hard disk of the server where the MTA runs so it is always accessible. Adequate disk space must be available to hold messages going to destinations that are temporarily closed.
Initially, the mslocal directory is created as a subdirectory of the domain directory.
If the Windows MTA runs on a different server from where the domain directory structure is located, you can move the mslocal directory. To move the mslocal directory to the server where the Window MTA is running, stop the MTA, the copy the mslocal directory, along with all of its subdirectories, to the new location. Then restart the MTA and specify the new location using the --work switch.
Historical Note: In earlier versions of GroupWise, the Message Transfer Agent (MTA) was called the Message Server (MS). Hence, the ms in mslocal. Some naming conventions were originally preserved for backward compatibility.
mmddxxx.nnn files
The mmddxxx.nnn file are MTA log files. The MTA creates log files to inform you of its processing and any problems it encounters. By default, these log files are created in the mslocal directory. You can change the location if needed. See Using MTA Log Files
in Message Transfer Agent
in the GroupWise 2012 Administration Guide.
The first two digits of the file name represent the month; the next two digits represent the day of the month; the next three characters indicate what program created the log. The three-digit extension is a sequence number for multiple log files created on the same day. For example, 0518mta.002 is the second MTA log file created on May 18.
On Linux, the MTA log files are stored in the /var/log/novell/groupwise/domain.mta directory
Historical Note: In earlier versions of GroupWise, the Message Transfer Agent (MTA) was called the Message Server (MS). Hence, the ms indicator representing the MTA. Some naming conventions were originally preserved for backward compatibility.
6.3.2 msglog directory
The msglog subdirectory contains message logging files. It is created when you turn on message logging. The MTA receiver threads log messages as they arrive so the MTA worker threads can process messages without having to scan the MTA input queues to look for work.
The resources used for message logging are configurable. See Optimizing the Routing Queue
in Optimizing the MTA
in the GroupWise 2012 Administration Guide.
More detailed message logging by the MTA is also available, but is turned off by default. See Enabling MTA Message Logging
in Configuring the MTA
in the GroupWise 2012 Administration Guide.
mmddmsg.nnn files
The mmddmsg.nnn files in the message logging subdirectory (msglog) in the MTA local directory are used by the MTA to track messages in its “in progress” queue.
The first two digits of the file name represent the month; the next two digits represent the day of the month. The three-digit extension is a sequence number for multiple files created on the same day. For example, 0518msg.002 is the second message logging file created on May 18.
6.3.3 gwinprog directory
The gwinprog subdirectory is the MTA “in progress” queue. It contains eight priority subdirectories parallel to those found in wpcsin. All messages for recipients in the domain pass through gwinprog, no matter whether they arrived by way of TCP/IP or by way of message files deposited into the MTA input queue by a POA or another MTA.
The resources used to process the “in progress” queue are configurable. See Optimizing the Routing Queue
in Optimizing the MTA
in the GroupWise 2012 Administration Guide.
6.3.4 mshold directory
The mshold subdirectory is a holding queue for messages addressed to domains, post offices, or gateways that are currently closed.
A location might be closed because its server is down or because the MTA is unable to communicate with it for any other reason. When a closed location is again open, the MTA moves messages from the holding queue back into the normal message flow.
Historical Note: In earlier versions of GroupWise, the Message Transfer Agent (MTA) was called the Message Server (MS). Hence, the ms in mshold. Some naming conventions were originally preserved for backward compatibility.
6.3.5 domainms directory
The domainms subdirectory in the holding directory (mshold) is used for internal processing by the MTA. It does not contain any files a GroupWise administrator needs to access.
Historical Note: In earlier versions of GroupWise, the Message Transfer Agent (MTA) was called the Message Server (MS). Hence, the ms in domainms. Some naming conventions were originally preserved for backward compatibility.
6.3.6 postx directories
The postx subdirectories in the holding directory (mshold) represent post offices in the domain. If a post office is closed, the MTA routes messages for that post office into its holding queue in mshold. When the post office is open, the MTA moves the messages from the holding queue back into the regular message flow. For more information, see Message Delivery to a Different Post Office.
The name of the holding queue for each post office consists of the first three characters of the post office name, followed by four hashed characters to ensure uniqueness.
6.3.7 gatewayx directories
The gatewayx subdirectories in the holding directory (mshold) represent gateways in the domain. If a gateway is closed, the MTA routes messages for that gateway into its holding queue in mshold. When the gateway is open, the MTA moves the messages from the holding queue back into the regular message flow through the gateway.
The name of the holding queue for each gateway consists of the first three characters of the gateway name, followed by four hashed characters to ensure uniqueness.
6.3.8 domainx directories
The domainx subdirectories in the holding directory (mshold) represent domains to which the current domain has a direct link. If a domain is closed, the MTA routes messages for that domain into its holding queue in mshold. When the domain is open, the MTA moves the messages from the holding queue back into the regular message flow. For more information, see Message Delivery to a Different Domain.
The name of the holding queue for each domain consists of the first three characters of the domain name, followed by four hashed characters to ensure uniqueness.
6.3.9 0-7 directories
The priority 0-7 subdirectories in each holding queue in the mshold subdirectory correspond to the priority 0-7 subdirectories located in each domain, post office, or gateway. See the following directory structures for more information about its priority 0-7 subdirectories:
6.3.10 mtaname files
The mtaname files in the closed location holding queues provide the name associated with the domain, post office, or gateway holding queue. They can help you check links between MTAs in ConsoleOne without going to the MTA agent console to determine the location name. To associate a location name with its holding queue directory from the MTA agent console, click select the location > click .
6.3.11 gwvsscan directory
The gwvsscan subdirectory is the working directory where third-party virus scanning programs that snap in to the MTA can perform their processing.
6.3.12 mtaconv directory
The mtaconv subdirectory is the working directory where the MTA converts GroupWise 2012, 8, 7, 6.x, and 5.x messages to 4.x format for transfer to a GroupWise 4.x system. After the conversion is finished, this directory should be empty.