XADM: Unable to Match Custom Recipient Due to RFC1327 Conversion

Retired KB Content Disclaimer

View products that this article applies to.

This article was previously published under Q155379

Expand all | Collapse all

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.

Back to the top

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.

Back to the top

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):

S E R V P A C K

Back to the top

MORE INFORMATION

The incoming message's address was converted from RFC822 format to an X.400 OR Name using the RFC1327's printable string conversions:

        ps-encoded       = *( ps-restricted-char / ps-encoded-char )
        ps-encoded-char  =                   "(a)"               ; (@)
                                           / "(p)"               ; (%)
                                           / "(b)"               ; (!)
                                           / "(q)"               ; (")
                                           / "(u)"               ; (_)
                                           / "(l)"               ; "("
                                           / "(r)"               ; ")"
                                           / "(" 3DIGIT ")"

The DDA Type is "RFC-822" and the address is the escape equivalent version of the RFC822 address.

Back to the top

APPLIES TO

Microsoft Exchange Server 4.0 Standard Edition
Microsoft Exchange Server 5.0 Standard Edition

Back to the top

kbbug kbfix kbinterop kbusage KB155379

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