5.0 Internet Agent Problems

This section suggests ways to fix the following problems:

No Relay Host Connectivity from the Target Server

Problem: During installation, the Internet Agent Installation program was not able to contact a mail process on the specified relay host. You can fix the problem after the Internet Agent has been installed.
Possible Cause: The server where you installed the Internet Agent is not yet configured for TCP/IP.
Action: On a NetWare server:

  1. Load INETCFG.

  2. In the Internetworking Configuration box, select Protocols > TCP/IP.

  3. Select Enabled.

  4. Exit INETCFG.

  5. Restart the server.

Refer to the NetWare documentation at the Novell Documentation Web site for more information about configuring TCP/IP on NetWare.

Action: On a Windows server:

NOTE:Steps may vary, depending on your version of Windows.

  1. Right-click My Network Places, click Properties, then double-click Local Area Connection.

  2. Check the list for Internet Protocol (TCP/IP).

  3. If TCP/IP is not in the list, click Add, then follow the instructions for installing TCP/IP.

    or

    If TCP/IP is listed, select it, then check the existing configuration information for accuracy.

  4. Click OK to save any changes you have made.

  5. Restart the server.

Refer to your Windows documentation for more information about installing TCP/IP on Windows.

Possible Cause: The server where you installed the Internet Agent cannot communicate with the relay host because the default router is not properly configured.
Action: On a NetWare server, if you are configuring TCP/IP in the autoexec.ncf file, add gateway=router_ip_address to the BIND statement.

If you are using INETCFG to configure TCP/IP:

  1. Load INETCFG.

  2. In the Internetworking Configuration box, select Protocols.

  3. In the Protocol Configuration box, select TCP/IP.

  4. In the TCP/IP Protocol Configuration box:

    1. Enable Static Routing.

    2. Select Static Routing Table.

    3. Press Enter.

  5. In the TCP/IP Static Routes box, press Insert to add a new static route.

  6. In the Static Route Configuration box:

    1. Press Enter in the Route Type field to display a list of route types.

    2. Select Default Route.

    3. Select Next Hop Router on Route, then press Enter to edit the field.

    4. Type the IP address of the default router, then press Enter.

    5. Press Esc twice.

  7. Select Yes, then press Enter to update the INETCFG database.

  8. Press Esc until prompted to exit INETCFG.

  9. Select Yes, then press Enter.

  10. Restart the server to put the new default router into effect.

Refer to the NetWare documentation at the Novell Documentation Web site for more information about using INETCFG.

Action: On a Windows server:

NOTE:Steps may vary, depending on your version of Windows.

  1. Click Start > Settings > Control Panel.

  2. Double-click Network and Dial-Up Connections, then click Local Area Connection.

  3. Select TCP/IP Protocol, then click Properties.

  4. In the Default Gateway field, specify the IP address of the default router on your network.

  5. Click OK.

  6. Restart the server to put the new default gateway information into effect.

Refer to your Windows documentation for more information about installing TCP/IP on Windows.

Possible Cause: There is no SMTP mail service listening at the IP address of the relay host.
Action: Start the mail service on the relay host.
Action: Specify a different relay host.

No Internet Connectivity from the Target Server

Problem: During installation, the Internet Agent Installation program was not able to connect to the Internet. You can fix the problem after the Internet Agent has been installed.
Possible Cause: The server where you installed the Internet Agent is not yet configured for TCP/IP.
Action: On a NetWare server:

  1. Load INETCFG.

  2. In the Internetworking Configuration box, select Protocols, then select TCP/IP.

  3. Select Enabled.

  4. Exit INETCFG.

  5. Restart the server.

Refer to the NetWare documentation at the Novell Documentation Web site for more information about configuring TCP/IP on NetWare.

Action: On a Windows server:

NOTE:Steps may vary, depending on your version of Windows.

  1. Right-click My Network Places, click Properties, then double-click Local Area Connection.

  2. Check the list for Internet Protocol (TCP/IP).

  3. If TCP/IP is not in the list, click Add, then follow the instructions for installing TCP/IP.

    or

    If TCP/IP is listed, select it, then check the existing configuration information for accuracy.

  4. Click OK to save any changes you have made.

  5. Restart the server.

