Hi! | You should delay the encoding until you actually have to deliver the | content. Once you connect to the SMTP server, you can find out whether | it supports eight-bit transfers. As i have understood it the SMTP spec says 7bit. And since the mail goes through several MTA's and it would be hard to know what each of them could handle. And MS only uses 7bit content transfer for us-ascii otherwise it uses 8bit and encodes the subject with base64
| guess some heuristics work in this case (I am CCing Jeff, which can | correct me): | | * If message body contains nulls, use base64 encoding. | | * If not, if the target server does not support 8-bit encoding | use Quoted Printable. | | * Else, use plain text transfer. | The code that is on the CVS reacts exactly as the .NET runtime on some different encodings. I could write a library that handles everything with encoding better than .NETruntime but then it would not be compatible. But thats not for me to decide. If you want me to write a better one but not compatible i can do so. The api would be the same but the resulting mail would differ. Either way is ok with me :) Best regards Per _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
