XFOR: Setting Up Messaging Between GWISE and Exchange with Dirsync
ID: Q201165
|
The information in this article applies to:
-
Microsoft Exchange Server, version 5.5
SUMMARY
After running directory synchronization (dirsync) between Exchange Server and GroupWise, most companies will also want to enable message connectivity between the two systems. This article describes how to do so.
MORE INFORMATION
There are several things you should be aware of:
- The primary address of these GroupWise custom recipients are of type GWISE.
- These GroupWise custom recipients do not inherit the Exchange Server site SMTP proxy address in the same fashion as other custom recipients. Instead, the SMTP proxy address is derived from information gathered in the GroupWise Connector Property pages for their default SMTP naming convention.
With this in mind, there are a couple of steps needed to support messaging between Exchange Server and GroupWise.
- Messaging is accomplished by means of SMTP, thus, you need the GroupWise Internet Gateway installed in Netware as a Network Loadable Module (NLM) or as a Windows NT service. The same holds for Exchange Server. You need an Internet Mail Service configured for SMTP mail.
- Go to the Address Space on the Internet Mail Service configuration, add a second address type of Other.
- Enter GWISE as the type. The cost and address will depend on the complexity of your Exchange Server and Groupwise connections. The default Cost of 1, and Address of * should be sufficient for most cases.
- Make sure that the GroupWise SMTP domain is accessible from the Internet Mail Service, either by Domain Name System (DNS), host file, or by manually specifying the IP address in the Connections tab of the Internet Mail Service.
Now when you send a message from Exchange Server to GroupWise, it will route to the Internet Mail Service, and use the SMTP proxy address for that custom recipient as the target SMTP domain.
Additional query words:
GroupWise, SMTP mail, GroupWise Connector
Keywords :
Version : winnt:5.5
Platform : winnt
Issue type : kbhowto
|