Refer to your Windows documentation for more information about installing TCP/IP on Windows.

Possible Cause: The server where you installed the Internet Agent cannot communicate with the Internet because the default router is not properly configured.
Action: On a NetWare server, if you are configuring TCP/IP in the autoexec.ncf file, add gateway=router_ip_address to the BIND statement.

If you are using INETCFG to configure TCP/IP:

  1. Load INETCFG.

  2. In the Internetworking Configuration box, select Protocols.

  3. In the Protocol Configuration box, select TCP/IP.

  4. In the TCP/IP Protocol Configuration box:

    1. Enable Static Routing.

    2. Select Static Routing Table.

    3. Press Enter.

  5. In the TCP/IP Static Routes box, press Insert to add a new static route.

  6. In the Static Route Configuration box:

    1. Press Enter in the Route Type field to display a list of route types.

    2. Select Default Route.

    3. Select Next Hop Router on Route, then press Enter to edit the field.

    4. Type the IP address of the default router, then press Enter.

    5. Press Esc twice.

  7. Select Yes, then press Enter to update the INETCFG database.

  8. Press Esc until prompted to exit INETCFG.

  9. Select Yes, then press Enter.

  10. Restart the server to put the new default router into effect.

Refer to the NetWare documentation at the Novell Documentation Web site for more information about using INETCFG.

Action: On a Windows server:

NOTE:Steps may vary, depending on your version of Windows.

  1. Right-click My Network Places, click Properties, then double-click Local Area Connection.

  2. Select Internet Protocol (TCP/IP), then click Properties.

  3. In the Default Gateway field, specify the IP address of the default router on your network.

  4. Click OK.

  5. Restart the server to put the new default gateway information into effect.

Refer to your Windows documentation for more information about setting up a default router on Windows.

Possible Cause: A firewall is blocking SMTP traffic.
Action: Configure the firewall to allow outbound messages to pass if the source IP address is the IP address of the server where you installed the Internet Agent. Also configure the firewall to allow inbound messages to pass if the destination IP address is the IP address of the server where you installed the Internet Agent. In both cases, the required port number is 25.
Action: As needed, configure the firewall to accept the following additional types of traffic: POP3 (port 110), IMAP4 (port 143), or LDAP (port 389).
Possible Cause: You are using a dial-up connection to the Internet and it is not configured to dial on demand.
Action: Refer to the documentation accompanying the dial-up router or contact the router software vendor.

Target Server Could Not Perform DNS Resolution

Problem: During installation, the Internet Agent Installation program determined that the server where you installed the Internet Agent cannot resolve DNS (Domain Name Service) host names. You can fix the problem after the Internet Agent has been installed.
Possible Cause: The server where you installed the Internet Agent is not yet configured for DNS.
Action: On a NetWare server, make sure that DNS has been set up as described in Internet Connectivity Requirements in Installing the GroupWise Internet Agent in the GroupWise 8 Installation Guide.
Action: On a Windows server:

NOTE:Steps may vary, depending on your version of Windows.

  1. Right-click My Network Places, click Properties, then double-click Local Area Connection.

  2. Select Internet Protocol (TCP/IP), then click Properties > DNS.

  3. Add or correct DNS information as needed.

  4. Click OK to save any changes you have made.

Refer to your Windows documentation for more information about setting up DNS on Windows.

Possible Cause: The DNS server is down or otherwise unavailable.
Action: Contact the administrator of the DNS server to resolve the issue.
Action: Configure the server where you are installing the Internet Agent to use a different DNS server.

Target Server Not Configured for TCP/IP

Problem: During installation, the Internet Agent Installation program determined that the server where you installed the Internet Agent is not configured for TCP/IP. You can fix the problem after the Internet Agent has been installed.
Action: On a NetWare server:

  1. Load INETCFG.

  2. In the Internetworking Configuration box, select Protocols > TCP/IP.

  3. Select Enabled.

  4. Exit INETCFG.

  5. Restart the server.

Refer to the NetWare documentation at the Novell Documentation Web site for more information about configuring TCP/IP on NetWare.

Action: On a Windows server:

