|Subject:||Re: Indy 9.0.18: Can't get attachment when email in specific format|
|Posted by:||Remy Lebeau (TeamB) (firstname.lastname@example.org)|
|Date:||Wed, 1 Dec 2004|
"ilya ovsischer" <iomong…@popa.com> wrote in message
> I just need to know if it can be solved by ugrading to Indy 10
Yes, the issue is addressed in Indy 10.
> Content-type: image/tiff
> Content-Transfer-Encoding: base64
> Content-Disposition: inline; filename="fax.tif"
There is no MIME boundary specified in the headers that you have shown.
Indy 9 will not be able to automatically decode the binary data properly.
In order for Indy 9 to recognize the "base64" encoding for the message
content, there has to be a MIME boundary specified, even if it is not
actually used in the content. Without that boundary present in the headers,
TIdMessageDecoderMIME will not be invoked to decode the data. The content
will be stored in the main Body property in its original encoded format, and
you will have to decode it manually.
> I did add some !, so borland will allow me to post this message.
You do not need to do that. You can post the headers as-is and they will
Indy 9.0.18: Can't get attachment when email in specific format posted by ilya ovsischer on Wed, 1 Dec 2004