The solution to the garbled header when sending UTF-8 encoded Chinese emails using PHP's mail function,

The solution to the garbled header when sending UTF-8 encoded Chinese emails using PHP's mail function, _PHP Tutorial

WBOY

Release： 2016-07-12 09:06:55

Original

1104 people have browsed it

The solution to the problem of garbled headers when sending UTF-8 encoded Chinese emails using PHP’s mail function.

I recently encountered a problem when using PHP’s mail function to send UTF-8 When encoding Chinese emails, the title appears garbled, but the body of the email is correct. At first I thought it was a page encoding problem, but found that there was no problem with the page encoding utf-8. After looking for the cause for a long time, I finally found the problem.

1. Use PEAR’s Mail class

PEAR’s Mail class allows you to choose to send mail using sendmail or SMTP. Such a packaged interface is easy to use, and you don’t need to reinvent the wheel yourself.

2. About the garbled characters of subject in headers

Do not put any text other than iso-8859-1 encoding directly into the subject. The correct way is to make the text in the subject comply with the specifications of RFC 2047. Assume that the encoding of the text in your subject is GB2312, then The correct subject should be in this format
$headers['subject'] = '=?GB2312?B?' . base64_encode('title text') . '?=';
If it is UTF-8, just replace the GB2312 at the beginning with UTF-8. It is recommended to use GB2312 encoding in the title, because MTA differentiation is really serious. Most MSPs use self-developed MTAs, and I believe that most domestic MTAs can support GB2312 encoding anyway.

If you are sending to an overseas MSP, it is recommended that you use base64-encoded UTF-8 text in the subject, because they most likely do not support GB2312 encoding.

3. Be sure to add content-type

in headers

The content-type in the email headers is similar to that of a web page, and is also in the format of text/plain; charset=gb2312. This option is mainly meaningful for clients that receive emails. It can avoid garbled characters on the client. Some Webmails will also encode and convert the content of the email based on the settings here to display it correctly. You can imagine what happens when you use gb2312 encoding to send it to the email address of .com.tw.

4. Correctly configure the host you use to send emails

1) Reverse resolution must be configured, because most non-fixed IPs cannot be reversely resolved, and some anti-spam strategies use this as a basis for judgment.
2) MX parsing must be configured. The reason is the same as above.
3) Make sure your return path can receive bounced emails, otherwise your email sending server may enter the receiving end's blacklist.

$subject = stripslashes($the_post['Title']); 
$headers　= "MIME-Version: 1.0\r\n"; 
$headers .= "Content-type: text/plain; charset=utf-8\r\n"; 
$headers .= "Content-Transfer-Encoding: 8bit\r\n"; 
$message = stripslashes(strip_tags($the_post['Content'])); 
mail($to, $subject, $message, $headers);

Copy after login

First use the function base64_encode() — use MIME base64 to encode the data
Add the encoding type before the title string, for example: =?UTF-8?B?
Add after the title string: ?=
For example:

<&#63;php  
 $to = "clairelume@qq.com"; //将此电子邮件地址改为自己的。  
 $name = $_POST['name'];  
 $email = $_POST['email'];  
 $subject = "来自博客读者的邮件";  
 $subject = "=&#63;UTF-8&#63;B&#63;".base64_encode($subject)."&#63;=";  
 $headers　= "MIME-Version: 1.0\r\n";  
 $headers .= "Content-type: text/plain; charset=utf-8\r\n";  
 $headers .= "Content-Transfer-Encoding: 8bit\r\n";  
 $message = $_POST['message'];  
 mail($to,$subject,$message,"From: ".$email."",$headers);  
 echo 'OK '.$name.', 您的邮件已发送。';  
&#63;>

Copy after login

In this way, the Chinese email title sent will not be garbled.

Isn’t it very simple? In fact, if you analyze the problem thoroughly, all problems will be solved easily. I hope this article will be helpful to everyone’s study.