NOTE:Steps may vary, depending on your version of Windows.

  1. Right-click My Network Places, click Properties, then double-click Local Area Connection.

  2. Check the list for Internet Protocol (TCP/IP).

  3. If TCP/IP is not in the list, click Add, then follow the instructions for installing TCP/IP.

    or

    If TCP/IP is listed, select it, then check the existing configuration information for accuracy.

  4. Click OK to save any changes you have made.

  5. Restart the server.

Refer to your Windows documentation for more information about installing TCP/IP on Windows.

Invalid or Unspecified Internet Host Name

Problem: During installation, you did not specify a valid Internet host name for the Internet Agent to use when resolving Internet addresses. You can fix the problem after the Internet Agent has been installed.
Possible Cause: The Internet host name is not yet stored in eDirectory.
Action: In ConsoleOne, browse to and right-click the GWIA object, then click Properties. Click GroupWise > Identification. In the Foreign ID field, provide the Internet host name of your company (for example, Novell.com).
Possible Cause: The host name you provided has not been registered and published by your ISP.
Action: Contact your ISP to find out when your hostname will be published. Make sure that your ISP has associated the correct IP address with your host name. Verify the contents of the MX and A records for your host name.
Possible Cause: Your host name as been published for less than 24 hours and your DNS server is still using cached information.
Action: Wait a day and try again.
Possible Cause: Inbound mail is routed through a relay host.
Action: You can ignore this warning if the relay host is configured to forward messages to the server where the Internet Agent is installed.
Action: If the relay host uses aliasing to forward messages to the server where the Internet Agent is installed, you must configure the Internet Agent to handle the alias. In ConsoleOne, browse to and right-click the GWIA object, then click Properties. Click GroupWise > Identification. In the Foreign ID field, provide the alias along with the Internet host name of your company. Separate the hostnames with a space.

Unverified Host Name for Target Server

Problem: During installation, the Internet Agent Installation program determined that the server where you installed the Internet Agent does not have a host name. You can fix the problem after the Internet Agent has been installed.
Action: On a NetWare server, make sure that the server where you installed the Internet Agent is listed in the sys:\etc\hosts file, including its host name and IP address.
Action: On a Windows server:

NOTE:Steps may vary, depending on your version of Windows.

  1. Right-click My Network Places, click Properties, then double-click Local Area Connection.

  2. Select Internet Protocol (TCP/IP), then click Properties > DNS.

  3. Fill in the Host Name and Domain fields.

  4. Click OK to save any changes you have made.

Refer to your Windows documentation for more information about setting up DNS on Windows.

RFC Compliance: Specify a Postmaster

Problem: During installation, you did not specify a postmaster for the Internet Agent to send error notifications to. You can fix the problem after you have finished installing the Internet Agent.
Action: Follow the instructions in Assigning a Postmaster in Installing the GroupWise Internet Agent in the GroupWise 8 Installation Guide.

Log Files

Explanation: The log file is a useful tool for diagnosing problems. It is an ASCII file that records Internet Access activity and provides a variety of configuration, message flow, and productivity information. The log file contains the same information that scrolls in the message log portion of the of the Internet Agent console.
Action: You can adjust the amount of information a log file records using the Log Settings page in ConsoleOne, the log startup switches, or the keystroke menu in the Internet Agent console. For more information, see Using Internet Agent Log Files in Internet Agent in the GroupWise 8 Administration Guide.

SMTP Statistics

Explanation: The Statistics screen, which is accessed from the Internet Agent console, lists numbers of error and informational messages. Most of these messages are informational only.
Action: Use the information on the Statistics screen to help you resolve Internet Agent problems.

Messages Sent/Messages Received: These fields display the number of messages the Internet Agent has sent and received.

Send Threads/Receive Threads: These fields display the number of currently active send and receive threads the Internet Agent is using to process outgoing and incoming messages. If the number of send or receive threads currently in use is consistently close to the total number allocated, you might want to increase the total number of send or receive threads.

Send Thr Avail/Receive Thr Avail: These fields display the number of available send and receive threads of the total number allocated.

MX Lookup Errs: This field displays the number of times the Internet Agent queries the Domain Name Server (DNS) for the address of the destination host and receives a SERVER FAIL code message back from the DNS. These messages are deferred and automatically re-queued according to the retry schedule.

