XADM: Secondary Proxy Address Replaces Target Address of CR

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q157007

Expand all | Collapse all

SYMPTOMS

When you create a Custom Recipient (CR) and add a secondary proxy address that is the same type (SMTP, X400, or MS) as the target address, the target address field will be replaced by the secondary proxy address field.

Back to the top

CAUSE

The E-Mail address and value in the proxy address list are kept in sync by a case insensitive comparison of the proxy address to figure out whether the E-Mail address should be updated. This is incorrect because the primary proxy address is always in upper case and the secondary address is always lower case.

Back to the top

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 4.0. This problem was corrected in the latest Microsoft Exchange Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base:

SERVPACK

Back to the top

APPLIES TO

Microsoft Exchange Server 4.0 Standard Edition

Back to the top

kbusage KB157007

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top