> Amost, try also to delete all "Content-Disposition: inline", that > possibly confuse specific version of Outlook. > > Lukas, you force 'inline' on each (as called by RFC) bodypart (text > or html content). However, from RFC 2183:
You are not true! I am not force this! You can create any MIME part with totally any parameters and headers, as you wish. MIME part is under your control. You can create your MIME part with any parameters you wish. So, possible solutions: - create mime part by yourself and set all properties as you wish. - of use pre-maded part creation code in TMimeMess, and after part creation you can modify part properties. Please, consider one important fact: MIME encoder/decoder is TMimePart! TMimeMess is just helper class for a few common cases. TMimePart have a few part creation helper methods, what cover a few typical usages. However is impossible to cover all part creation cases! It have too many possible combinations. So, AddPartHtml is designed for adding of HTML based message text. 'Inline' is here correctly. If you want to do non-typical case - add HTML as attachment for example, you must use different part properties, of course! But AddPart* methods cannot cover all possible cases, include this one. However you can add part manually (for example by TMimeMess.AddPart) and set all needed properties as you wish. -- Lukas Gebauer. E-mail: [EMAIL PROTECTED] http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ synalist-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synalist-public
