Novell GROUPWISE 7 - TROUBLESHOOTING 2 Troubleshooting Manual page 56

Possible Cause: Outbound ports are disabled. TCP/IP can use port 1024 through 2099 or some
The Internet Agent Experiences a Problem with Rules Causing Looping
56 GroupWise 7 Troubleshooting 2: Solutions to Common Problems
Action: Make sure the named Internet Agent program is running on the nameserver
server.
other range of outbound ports for sending.
Action: Check with your Internet service provider for the outbound ports it uses.
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.