XFOR: Message Reprocessed Due to Error 80040C15-F0000000

 Last reviewed: February 10, 1998
Article ID: Q174722
The information in this article applies to:
  • Microsoft Exchange Server version 5.5

SYMPTOMS

When an Exchange Server computer receives a message with a recognized character set, it reprocesses the message to MESSAGE.txt. The following warning is written to the Event log. 

   Event ID: 12035
   Source: MSEchangeNNTP
   Type: Warning
   Category: Content Engine
   Message with subject <subject text> from <name> had to be reprocessed
   due to error 80040C15-F0000000.

CAUSE

It is not possible to assume a default character set (for example, US- ASCII), because if the message truly contains some characters that do not map to the chosen default character set, the message is corrupted. The character sets here are "x-mac-roman" and "Macintosh."

WROKAROUND

You can create an alias in the MIME database to map the unknown character sets to a known character set.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange Server version 5.5. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: Character set
Keywords : XFOR
Component : IMail
Version : WinNT:5.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.