XFOR: IMS Uses Incorrect Reply To Address

Last reviewed: February 13, 1998
Article ID: Q176739
The information in this article applies to:
  • Microsoft Exchange Server version 5.0

SYMPTOMS

This problem occurs when you are using the routing feature in following scenario:

   UNIX (host1.osu.com)----Exchange Server (osu.com)-----Internet

In the registry for IMS/Parameters to have: AddressRewrite:DWORD=1 and ResolveP2:DWORD=1.

In Exchange Server, you create a customer recipient for a USER1 on host1 as follows:

      smtp  user1@host1.osu.com
      SMTP  user1@osu.com

A mesasge is sent from user1 where the originator address is user1@host1.osu.com into Exchange Server destined to the Internet.

The problem is that the Internet recipient sees user1@host1.osu.com in the 822 body instead of user1@osu.com.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server, version 5.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Exchange Server version 5.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

   S E R V P A C K
Keywords          : kbbug5.00 kbfix5.00.sp2 XFOR
Version           : WinNT:5.0
Platform          : winnt
Issue type        : kbbug
Solution Type     : kbfix


================================================================================


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 13, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.