[wp-trac] [WordPress Trac] #60420: Default wordpress at site.com sender address can be problematic

[WordPress Trac]

#60420: Default wordpress at site.com sender address can be problematic
-----------------------------+------------------------------
 Reporter:  thinlinecz       |       Owner:  (none)
     Type:  feature request  |      Status:  reopened
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Mail             |     Version:  1.5.1.2
 Severity:  normal           |  Resolution:
 Keywords:  close            |     Focuses:
-----------------------------+------------------------------
Changes (by SirLouen):

 * keywords:   => close


Comment:

 Replying to [comment:16 desrosj]:
 > However, maybe there is some mix of the following that can be explored:
 > - Add a warning or info-level notice in Site Health educating the user
 about how to make their site's email more reliable (seems like #62129 aims
 to accomplish some form of that)
 > - Possibly create a simple canonical plugin that helps site owners
 control and adjust the appearance of their site emails without needing to
 add their own filters.
 > - Work with the Hosting team to better document this and explore
 possible best practices to recommend. For example, I believe if the host
 is in control of the name servers for the domain name and no email related
 DNS entries are present, a forwarder could probably be set up by default.

 Yes, this is mostly the summary of the conclusions we got in this report.

 The idea was the following:

 - I was planning to leave this report closed, mainly because the idea was
 to do a new summary with all the information retrieved and create a new
 clean report focusing on this specific target, building the Health Check.

 - The canonical plugin is always an option, still I don't have a clear
 guidance on how canonical plugins work from scratch (like where to start
 implementing and all that)

 - This was already in process, I already sent the
 [https://github.com/WordPress/Advanced-administration-handbook/issues/406
 report upstream] to Hosting and [https://github.com/WordPress/Advanced-
 administration-handbook/pull/407 the corresponding PR] to activate this.
 After this, I might be probably improving a bit the docs to make this
 clearer.

 Replying to [comment:17 michael.orlitzky]
 > This is the hardest, because we absolutely still need an easily
 configurable "From" address, and all of the plugins that are currently
 using the site admin address as the "From" address are using it wrong.

 This is what we have already been discussing all the way through. The
 admin email is only meant to be a "To" address, mainly for notification
 purposes regarding the administration level of the site. All inputted
 emails (including other plugins in the ecosystem, like bbPress and
 Buddypress), use any "saved in the DB" email as a To email. For the `From`
 email, the solution was, as I said, using the filter.

 You argue that the filter is not well documented in the front end, and
 this is what we will be solved via Health Check and the Administration
 docs. These happen to be the classic docs go-to within the administration
 interface. As we already identified, changing this behaviour can provoke a
 backwards compatibility trouble, and setting the admin email as the `From`
 also collides, as I said, with the idea that this email could be mostly
 anything the admin decides (for example, the admin's Gmail account).

 Maybe we could also improve the copy for that, but again I would open a
 new ticket for this specifically. Personally, I prefer [https://oandre.gal
 /make-your-pull-requests-answer-a-single-question/ individual tickets for
 each single thing] (working as much atomically as possible), that trying
 to approach everything in a single shot.

 This is why I would consider this a `close` candidate at least, once all
 the new atomic tickets have been deployed.

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