Several years ago I wrote a mass-email program that uses Indy components. It seemed to work everywhere but Outlook so I've got a bit of experience with Outlook. I doubt Outlook is the problem.
Outlook is very unforgiving about all of the smtp encoding. I've forgotten the details but as I recall you have two levels of encoding you have to follow. (Two RFC's) The first level is the "." junk related to line termination and word wrap. I can't recall what the second level of encoding is. For reference: Indy did both levels wrong (I've had to hand modify the Indy code to get it to encode correctly). If the corrupted text contains a lot of "=" signs you are doing the second level of encoding wrong (had something to do with hard returns as I recall). If the corrupted text contains a lot of boxes and such you are probably specifying your content type or character set wrong. ------------------------------------------------------------------------- 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
