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

WordPress Trac noreply at wordpress.org
Tue Mar 11 23:31:36 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 iandunn):

 Replying to [comment:6 bpetty]:
 > I'm not sure where the "@macenzie.local" part is coming from. Obviously
 it's your actual test installation, but what I mean is that I'm not sure
 how it's being added to the Reply-To header, directly after the encoded-
 word part of the header.

 Yeah, that made me curious too. `macenzie.local` is the local hostname of
 the server, rather than the domain name of the virtual host. I've traced
 the headers from `wp_mail()` through PHPMailer to `mail()` and they look
 fine the entire time, even though they're malformed in the message I
 actually receive.

 So, that makes me wonder if maybe the `Reply-To` header string isn't being
 encoded properly, and sendmail is adding the extra `",[carriage
 return][tab][local hostname]"`bit.

 The string that PHPMailer sends to `mail()` looks like:

 `Reply-To: =?UTF-8?Q?Luk=C3=A1=C5=A1_<ian.dunn at example.org>?=`

 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.


 > Are you testing with latest trunk? PHPMailer was updated recently to
 5.2.7 (see #25560). When I test with latest trunk with this update, here
 are the verbatim headers that are generated:

 I originally encountered this on a production server running 3.8.1, and
 then reproduced it on my local environment with trunk.

 If it is happening at the server level, then it would make sense that some
 MTAs would handle it gracefully while others exhibit the behavior I'm
 seeing.

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


More information about the wp-trac mailing list