Unless the number of MX Lookup Errors is very significant, do not be concerned by these messages. If the number of messages is very significant, you might want to check the DNS to make sure the tables are not corrupted. If you’re using a remote DNS, you might consider setting up a local DNS server. It could also mean that your file server TCP/IP is not correctly configured.

Unknown Hosts: This field displays the number of times the Internet Agent attempted to do a lookup on a destination host and the host name did not exist in either the DNS records or in the host table. The Internet Agent sends back a non-deliverable message to the sender for each Unknown Host message.

TCP/IP Read Errs/ TCP/IP Write Errs: These fields display the number of TCP/IP read or write errors indicating some communication problem occurred. This is a temporary error. These messages are deferred and automatically re-queued according to the retry schedule. Unless the number of TCP/IP read or write errors is very significant, do not be concerned by these messages. If the number of messages is very significant, you might want to contact your Internet service provider to check for anything that could hinder communication, such as network problems or line noise. You might also want to adjust the timeout switches, particularly the /te and /tr switches.

Hosts Down: This field displays the number of times the Internet Agent tried to open a connection with the destination host and received a connection refused status. This is a temporary error. These messages are deferred and automatically re-queued according to the Retry Schedule.

The statistics count the number of times a code or SMTP reply, such as Host Down, comes back to the Internet Agent. It does not keep track of the mail messages causing these replies. If, for example, a message is deferred and re-queued for four days during the Retry Schedule, each attempt the program makes to send the message results in another SMTP reply or error code.

Retry Schedule: If an Internet host is down or the connection is not made on the Internet, the Internet Agent defers the message and re-queues it according to the retry schedule. The Internet Agent program places the message in the \wpgate\gwia\defer directory for 20 minutes. Then it transfers the file to the send directory for another attempt at sending to the Internet. The Internet Agent makes this attempt three times in one hour and then every four hours for four days. After the four days, if the Internet host remains down, an undeliverable status is sent back to the sender.

Internet Agent Not Sending Messages

Problem: Messages are not returned to the user’s Sent Items folder as undeliverable, and the recipients are not receiving the messages.
Action: Make sure the Internet Agent is running and is correctly configured in ConsoleOne.
Action: Make sure the Message Transfer Agent is running.
Action: Make sure the Internet Agent can access the GroupWise domain directory.
Action: Make sure the program is properly configured. Check the startup file to verify that the /dhome switch is pointing to the Internet Agent directory.
Action: Check the statistics from the Internet Agent console. If any of the fields, such as TCP/IP Read or Write Errors or MX Lookup Errors, have a very significant number, you might want to contact your Internet service provider. See SMTP Statistics for more information.
Action: Check the log file for error messages. You might want to set the log level to Diag and resend problem messages. See Internet Agent Error Messages in GroupWise 8 Troubleshooting 1: Error Messages for more information.
Action: Make sure the resolv.cfg file is set up correctly. See Internet Connectivity Requirements in Installing the GroupWise Internet Agent in the GroupWise 8 Installation Guide.

Internet Agent Not Receiving Messages

Problem: The Internet Agent is not receiving messages from the Internet.
Action: Make sure the Internet Agent directory has sufficient network rights.
Action: Make sure the Internet Agent can access the GroupWise domain database.
Action: Make sure the Internet Agent has rights to the domain directory and that the Internet Agent can access all its subdirectories.
Action: Make sure the program is properly configured. Check the startup file to verify that the /dhome switch is pointing to the Internet Agent directory.
Action: Check if you can ping the Internet Agent server from another Internet server.
Action: Send a test message from a UNIX Internet computer using the sendmail -v option. The -v option shows all the SMTP reply codes for the message. For example, use the following syntax: 
echo test | /usr/lib/sendmail -v user@host

Internet Agent Locking Up

