[wp-trac] Re: [WordPress Trac] #4457: WP does not properly encode UTF-8 mail per RFC 2047

WordPress Trac wp-trac at lists.automattic.com
Mon Aug 27 04:30:20 GMT 2007

#4457: WP does not properly encode UTF-8 mail per RFC 2047
 Reporter:  trauschus                       |        Owner:  anonymous
     Type:  defect                          |       Status:  new      
 Priority:  high                            |    Milestone:  2.2.3    
Component:  General                         |      Version:  2.2      
 Severity:  critical                        |   Resolution:           
 Keywords:  rfc2047 mail reporter-feedback  |  
Comment (by takayukister):

 The point of this issue is not about encoding itself but about how encoded
 strings split into encoded-word chunks. 'encoded-word' is defined in
 [http://tools.ietf.org/html/rfc2047 RFC 2047] as:

   Generally, an "encoded-word" is a sequence of printable ASCII characters
 that begins with "=?", ends with "?=", and has two "?"s in between.

 And as trauschus quoted from RFC 2047, "a multi-octet character may not be
 split across adjacent encoded-words". So the header of his received mail
 should by right be:


 because '=E2=80=99' is a character (’) [0x2019], not splittable.

 I think this issue is solved if someone fix
 phpmailer.php#L1136 EncodeHeader() in class-phpmailer.php] to treat this
 splitting properly. I'm trying but not yet succeeded.

Ticket URL: <http://trac.wordpress.org/ticket/4457#comment:7>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software

More information about the wp-trac mailing list