Use UTF-8 encoded/jmail component to send mail garbled problem

A long time ago listen to a friend said, use UTF-8 code to send mail, there will be garbled situation occurs. Recently for the company to develop support for multi-language Web sites, just want to use UTF-8 coding. The website has the member registration, the inquiry form and so on module all needs to send the mail to the registered user or the administrator. The mind is inevitably to and this garbled problem head-on conflict.

Curiously, the project has been carried out smoothly, although the mail in the Chinese on the Web page to check is really garbled. However, it is normal to view it locally after receiving it with Outlook or Foxmail. Ha, is it true that a friend is referring to garbled characters? It seems that the problem is not, I will upload the site to the server to another group to test.

The next day, just as I relax in the song to read the article, the colleague there feedback came to say that the message will be garbled. Heart under a startled, immediately tried, sure enough, with Foxmail received open or a question mark. Google, for example, wants to see if anyone has encountered the same problem, but nothing has been found. Then went to Dimc.net (JMail's official website) of the forum shook for a half-day, also failed to solve the problem. It seems only on my own ...

After two hours of constantly modifying the code on the server to send mail tests, the problem did not improve.

Starting with the difference between the local computer and the server, we first discovered that the JMail version was inconsistent and updated the JMail version of the server. Invalid. The sensory problem should not be on the Web site program and the JMail component. In order to determine the crux of the problem, the message will have been assigned to jmail content output, sure enough, here the content of the message has been garbled. My operating system is installed in Simplified Chinese version, the server is the English version, and finally. Try to use Chinese in the language of the advanced, non-Unicode programs in the locale and language options, and after restarting the server, the problem is finally solved ...