XADM: Unable to Match Custom Recipient Due to RFC1327 Conversion (155379)
The information in this article applies to:
- Microsoft Exchange Server 4.0
- Microsoft Exchange Server 5.0
This article was previously published under Q155379 SYMPTOMS
Custom recipients created to allow addressing to SNADS recipients fail,
because the custom recipient address does not match after the conversion
from Internet to X.400 mail.
CAUSE
The conversion of the RFC822 address attributes to X.400 attributes
mistakenly leaves the "at" sign (@) in the address. Because this is
not a printable character in X.400, the address does not match the custom
recipient address, and the message is returned as non-deliverable. The FROM
field of the message displays as an X.400 address with a DDA value when a
custom recipient exists in the site.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Exchange Server,
versions 4.0 and 5.0.
This problem was corrected in the latest Microsoft Exchange Server 4.0 and 5.0
U.S. Service Packs. For information on obtaining the service pack, query on the
following word in the Microsoft Knowledge Base (without the spaces):
Modification Type: | Minor | Last Reviewed: | 4/28/2005 |
---|
Keywords: | kbbug kbfix kbinterop kbusage KB155379 |
---|
|