This bug is separated from bug# 16878 to ease the tracking of the fix. Steps to reproduce: -input non-ascii (accented chars) into the message body; -click send and get the message; //note: all non-ascii are stripped from the body, leaving only us-ascii there *****observed with 1999-10-20-M11 win build ******
Only text/plain mails can be composed with yesterday's build. So I assume this is for plain text mail. On my local build with a fix of the problem, I can send html and I don't see this problem. Plain text also working fine with Latin1 characters. Please try again with today's build once it's released.
sending this to marina for check.
I used today's release build 1999-10-21-11-M11 on my WinNT. I could send both html and plain text with Latin1 characters (e.g. á, ê). Marking as WORKSFORME.
This was happening yesterday, and per ftang i separeated it into the new bug not to overload #16878 with two problems.Today it is working for me also, somehow got fixed. I would say resolved as fixed.
marking as such after testing 1999-10-21-10M11 build