Here's the scenario (ChilkatDotNet2.dll, 126.96.36.199):
Received an email with a PDF attached, the standard mail client/web client extract the file correctly, while the Chilkat.Email object loaded with the same message contains an invalid file.
If I lookup at the original source, with .FetchMime(uidl), this is what it shows at the start of the attachment
After i use the MIME string to generate the full Email object, this is how it's altered:
Now, "Content-Type: text/html" is an error from the sender client, which i have no control of, but the problem is that the chilkat object re-encodes the attachment
If i manually alter the string, injecting "application/pdf" in the right spot, and then pass that to .SetFromMimeText(TheMimeText), the message is okay, but of course this is not a feasible workaround
is there any other way to avoid this?
asked Dec 17 '13 at 04:14