[wp-trac] [WordPress Trac] #21659: wp_mail() problem with Reply-To header

WordPress Trac noreply at wordpress.org
Wed Mar 12 00:02:54 UTC 2014


#21659: wp_mail() problem with Reply-To header
--------------------------+------------------------------
 Reporter:  pavelevap     |       Owner:
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Mail          |     Version:  3.4.1
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by bpetty):

 Replying to [comment:7 iandunn]:
 > That looks correct to me, but so far I haven't been able to find an RFC
 or anything that specifies what the format should be.

 [https://www.ietf.org/rfc/rfc2047 RFC 2047] describes UTF-8 encoded
 headers (also see #18521). As far as I can see, encoded-words are allowed
 in To, From, CC, BCC (and thus likely Reply-To headers). Although, looking
 through here again, it does mention that "An 'encoded-word' MUST NOT
 appear in any portion of an 'addr-spec'." I think this means that instead
 of this:

 {{{
 Reply-To: =?UTF-8?Q?Luk=C3=A1=C5=A1_LastName_<foo at example.org>?=
 }}}

 It's possible that it's *supposed* to be:

 {{{
 Reply-To: =?UTF-8?Q?Luk=C3=A1=C5=A1_LastName?= <foo at example.org>
 }}}

 In other words, I think it's possible that the actual email address is
 supposed to never be included in an encoded-word section.

 This would certainly mean it's a bug in PHPMailer upstream then if that's
 correct.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/21659#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list