Novell GROUPWISE 7 GATEWAY FOR MICROSOFT EXCHANGE - INSTALLATION AND ADMINISTRATION, Руководство по установке и администрированию, Страница: 102 / 144

102 GroupWise 7 Gateway for Microsoft Exchange Installation and Administration Guide
no
vd
ocx
(e
n)
6 Ap
ril 20
07
ConsoleOne then notifies the Exchange Gateway to restart so the new settings can be put into
effect.
The Exchange Gateway should now be visible to your SNMP monitoring program.
9.5 Notifying the Exchange Gateway
Administrator about Bad Messages
Occasionally, the Exchange Gateway encounters a message that it cannot process, either because the
message file has been damaged or because the recipient is not a user that is recognized by the
gateway. You can use the
/badmsg switch in the Exchange Gateway startup file to indicate how you
want the Exchange Gateway to handle messages that are damaged or undeliverable.
By default, bad messages are moved to the
domain \wpgate\ exchange \gwprob
directory
(the equivalent of /badmsg-move). If you want to take a look at bad message files, you can have the
gateway send the bad message files to the postmaster using /badmsg-send. If you do not yet have a
postmaster, see
Section 8.6, “Establishing Gateway Administrators,” on page 84 for setup
instructions.
If you do not want to do anything with bad messages, you can have the gateway delete them
immediately using /badmsg-neither.
9.6 Understanding Exchange Gateway Error
Messages
As you monitor the Exchange Gateway, you might occasionally see error messages. Exchange
Gateway error messages are documented with the source of the error, possible causes of the error,
and actions to take to resolve the error. See
Appendix A, “Error and Informational Messages,” on
page 117 .