[wp-trac] [WordPress Trac] #49661: mails, Howdy, wp_mail() and filters spreading

[WordPress Trac]

#49661: mails, Howdy, wp_mail() and filters spreading
-------------------------------------------------+-------------------------
 Reporter:  arena                                |       Owner:  (none)
     Type:  defect (bug)                         |      Status:  new
 Priority:  normal                               |   Milestone:  Future
                                                 |  Release
Component:  Mail                                 |     Version:  1.5.1.2
 Severity:  normal                               |  Resolution:
 Keywords:  good-first-bug has-test-info needs-  |     Focuses:
  patch                                          |
-------------------------------------------------+-------------------------
Changes (by SirLouen):

 * keywords:  has-patch => good-first-bug has-test-info needs-patch
 * version:  5.4 => 1.5.1.2
 * type:  feature request => defect (bug)
 * milestone:  Awaiting Review => Future Release


Comment:

 == Bug Reproduction Report

 === Description
 ✅ This report validates that the issue can be reproduced.

 === Environment
 - WordPress: 6.9-alpha-60093-src
 - PHP: 8.2.29
 - Server: nginx/1.29.1
 - Database: mysqli (Server: 8.4.6 / Client: mysqlnd 8.2.29)
 - Browser: Chrome 139.0.0.0
 - OS: Windows 10/11
 - Theme: Twenty Twenty-Five 1.3
 - MU Plugins: None activated
 - Plugins:
   * Micro Email Testing 1.0.0
   * Test Reports 1.2.0

 === Reproduction Instructions
 1. Create a comment to a post
 2. Add a reply to that comment
 3. Check the received email, more specifically the Reply-To
 4. 🐞 It's being wrongly formatted like:

 {{{
 Reply-To: "\"tester at example.org\"" <tester at example.org>
 }}}

 The name is wrongly being picked + double quotes.

 === Actual Results
 1.  ✅ Error condition occurs (reproduced).

 === Additional Notes

 After reviewing the patch, I can say that despite this was very ambitious,
 it would bring massive backward compatibilities issues. I think there is a
 good amount of content to make feature or canonical plugin I've been
 thinking around. I was considering on closing as `maybelater` for these
 reasons, but then I noticed that between the code, there is a bug that
 I've been able to reproduce, so we should be focusing on this bug for this
 ticket.

 The problem is happening among these lines:
 https://github.com/WordPress/wordpress-
 develop/blob/dd2d7efd9dc11a362056be6cd7fc75ccd6b0cf22/src/wp-
 includes/pluggable.php#L1751-L1761

 Here, there is not only the double quotes formatting issue, but using the
 email instead of the name, that we also could have (Both email and name
 fields are mandatory). First introduced in [3035], #1593

 === Supplemental Artifacts

 Raw email received:

 {{{
 Return-Path: <test at example.com>
 Received: from localhost (wordpress-develop-php-1.wordpress-
 develop_wpdevnet. [172.20.0.3])
         by 93e77d70be1e (Mailpit) with SMTP
         for <test at example.com>; Sun, 17 Aug 2025 16:23:45 +0000 (UTC)
 Date: Sun, 17 Aug 2025 16:23:45 +0000
 To: test at example.com
 From: "Mr. Tester" <test at example.com>
 Reply-To: "\"tester at example.org\"" <tester at example.org>
 Subject: [WordPress Develop] Comment: "Hello world!"
 Message-ID: <IzHNN1HuqMA90LeQ9cRI3IT38sLlzkOuncMuCLX4k at localhost>
 X-Mailer: PHPMailer 6.10.0 (https://github.com/PHPMailer/PHPMailer)
 MIME-Version: 1.0
 Content-Type: text/plain; charset=UTF-8

 New comment on your post "Hello world!"
 Author: Mr. Tester (IP address: 172.20.0.1, 172.20.0.1)
 Email: tester at example.org
 URL:
 In reply to: http://localhost:8889/wp-
 admin/comment.php?action=editcomment&c=3#wpbody-content
 Comment:
 This is a test example

 You can see all comments on this post here:
 http://localhost:8889/2025/08/17/hello-world/#comments

 Permalink: http://localhost:8889/2025/08/17/hello-world/#comment-4
 Trash it: http://localhost:8889/wp-admin/comment.php?action=trash&c=4
 #wpbody-content
 Spam it: http://localhost:8889/wp-admin/comment.php?action=spam&c=4
 #wpbody-content
 }}}

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