It seems that the code


can not correctly identify the correct character encoding for Russian (uses charset="utf-16" instead of utf 😎. Is the any other way to set directly encoding for all messages?

v1.9.6.1

I cannot seem to find another reliable method. char is 2 bytes (so utf-16). This should work.

I cannot seem to find another reliable method. char is 2 bytes (so utf-16). This should work.

http://forum.yetanotherforum.net/yaf_postsm55427_Few-email-issues.aspx#post55427 

I cannot seem to find another reliable method. char is 2 bytes (so utf-16). This should work.

http://forum.yetanotherforum.net/yaf_postsm55427_Few-email-issues.aspx#post55427 

I am using non-english culture and also facing the same issue. I also did the following modification

public static bool ContainsUnicodeCharacter(string input)
{
return input.ToCharArray().Any(c => (c > '\x00ff'));
}

and used Encoding.Default instead of Encoding.UTF8, still got the messy message body. I found the problem is because the input string contains \n instead of \r\n. Really wonder why.

Very interestingly, I tested on another machine, it shows the normal \r\n. Not sure if it's database problem or the operating system problem.

Further investigation finds it's because the XmlSerializer doesn't deserialize the streamReader object correctly. it only parses new line as \n.

Yucks.