XIMS: SMTP Connector Ignores Setting to "Never" Use Exchange Rich Text Format When the Recipient Address Is Encapsulated

This article was previously published under Q300996
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
When Exchange 2000 users send mail with a FAX address type (or any other custom address type) over a Simple Mail Transfer Protocol (SMTP) connector and that mail is received by an SMTP server, if the Never check box is selected under Exchange rich text format for the SMTP connector, this setting may be ignored and an encapsulated address may be used. A Multipurpose Internet Mail Extensions (MIME) encoded message should be sent; instead, a message with a Winmail.dat file is sent, which the recipient's system may not be able to interpret.

In Microsoft Exchange Server 5.5, the SMTP connector does not ignore the connector setting.

NOTE: To locate the Never check box, in Exchange System Manager, click to expand Global Settings, right-click Internet Message Formats, click Properties, and then click the Advanced tab.
You cannot choose whether or not the recipient is a Messaging Application Programming Interface (MAPI) recipient when you create a contact with a fax address. By default, the Always send to this recipient in the Outlook rich text format attribute is always set for the fax address. When the Internet Mail Service receives this message, the FAX:Number is encapsulated.

This problem can occur because the Internet Mail Service uses the encoding setting of the encapsulated address, even if the Internet Mail Service domain setting under Exchange Rich Text format is set to Never.
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 theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:

Component: Internet Mail Service

File nameVersion

NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
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 2.
To enable this functionality, you need to add the following NonSMTPDomainEncoding registry value and set it to 1. If the registry value is set to 0 or is not available, the Internet Mail Service behaves as it did before the fix was applied and uses the encoding of the original contact instead of using the domain setting in the Internet Mail Service.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To add the NonSMTPDomainEncoding registry value and set it to 1:
  1. Start Registry Editor (Regedt32.exe).
  2. Locate and click the following key in the registry:
  3. If the following key does not exist, add it under MSExchangeTransport:
  4. On the Edit menu, click Add Value, and then add the following registry value under the Parameters key that you created:
    Value name: NonSMTPDomainEncoding
    Data type: REG_DWORD
    Radix: Hexadecimal
    Value data: 1
  5. Quit Registry Editor.

Article ID: 300996 - Last Review: 10/24/2013 06:53:48 - Revision: 3.1

  • Microsoft Exchange Server 2000 Service Pack 1
  • kbnosurvey kbarchive kbbug kbexchange2000sp2fix kbfix KB300996