Problem: The Internet Agent locks up or hangs.
Possible Cause: Bad message file
Possible Cause: Bad configuration file in the 000.prc directory
Possible Cause: Bad domain record
Possible Cause: Bad domain user record
Possible Cause: Software incompatibility
Possible Cause: Hardware failure
Action: Check the dates of the executables and make sure you are using the most current software and patches. Apply the latest versions for the Internet Agent as well as for the TCP/IP kernel. Make sure you meet the minimum version and system requirements for the operating system.
Action: Check for bad message files. Move all files currently in any queues in the send, receive, defer, result, wpcsin, wpcsout, or 000.prc\gwwork directories and let the Internet Agent run idle without processing any messages. If the Internet Agent can run idle without locking, a bad message is probably causing it to lock. Start copying the files back to the appropriate directory queues starting with the newest file to the oldest. This approach assumes the oldest file caused the lock and allows the Internet Agent to process the messages that got backed up before dealing with the bad file. Delete the bad file when you find it. Because the file is encrypted, there is no way to determine who sent the message.
Action: Check for a bad configuration file. One of the setup files in the 000.prcdirectory might be damaged and therefore causing problems. Before removing or changing anything, back up your directories. Be sure to back up any files you want in the 000.prc directory such as the log and accounting files. Remove all the files in the 000.prc and restart the Internet Agent. If you had set a screen color or screen saver, you must reset these settings after removing the SET file.
Action: Remove directories and have the Message Transfer Agent and the Internet Agent re-create new ones. Be sure to back up the whole GWIA directory and all subdirectories before deleting anything. Shut down the Internet Agent and the Message Transfer Agent. Remove the send, receive, defer, result, wpcsin, wpcsout, 000.prcdirectories. Restart the Message Transfer Agent first to re-create the wpcsin and wpcsout directories, then restart the Internet Agent to re-create the other directories (empty). This approach is often effective for solving locking problems, although it is not very effective for isolating and determining what is causing the problem.
Action: If the Internet Agent continues to lock after removing and re-creating the directories, you might want to rebuild the domain database for the domain where the Internet Agent is installed in case there are database structural problems. If it’s a primary domain database, you must rebuild the database from itself. If it’s a secondary domain database, you can rebuild it from the primary domain database or rebuild it from itself. See Rebuilding Domain or Post Office Databases in Databases in the GroupWise 8 Administration Guide.
Action: Run the Internet Agent on a different server that is already set up and running well (without problems with requestors, network interface cards, and so on). If the Internet Agent runs well with the same configuration on a different server, then the hardware is probably causing problems.

Internet Agent Cannot Access the Domain

Problem: The Internet Agent cannot access its input and output queues in the domain.
Explanation: When the domain is located on a remote NetWare server, the Internet Agent must be started with the /user and /password switches so it can log in to the remote server.
Action: Make sure these switches have been specified in the Internet Agent .cfg file.
Action: Make sure the user has sufficient rights to access the \domain\wpgate\gwia directory.
Action: Make sure the password is correct and current.

Internet Agent Doesn’t Send Outgoing Mail

Problem: The Internet Agent seems to receive and process messages, but never sends them.
Action: If you are using an external domain to simplify addressing for your users, make sure the external domain type is set to Non-GroupWise Domain, not External Domain. In ConsoleOne, in the GroupWise View, delete the external domain, then create a non-GroupWise domain.

Internet Agent Fails to Respond to Configuration Changes Made in ConsoleOne

Problem: You change an Internet Agent access control setting in ConsoleOne, but the Internet Agent does not respond to the change.
Action: Exit, then restart the Internet Agent so it rereads its access control database (gwac.db).

Administrator Wants to Prevent Certain Types of Messages from Passing through the Internet Agent

Problem: Message flow through the Internet Agent is being hindered because large numbers of undesirable types of messages are passing through.
Explanation: You want to prevent messages larger than a specified size from coming into the GroupWise system through the Internet Agent.
Action: In ConsoleOne, browse to and select the domain where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties > Access Control. Double-click Default Class of Service.

Exit, then restart the Internet Agent.

Action: To restrict the size of incoming messages, click SMTP Incoming, select Allow Incoming Messages, select Prevent Messages Larger than X Kbytes, specify the maximum message size in kilobytes, then click OK.

Exit, then restart the Internet Agent.

Action: To restrict the size of outgoing messages, click SMTP Outgoing, select Allow Outgoing Messages, select Prevent Messages Larger than X Kbytes, specify the maximum message size in kilobytes, then click OK.

