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

WordPress Trac noreply at wordpress.org
Fri Dec 12 23:36:54 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:36 amanandhishoe]:
 > Email configuration itself is beyond the scope of WordPress core.
 However, WordPress could provide guidance. For example, Site Health could
 check whether SPF, DKIM, and DMARC records exist for the domain and show a
 notice such as:
 > “Your domain does not publish SPF, DKIM, or DMARC records. Emails sent
 from this site are likely to be rejected or placed in spam.”

 Yes, that could be an option to be added. We were already discussing about
 health checks for this purpose like #62129

 Replying to [comment:35 mvl22]:
 > I think forcing the requirement to create a plugin and define a
 `wp_mail_from` value is not really an acceptable workaround (though it
 should remain in place). Update notifications are a security matter. The
 from address should therefore be settable by an administrator easily, just
 as any other setting is.

 Nowadays security updates go on point releases which are automatic by
 default regardless of the major version you sit in (if still supported).
 So if you want to deactivate this automatic updates for point releases for
 any reasons, I would seriously rethink taking your time into supporting
 the mail behaviour with whatever hooks it's required.

 One thing that I have commented above in many other posts is the nature of
 the current mail system in WP. This is not something I support, but is
 worth knowing to understand how troublesome it is to change. Mail all
 around currently is a `pluggable` (a.k.a. meant to be managed through a
 plugin). One of my plans is removing this "pluggable" status in the
 future, with how things are going I would look minimum into 7.1 or 7.2,
 nothing closer.

 About the frontend field expectations, I always thought that a frontend
 place to add the from address (and probably the `From name`), could be
 great as these are very useful fields and setting up mail in a trustworthy
 way should be something that every single WP user should take his time to
 set up, just like any other feature, as mail is the current and long-term
 main notification medium (there were plans of extending the notifications
 API but this is not going to happen any time soon)

 I've seen myself in endless discussions about new Frontend inputs that get
 to nowhere, and then I see things like this:

 [[Image(https://i.imgur.com/hIWCeb3.png)]]

 and

 [[Image(https://i.imgur.com/6Qs8Xfs.png)]]

 It's a 🤦‍♂️

 Currently, all the frontend updates are surging in the "Appearance" tab
 (that is being controlled by the Gutenberg team). It's remarkable because
 most new items are going to even have the new interface. So I'm still
 thinking how to give this a plot twist to avoid inferencing in the
 Jurassic Park admin menus. Surely, we will see a `From address` one day
 somewhere.

 Long story short: don't expect anything anytime soon, but eventually, we
 will see some improvements.

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


More information about the wp-trac mailing list