XFOR: Custom Recipient Receives Rich Text Format Information Unexpectedly (173713)
The information in this article applies to:
- Microsoft Exchange Server 5.0
This article was previously published under Q173713 SYMPTOMS
A Custom Recipient (CR) receives a message that includes Rich Text Format
(RTF) information. This occurs even if Allow Rich Text Format is not
selected in the Advanced tab of Properties for the CR. If the original
message sent contained an attachment, the attachment may be received by
non-Microsoft mail clients as an unreadable RTF attachment.
CAUSE
While expanding Distribution Lists and processing alternate recipients, the
Microsoft Exchange Message Transfer Agent (MTA) did not preserve the CR
property indicating whether it should receive RTF.
WORKAROUND
In the Microsoft Exchange Administrator program, change the Send Microsoft
Exchange Rich Text Formatting option to NEVER in the Interoperability
dialog box of the IMC Internet Mail property page (use the Specify Message
Content by E-Mail Domain option if you want to restrict this option to
individual domains).
For additional information about a client-side fix for this problem, click the article number below
to view the article in the Microsoft Knowledge Base:
169666 XADM: POP3 Users may not Receive an Attachment if Part of DL
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):
Microsoft has confirmed this to be a problem in Microsoft Exchange Server
version 5.5. This problem has been corrected in the latest U.S. Service
Pack for Microsoft Exchange Server version 5.5. For information on
obtaining the Service Pack, query on the following word in the Microsoft
Knowledge Base (without the spaces):
Modification Type: | Major | Last Reviewed: | 4/7/2006 |
---|
Keywords: | kbQFE KBHotfixServer kbbug kbfix KB173713 |
---|
|