Exit, then restart the Internet Agent.

Explanation: By default, the Internet Agent downloads only 100 messages at a time. You want to increase or decrease this number.
Action: In ConsoleOne, browse to and select the Domain object where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties. Click Access Control, then double-click Default Class of Service. Click POP3, modify the setting in the Maximum Number of Messages to Download field as needed (valid settings range from 1 to 1000), then click OK.

Exit, then restart the Internet Agent.

POP3 Client Users Can’t Send Internet Mail through the Internet Agent

Problem: Users of POP3 mail clients are unable to send mail through the Internet Agent.
Possible Cause: Allow Message Relaying has been turned off.
Action: Make sure Allow Message Relaying is turned on. In ConsoleOne, browse to and select the Domain object where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties. Click Access Control > SMTP Relay, select Allow Message Relaying, then click OK.

Exit, then restart the Internet Agent.

POP3 Client Users Can’t Access the GroupWise Address Book through the LDAP Services of the Internet Agent

Problem: POP3 client users cannot look up addresses using the LDAP directory services created in their browser.
Possible Cause: If you are using Netscape Communicator, the Search Root setting does not match the Internet Agent LDAP Context setting.
Action: First, check the Search Root setting. In Netscape Communicator, click Edit > Preferences > Mail & Groups > Directory > GroupWise Address Book > Edit. Check the setting in the Search Root field. Note the current setting; it can be anything. Then, check the Internet Agent LDAP Context setting. In ConsoleOne, browse to and select the Domain where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties. Click Advanced Settings. Make sure the setting in the LDAP Context field matches the setting in the Netscape Communicator Search Root field.
Possible Cause: If you are using Internet Explorer, the Search Base setting does not match the Internet Agent LDAP Context setting.
Action: First, check the Search Base setting. In Internet Explorer, click File > New Message > Mail > Choose Recipients > Find. Right-click in the Search window, then click Directory Services from the pop-up list. Click GroupWise Address Book > Properties > Advanced. Check the setting in the Search Base for this Directory Service field. It can be anything; it defaults to c=US. Then, check the Internet Agent LDAP Context setting. In ConsoleOne, browse to and select the Domain object where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties. Click Advanced Settings. Make sure the setting in the LDAP Context field matches the setting in the Internet Explorer Search Base field.
Possible Cause: The Internet Agent does not have access to a post office to retrieve information from the GroupWise Address Book by accessing a post office database (wphost.db).
Action: In ConsoleOne, browse to and select the Domain object where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties. Click Access Control > LDAP Public, then make sure a valid post office has been specified. Make sure the post office access mode includes direct access. Make sure that message file processing has not been turned off. See Adjusting the Number of POA Threads for Message File Processing in Post Office Agent in the GroupWise 8 Administration Guide.

IMAP4 Client Users Can’t Access Mail through the Internet Agent

Problem: Users are unable to access GroupWise mail using IMAP4 from a browser because they are unable to log in.
Action: The user has Server Supports Encrypted Connections (SSL) turned on. In the user’s browser, check the setting for Server Supports Encrypted Connections (SSL). This is not currently supported by the Internet Agent. Deselect this option in the user’s browser. For example, in Netscape Communicator, click Edit > Preferences > Mail & Groups > Mail Server, then  deselect Server Supports Encrypted Connections (SSL) in the Mail Server Type box.

Extended Characters in User Names Prevent Delivery through the Internet Agent

Problem: Messages arriving from the Internet through the Internet Agent addressed to recipients who have extended characters in their user names are undeliverable.
Explanation: User names are part of message header files. According to RFC822 and RFC1521 standards, text in header fields must be composed of printable ASCII characters.
Action: As a workaround, create a nickname for affected users without the extended characters. See Creating a Nickname for a User in Users in the GroupWise 8 Administration Guide.

Messages Sent Out through the Internet Agent Don’t Wrap When Displayed by Recipients

Problem: Recipients of GroupWise messages sent across the Internet through the Internet Agent complain that the messages do not wrap correctly when viewed in their e-mail client software.
Action: Enable line wrapping in the recipient’s e-mail software.
Action: To specify how you want lines to wrap when displayed by the recipient, browse to and select the Domain object where the Internet Agent is installed. Right-click the Internet Agent object, then click Properties. Click SMTP/MIME Settings > Message Formatting, specify a setting for Line Wrap Length for Message Text on Outbound Mail, then click OK.

