The following directories and files are found under the \domain\wpgate\ structure for the GWIA after the software has been installed and the GWIA has processed messages.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The domain\wpgate\gwia directory is the GWIA home directory where GWIA configuration files and queue directories are located. The name is established when you install the GWIA. The default is wpgate\gwia in the domain directory. You can change the location using the --home switch in the GWIA configuration file (gwia.cfg).
The GWIA uses the 000.prc directory to process messages.
The gwwork directory stores temporary files created by the GWIA as it converts and builds messages for transfer across the Internet.
The mmddlog.nnn files hold error and status messages about the functioning of the GWIA. The GWIA creates a log file each day with a unique name, where mm is the month, dd is the day, and nnn is a sequential number indicating the sequence of log files in a single day. For more information log files, see Using GWIA Log Files
in Internet Agent
in the GroupWise 2012 Administration Guide.
The acct file contains information about the messages the GWIA sends each day. It is emailed to the accounts each day at midnight. For more information about the accounting files, see Tracking Internet Traffic with Accounting Data
in Internet Agent
in the GroupWise 2012 Administration Guide.
The set file stores GWIA console settings such as color, log settings, and so on. For more information, see Using the GWIA Server Console
.
The stat file stores statistics about the GWIA’s functioning. For information about the statistics provided by the GWIA, see Statistics
in Internet Agent
in the GroupWise 2012 Administration Guide.
The proc file is the lock file for the GWIA process. The proc file is opened and locked when the GWIA starts. This prevents multiple GWIAs from being started for the same domain.
The pulse.tmp file is re-created by the GWIA every time it completes a cycle (after an idle loop). If you are not at the GWIA console but need to know if the GWIA is running, you can delete the pulse.tmp file. If the GWIA is running, it re-creates the file.
For a mapped/UNC link, the GWIA places inbound messages in one of the wpcsin priority subdirectories (0-7). Most messages go in the 4 directory, although some administrative and status messages might go in other directories. The MTA retrieves the messages and delivers them to the proper destinations.
For a TCP/IP link, the GWIA and the MTA communicate by way of TCP/IP rather than by transferring message files. For a comparison, see Section 4.0, Message Delivery to and from the Internet.
For a mapped/UNC link, the wpcsout directory is the MTA output queue as well as being the GWIA input queue.
For a TCP/IP link, the GWIA and the MTA communicate by way of TCP/IP rather than by transferring message files. For a comparison, see Section 4.0, Message Delivery to and from the Internet.
The gwixxxx directory is a system-defined directory, where gwi represents the first three letters of the GWIA object name as defined during installation and displayed in ConsoleOne, and xxxx is a randomly-generated string. Here, the MTA places outbound messages in the appropriate 0-7 priority subdirectory for the GWIA to retrieve and process.
The problem directory holds messages that the MTA cannot process.
You should check this directory periodically for problem files, resolve the problem, then place the files back into the appropriate queue for continued processing. For assistance, see Message Is Dropped in the problem Directory in the Domain
in Strategies for Message Delivery Problems
in the GroupWise 2012 Troubleshooting 2: Solutions to Common Problems.
The gwhold directory holds messages that are scheduled for delayed delivery.
The qfiles directory holds messages that cannot be sent during the current Send/Receive cycle. The messages are queued to this directory until the next cycle.
The delayed delivery messages waiting in the qfiles directory remain in encrypted format until the GWIA transfers them to the send directory for processing by the SMTP service.
The GWIA uses the gwprob directory for messages it cannot process. These are usually messages that have been damaged during transmission or that contain incorrectly formed MIME data.
These messages cannot be recovered. You can delete them to conserve disk space.
This directory contains conversion tables that the GWIA uses to convert message attachments between character sets.
If you reinstall or upgrade the GWIA, your old configuration files are copied to the save directory as a backup. If you reinstall or upgrade repeatedly, the files are overwritten each time.
The gwia.cfg file is the GWIA configuration file that contains switches. Some switches are set during installation. You can set others as needed. For more information, see Using GWIA Startup Switches
in Internet Agent
in the GroupWise 2012 Administration Guide.
Linux: |
The Linux GWIA uses the gwia.cfg file created in /opt/novell/groupwise/agents/share during installation. The gwia.cfg file under the domain is just a boilerplate file with no switches set during installation. |
Windows: |
Only the Windows GWIA actually uses the gwia.cfg file under the domain. |
The route.cfg file enables you to customize routing for specific hosts. For more information, see Using a Route Configuration File
in Internet Agent
in the GroupWise 2012 Administration Guide.
The gwauth.cfg file enables the GWIA to log in to SMTP hosts that require authentication. For more information, see SMTP Host Authentication
in Internet Agent
in the GroupWise 2012 Administration Guide.
The mimetype.cfg file enables you to customize MIME content-type mappings for various attachment types. For more information, see Customizing MIME Content-Type Mappings
in Internet Agent
in the GroupWise 2012 Administration Guide
The exepath.cfg file is used by ConsoleOne to locate the gwia.cfg file. This enables ConsoleOne to write any configuration setting changes to the gwia.cfg file or update Novell eDirectory with any changes from the file. The file must contain the path to the gwia.cfg file in the /opt/novell/groupwise/agents/share directory on Linux, or the domain\wpgate\gwia directory on Windows.
The frgnames.cfg file lets you list more Internet domain names than can fit in the field on the Identification page of the GWIA object in ConsoleOne. For more information, see Configuring How the GWIA Handles Email Addresses
in Internet Agent
in the GroupWise 2012 Administration Guide.
The xspam.cfg file lists “X” header fields that your anti-spam service writes to the MIME header, along with the values that flag the message as spam. The GWIA examines the MIME header for any field listed in the xspam.cfg file. When a match occurs, the message is marked for handling by the GroupWise client Junk Mail Handling feature. For more information, see Customized Spam Identification
in Internet Agent
in the GroupWise 2012 Administration Guide.
The gwac.db file is the access control database that stores information about the classes of service you have created. For more information, see Maintaining the Access Control Database
in Internet Agent
in the GroupWise 2012 Administration Guide.
The gwac.dc file is the data dictionary file from which the gwac.db is created.
The preamble.txt file is an ASCII text file that is automatically included with any MIME multipart message and is displayed when the message recipient lacks a MIME-compliant mail reader. For more information, see Customizing MIME Preamble Text
in Internet Agent
in the GroupWise 2012 Administration Guide.
The preamble.all file contains the preamble text in multiple languages. For more information, see Customizing MIME Preamble Text
in Internet Agent
in the GroupWise 2012 Administration Guide.
The blocked.txt file contains a list of Internet sites that you have added to the Prevent Messages From list for your default class of service in ConsoleOne. For more information, see Controlling User Access to the Internet
in Internet Agent
in the GroupWise 2012 Administration Guide.
The statusxx.xml file enables you to customize the messages that users receive regarding message delivery status. For more information, see Customizing Delivery Status Notifications
in Internet Agent
in the GroupWise 2012 Administration Guide.
The gwia directory is the SMTP service (daemon) home directory where messages are converted between GroupWise format and Internet format. On Linux, the default location is wpgate/gwia, the same as the GWIA home directory. On Windows, the default location is the GWIA installation directory. You can change the location using the --dhome switch in the GWIA configuration file (gwia.cfg).
The GWIA SMTP service places outbound messages in the send directory after they have been converted out of GroupWise format into SMTP format. The SMTP service polls the send directory and sends any messages to the destination SMTP host.
The GWIA SMTP service places inbound messages in the receive directory, converts them into GroupWise format, and then passes them to the MTA by placing them in the wpcsin directory.
When the GWIA SMTP service processes the message, it builds a file, r*.*, in the result directory that contains several lines of comments and SMTP reply codes, which might indicate possible errors or confirm correct transmission. After the GWIA SMTP service has completed the transmission with the destination host, it moves another file, s*.* from the send directory to the result directory. The file names for both files are identical, except for the first letter, which is either “s” or “r”. The s*.* file is the converted message file. The SMTP service looks at the “s” and “r” files in the result directory and compares the conversation. If the r*.* file contains the correct (250 OK) SMTP reply codes, the SMTP service deletes the file and sends a transferred status message to the user’s Sent Items folder in the GroupWise client.
The defer directory holds messages that are deferred and re-queued according to the Retry Schedule. If the GWIA SMTP service receives a temporary error, such as Host Down, it places the message in the defer directory for a specified time, then transfers the file to the send directory for another attempt at sending to the Internet. For more information, see Configuring Basic SMTP/MIME Settings
in Internet Agent
in the GroupWise 2012 Administration Guide.
The dsnhold directory stores header information for inbound messages that request delivery status notifications. For more information, see Using Extended SMTP (ESMTP) Options
in Internet Agent
in the GroupWise 2012 Administration Guide.