I've found (I believe) what is the reason for this error.
The message is sent by a Debian mail server with default MTA - Exim and
received by a Microsoft exchange server. I don't know if this matter. Could
be that Indy doesn't know how to handle the messages produced by a Debian
mail server.
Now about Indy objects:
The received error (EIdTableNotFound) is raised into
Idcoder3to4.GetTableIndex for chars like #13 and #0.
The Content-Transfer-Encoding is different in the message at text and
attachment levels (7-bit and base64).
So, I believe that is used a wrong table or a wrong decoder (maybe a
UUDecoder could be more suitable instead of a base64Decoder?)
There is a workaround for this? How can be decoded chars like #13 or #0
(even though I think those chars have nothing to do inside the message)
Any opinion you'll post is valuable!
Mike_
