XCLN: Outlook & Exchange One-Off SMTP Address & Display Name Parsing (184957)
The information in this article applies to:
- Microsoft Outlook 97 8.0
- Microsoft Outlook 97 8.01
- Microsoft Outlook 97 8.02
- Microsoft Outlook 97 8.03
- Microsoft Outlook 98
- Microsoft Exchange Client 4.0
- Microsoft Exchange Client 5.0
- Microsoft Exchange Windows NT client 4.0
- Microsoft Exchange Windows NT client 5.0
This article was previously published under Q184957 SYMPTOMS
Microsoft Exchange and Outlook clients are unable to parse one-off SMTP
addresses in the following forms:
<someone@microsoft.com>
First Last <someone@microsoft.com>
(First Last) <someone@microsoft.com>
"First Last" <someone@microsoft.com>
(First Last) someone@microsoft.com
"First Last" someone@microsoft.com
First Last <"<First>Last"@microsoft.com>
(First Last) "<First>Last"@microsoft.com
someone@microsoft.com (First Last)
someone@microsoft.com "First Last"
<someone@microsoft.com> (First Last)
<someone@microsoft.com> "First Last"
CAUSE
Microsoft Exchange clients and Microsoft Outlook 97 client versions 8.00,
8.01, 8.02, and 8.03 only accept one-off SMTP addresses in the form of:
Microsoft Outlook 98 version 8.50 accepts one-off SMTP addresses in the
following forms:
someone@microsoft.com
First Last <someone@microsoft.com>
Outlook 98 parses the SMTP address from the one-off string in the last
example above, but it uses the full original string as the display name.
WORKAROUND
Use the one-off SMTP addressing forms supported by the Outlook and Exchange
clients.
RESOLUTION
To resolve this problem, obtain the latest service pack for Exchange Server
version 5.5. For more information, please see the following article in the
Microsoft Knowledge Base:
191014
XGEN: How to Obtain the Latest Exchange Server 5.5 Service Pack
Additional SMTP one-off address parsing features are now available from
Microsoft as an official hotfix for Outlook and Exchange clients. Contact
Microsoft Technical Support for more information.
STATUS
Microsoft has confirmed this to be a problem in the products listed above.
A supported fix is now available, but has not been fully regression-tested
and should be applied only to systems experiencing this specific problem.
Unless you are severely impacted by this specific problem, Microsoft
recommends that you wait for the next Service Pack that contains this fix.
Contact Microsoft Technical Support for more information.
This problem was first corrected in Exchange Server 5.5 Service Pack 2.
Modification Type: | Major | Last Reviewed: | 4/7/2006 |
---|
Keywords: | kbQFE KBHotfixServer kbbug kbfix KB184957 |
---|
|