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

WordPress Trac noreply at wordpress.org
Sat Aug 2 16:51:28 UTC 2025


#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:
-----------------------------+------------------------------

Comment (by SirLouen):

 Replying to [comment:19 michael.orlitzky]:
 > 1. A usable sender address is one of the most basic settings that needs
 to be tweaked -- or at least verified -- on every site. Requiring code to
 change it just means that it will remain incorrect for many people,
 leading to (silently) lost or junked messages.

 In fact we were talking about the future posssibility of creating some
 sort of canonical plugin, which could kind of sort this issue and maybe
 others related to this (a plugin maintained by WP organization). This
 could add the field you are mentioning, and other issues I've been
 encountering in the past months.

 > 2. It's a site-wide setting, so in particular it doesn't belong in a
 theme; upgrading a theme from wordpress.org/themes shouldn't erase the
 setting. Is there an easy way to install filters site-wide? (I don't think
 creating a new custom plugin for each site to change one email address is
 reasonable.)

 WP is meant to be extended. It's completely reasonable to have a custom
 plugin that adds this sort of filters. In fact is a great practice to have
 a custom plugin per site, where you add all your tweaks there. One of the
 biggest weaknesses of WP by far, is the effort developers do to preserve
 backwards compatibility, specially with hooks, so the code maintainance
 burden of plugins with hooks is virtually 0. You could have added this
 hook back in 2010, and come now and the plugin would have been working
 flawlessly.

 So having a custom plugin per site is not only reasonable, but very
 recommended. There are zillions of hook filters (I'm discovering a new one
 every single day), for a reason. This is essentially the core nature of
 WP. In fact, there are a couple of plugins that extend by just adding one
 hook.

 If you are worried about people not knowing that this is not configured or
 missconfigured, here is where the Health Check we commented before comes
 into play. Health Checks have been used like the swiss army knife for
 pretty much anything docs within WP admin UI, without having to add more
 fields or more notices.

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


More information about the wp-trac mailing list