'Local Failure Notice' messages

[krbaker]

Note that the tz id="" seems to have lost the invalid char in that post, but it was as the error message says 0x4

[krbaker]

Seeing these more and more.

Now I've seen one on a calendar update which just seemed to corrupt the content type field!?!

XML Parsing Error: not well-formed

Line Number 130, Column 55:</content></mp></mp><mp ct="image/gif"><content>GIF89a</content></mp><mp ct="image/gif"><content>GIF89aA</content></mp><mp ct="text/html"><content>&lt;html&gt;&lt;body&gt;&lt;/body&gt;&lt;/html&gt;</content></mp></mp><attach aid="aa3d13a5-f4e6-4a9e-8470-3030720711c8:c700549c-a2ea-4fb4-8ba4-20654f2002bf"/></m></default></SetAppointmentRequest></soap:Body></soap:Envelope></Request><Response><soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body><soap:Fault><soap:Code><soap: Value>soap:Sender</soap:Value></soap:Code><soap:Reason><soap:Text>parse error: Error on line 130 of document : An invalid XML character (Unicode: 0x10) was found in the element content of the document. Nested exception: An invalid XML character (Unicode: 0x10) was found in the element content of the document.</soap:Text></soap:Reason><soapetail><Error xmlns="urn:zimbra"><Code>service.PARSE_ERROR</Code><Trace>btpool0-6264:1257190678054:e174b3d8bd546d69</Trace></Error></soapetail></soap:Fault></soap:Body></soap:Envelope></Response></SyncError>
------------------------------------------------------^

[fsiegel]

We hear of things like this extremely infrequently, and generally have a hard time reproducing. If you know where this meeting came from, or have any idea of anything special about, please let us know. That would help our repro cases.

There is a bug on this (bug 32967) that is slated for 6.0.3, our next release. We will also put the fix in 5.0.21. We'll have to see if we can still repro, and the fix will probably just be to get rid of the bad character. But info on how to repro (even the MIME message) will help.