Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 49

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
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
to 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
Action: Make sure the program is properly configured. Check the startup file to verify
that the
directory for 20 minutes. Then it transfers the file
directory for another attempt at sending to the Internet. The
send
/dhome switch is pointing to the Internet Agent directory.
/te and /tr switches.
®
domain directory.
Internet Agent Problems 49