Article ID: 279209 - View products that this article applies to.
This article was previously published under Q279209
This article has been archived. It is offered "as is" and will no longer be updated.
Mail users may see non-delivery reports (NDRs) if the name of a distribution list (DL) that they are a member of begins with a space.
When the directory is searched, to expand the DL membership, an LDAP query is constructed. Spaces and other special characters must be escaped following specific guidelines in Requests for Comments (RFC).
In distinguished names, spaces are escaped with a backslash (\) in accordance with RFC 1779. However, the distinguished name escaping in RFC 1779 does not apply to other attributes, including CN. Because Exchange 2000 reads the members in the RFC 1779 distinguished name format, but issue searches based on CN, Exchange 2000 has special code that unescapes characters that are escaped in the RFC 1779 format.
Searches may not work because LDAP is not expecting the space to be escaped. You can quickly verify this using Ldp.exe. If the name of the DL is " MyDL," the search (CN=\ MyDL) does not find the object, but the search for (CN=MyDL) does.
Now, even with CN attributes, there are several characters Exchange 2000 escapes in the RFC 2254 format. These characters are the parentheses (()) and asterisk (*). The RFC 2254 escaping mechanism looks like \XY, where XY are the hexadecimal digits that correspond to the ASCII character code:
The character must be encoded as the backslash (\) character (ASCII 0x5C) followed by the two hexadecimal digits that represent the ASCII value of the encoded character. The case of the two hexadecimal digits is not significant. Therefore, if you construct the LDAP query for your DL named " MyDL," following these guidelines, it looks like "CN=\20MyDL," which resolves correctly.
Character ASCII value --------------------------- * 0x2A ( 0x28 ) 0x29 \ 0x5C NUL 0x00 space 0x20
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
301378The English version of this fix should have the following file attributes or later:
(https://support.microsoft.com/kb/301378/EN-US/ )XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
Component: Transport Core
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 1.