Re: Undeliverable from Exchange Server

[Kathy J. Mikich]

Karen the first thing I would check here is that the recipient policy is actually stamping the user in the groupwise container in AD with the correct Gwise address space and not more then one.  If all the GroupWise users have a Gwise address space on them (only one) then next check your gwproxy.dll in the exchange installation directory / address space / gwise/ i386 or there bouts.  I don't have a system in front of me so going from memory.  The Gwproxy.dll is used to generate the Gwise address space that is put in the recipient policy and must not be an older gwproxy.dll that say Microsoft generated.   Check the dates of this file on all exchange servers against the file you have by this name in the directory of software you downloaded to install the gateway.  If it is not the same then delete the gwproxy.dll from all exchange servers, remove it from the policy, run the policy so users no longer have a gwise address space on them.  With it all cleaned up run the gateway install again and check the button for install addressing components only.  This will install the gwproxy.dll add the address space to the policy and the uses address space will be corrected. 

 

you must make sure we don't have old gwise address space on the users and they instead get the newly created one using the correct gwproxy.dll

 

>>> Karen<Kj...@altamed.org> 2007-12-05 3:46 PM >>>
We just completed installed GroupWise Gateway for Microsoft Exchange. The
Exchange users are able received the e-mail sent from the GroupWise user.
The GroupWise user are unable received the e-mail from exchange user. We
received the following undeliverable message from exchange gateway:

The following recipient(s) could not be reached

The e-mail account does not exist at the organization this message was
sent to. Check the e-mail address, or contact the recipient directly to
find out the correct address.

<exchange server name.domain.pri #5.1.1 smtp;550 5.1.1 User unknown>

We have GroupWise 7.02  and exchange server 2003.

Did anyone have the same problem we have? Please help.