Microsoft KB Archive Search

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.

  1. Home
  2. XCON: Content Not Supported NDR When Using X.400 Connector

XCON: Content Not Supported NDR When Using X.400 Connector

View products that this article applies to.

This article was previously published under Q146588

↑ Back to the top

Symptoms

When you send a mail message over an X.400 connection to a Microsoft Exchange recipient, it might result in the following Non-Delivery Report (NDR):
The message contains a content type that is not supported.
This can happen regardless of whether it was sent with an attachment or using Rich-Text Format (RTF).

The following error will be generated in the Application Log of the Microsoft Exchange Server:
MSExchangeMTA Event ID 210
An internal MTA error occurred. Content conversion for message C=US;A=ADMD;P=PRMD;L=servername

↑ Back to the top

Status

Microsoft has confirmed this to be a problem in version 4.0 of Microsoft Exchange.

↑ Back to the top

More information

This error is caused by duplication of information on the X.400 address. For example: 
   c=US;p=Microsoft;o=Mail;g=Exchange;s=User;ou=Seattle;cn=Test;s=User

Notice that there are two s= fields. Regardless of whether or not they contain identical information, it is an illegal address.

The Microsoft Exchange Message Transfer Agent (MTA) does not filter the address itself, but rather passes it down to the content converter to build an O/R address. This is the point at which it fails and is the reason for the content type not supported NDR message.

↑ Back to the top

Keywords: KB146588, kbusage, kbpending, kbbug

↑ Back to the top

Article Info
Article ID : 146588
Revision : 6
Created on : 10/28/2006
Published on : 10/28/2006
Exists online : False
Views : 301