Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

XADM: Display Name Missing for RFC 822 "Group:;" Address


View products that this article applies to.

This article was previously published under Q176538

↑ Back to the top


Symptoms

Microsoft Exchange Server versions 4.0 and 5.0 do not handle the Display Name (DN) correctly in messages received from the Internet that were sent to a Distribution List (DL) using the RFC 822 addressing form of:

Group:;

↑ Back to the top


More information

The addressing option defined by RFC 822 section 6.2.6 states that users may be able to address messages to a group or DL in the form:

Group:;
Notice that no individual members were listed in the address above. When a message sent externally to a DL in this form arrives in Microsoft Exchange Server, the DN is not handled correctly. In Microsoft Exchange Server version 4.0, users will see the following:

Display Name: The recipient's address is unknown.
E-mail address: The recipient's address is unknown.
In Microsoft Exchange Server version 5.0, the DN will be blank. The messages will still be delivered to the recipients though they will be unable to reply to the DL.

↑ Back to the top


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

Customers who experience this problem on Microsoft Exchange Server version 4.0 will need to upgrade to Microsoft Exchange Server version 5.0 and Microsoft Exchange Server Service Pack 1 (SP1) and install the post SP1 hotfix in order to resolve this issue.

↑ Back to the top


Keywords: KB176538, kbqfe, kbfix, kbbug, kbqfe, kbhotfixserver

↑ Back to the top

Article Info
Article ID : 176538
Revision : 7
Created on : 10/28/2006
Published on : 10/28/2006
Exists online : False
Views : 260