OK, I see the parts to change the coding in TMimeMess so I'll have a play around with that and see if it can solve this problem.
Thanks for your help On 29/03/07, Roberto <[EMAIL PROTECTED]> wrote: > it is not likely the SMTP server, the problem is either at source: > message not encoded properly or wrong encoding set in header, or at > destination: the recepient is not decoding the message properly. Do > you have a sample message? > Yes, you can send with any encoding with synapse. > > On 28/03/07, David Perkins <[EMAIL PROTECTED]> wrote: > > Thanks Roberto. For most smtp servers this works OK, but one customer > > who shares the same ISP as me (and thus smtp server) we get equals > > chars where the line wraps. Is this likely to be the SMTP server or > > the POP3 end? > > > > I use the default synapse smtp functions, do they allow me to send > > with 8-bit chars? > > > > Many thanks > > > > David > > > > ------------------------------------------------------------------------- > 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 > ------------------------------------------------------------------------- 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
