Monitor unlimited number of servers
Filter log events
Create email and web-based reports

Direct access to Microsoft articles
Customized keywords for major search engines
Access to premium content

Event ID: 210 Source: MSExchangeMTA

Source
Level
Description
An internal MTA error occurred. Content conversion for message C=US;A=;P=test+internet;L=<s5b5a62a.027@mta.test.microsoft.com> failed. Conversion error: 258, Object at fault: 06000038, Original content type: 56010A00, New content type: 2A864886F7140501. PDU dump reference 1 [MTA DISP:FANOUT 15 112] (14)
Comments
 
This problem may occur if the message is sent by using a code page that is not supported by the message transfer agent. Code pages for Eastern European languages that use the Cyrillic alphabet may cause this problem. See ME829706 for a hotfix applicable to Microsoft Exchange Server 5.5.

This event may occur if you connect two Exchange 5.5 Server sites by using an X.400 connector and you click to select "Allow MS Exchange contents" and "Remote Clients Support MAPI" check boxes in the properties of the X.400 connector. See ME814553 for a hotfix applicable to Microsoft Exchange Server 5.5.

This problem occurs when your e-mail message is sent across a Microsoft Exchange Server 5.5 X.400 Connector and the third letter in the subject field of your e-mail message has a diacritic mark, such as an accent. See ME833035 for a hotfix applicable to Microsoft Exchange Server 5.5.

This problem can appear when an MS Mail address space is included in the Gateway Address Resolution Table (GWART). The MTA confuses the MS address type in MS Mail for the embedded MSXCX500 domain-defined attribute values; therefore, the routing problem occurs. See ME332019 for a hotfix applicable to Microsoft Exchange Server 5.5.

This problem may occur if the message contains incorrectly formatted Microsoft Database Format (MDBEF) encoding or when the MDBEF encoding contains MAPI properties that do not belong in the contexts that they are used in. See ME834570 for a hotfix applicable to Microsoft Exchange Server 2003.  

Also see ME146588, ME151790, ME156369, ME159188, ME159303, ME165093, ME175964, ME178821, ME222641, ME231799, ME232388, ME270695 and MSEX2K3DB for more information on this event.
As per Microsoft: "This condition can occur when a 1984 X.400 System is embedding Transport Neutral Encapsulation Format (TNEF) in the P2 of the message". See ME191947, ME169694, ME176132, ME821698 and ME833035 for more details.

Windows Event Log Analysis Splunk App

Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.

Read more...

 

Cisco ASA Log Analyzer Splunk App

Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.

Read more...