Paul J Stevens wrote:
A final followup for tonight: Those non-ascii chars were not there at the beginning of the original message. So all this is quite likely related to the parser bug (or another parser bug) after all.
So what you're saying is that there are characters in the message stored in the database, that should not be there? If this is correct then the bug is in the message insertion code. It sounds a lot like a piece of uninitialised or non-cleared (no memset(buffer, '\0', size) used) memory that's being inserted, giving random results.
Can anybody send the list such a message? And even better, attach a trace of the message being inserted (that should give some clues to the origin of the 'random' characters.
Ilja