You can also specify the line wrap setting using the /wrap switch in the Internet Agent startup file (gwia.cfg).

The line wrap setting affects only RFC822-formatted messages, not MIME messages.

The Internet Agent Cannot Communicate with the Message Transfer Agent (MTA)

Problem: The Internet Agent is not receiving messages to send out across the Internet.
Explanation: The Message Transfer Agent distributes messages between post offices, gateways, and domains. A Message Transfer Agent is required in each domain. If the Message Transfer Agent is offline, outgoing messages are queued in the Message Transfer Agent directories. When the Message Transfer Agent is brought online, all queued messages are routed.
Action: Make sure the Message Transfer Agent is running and transferring messages. See Monitoring the MTA in Message Transfer Agent in the GroupWise 8 Administration Guide.
Action: Make sure the Message Transfer Agent is correctly configured in ConsoleOne. See Configuring the MTA in Message Transfer Agent in the GroupWise 8 Administration Guide.
Action: Check the Message Transfer Agent console or the Message Transfer Agent log files. Both of these sources provide a detailed record of Message Transfer Agent operations. See Using the MTA Server Console and Using MTA Log Files in Message Transfer Agent in the GroupWise 8 Administration Guide.
Action: Check the Status portion of the MTA agent console to find out whether the domain, post office, or gateway is closed. See MTA Status Box Shows a Closed Location.
Action: Make sure you can send messages between post offices. See Message Does Not Arrive between Post Offices.

The Internet Agent Displays a 450 MX Record Lookup Failure

Problem: The Internet Agent has requested a lookup from the Domain Name Server and did not get a response.
Action: Check the resolv.cfg file for correct configuration.

The resolv.cfg file should be in the following format: 

domain your_domain_name 
nameserver ip_address
nameserver ip_address 
nameserver ip_address

The domain name is first, followed by up to three nameserver IP addresses. The following is a sample resolv.cfg file: 

domain sgunix.org 
nameserver 172.16.5.18
Possible Cause: The IP address to your DNS has changed.
Action: Update the resolv.cfg file.
Possible Cause: TCP/IP is configured incorrectly.
Possible Cause: There is a problem with your network interface card.
Possible Cause: There is a problem with your network cabling.
Possible Cause: The DNS server is down.
Possible Cause: IP filtering has been added to the routers so the Internet Agent cannot see the DNS server.
Action: Ping the nameserver IP address to see if it is reachable from the gateway station.
Action: Ping the LAN segment router IP address.
Action: Make sure the named Internet Agent program is running on the nameserver server.
Possible Cause: Outbound ports are disabled. TCP/IP can use port 1024 through 2099 or some other range of outbound ports for sending.
Action: Check with your Internet service provider for the outbound ports it uses.

The Internet Agent Experiences a Problem with Rules Causing Looping

Problem: An infinite message loop can occur when a user has turned on a rule automatically replying to messages. If a message is then sent to another user who has an automatic reply rule, or to a list server, an infinite loop can occur.
Explanation: GroupWise has built-in counters to prevent most infinite loops, primarily those occurring within the GroupWise system. The following safeguards have been implemented by the GroupWise Internet Agent to prevent the looping of messages that go through the gateway:

  • Messages generated by a rule now have the From address changed to POSTMASTER@foreign_name.

  • A Reply To: field has been added with the real user address so most mailers will reply to the user, but list servers that reply to the From address will reply to the postmaster instead.

  • An Errors To: field has been added with the POSTMASTER foreign name address. With this field, undeliverable messages won’t be sent to a mailbox that has a rule associated with it.

  • If a message is sent to a user that is defined on a foreign domain or gateway, the Reply To: field will contain the postmaster’s actual resolved address. This allows the postmaster message to get to a postmaster who might not be on the GroupWise system.

Action: The infinite loop protection built into GroupWise might not work for some messages going through the gateway to Internet list servers. Such infinite loops must be resolved on a case-by-case basis.