[wp-trac] [WordPress Trac] #60420: Default sender address
WordPress Trac
noreply at wordpress.org
Mon Jul 14 19:28:58 UTC 2025
#60420: Default sender address
-----------------------------+------------------------------
Reporter: thinlinecz | Owner: (none)
Type: feature request | Status: closed
Priority: normal | Milestone: Awaiting Review
Component: Mail | Version: 1.5.1.2
Severity: normal | Resolution: wontfix
Keywords: | Focuses:
-----------------------------+------------------------------
Comment (by SirLouen):
Replying to [comment:8 michael.orlitzky]:
> Mail hooks etc. are good workarounds for people who know what the
problem is, but TBH we just patch wordpress. I reported this because there
are a lot of people out there who know nothing about email except that
they don't get certain messages from their hosted WP installations. Using
the admin address isn't perfect, but it's a lot more likely to work
because, if the admin address doesn't work at all, someone is likely to
notice.
Generally, hostings set all this for you when you set up your WP with
them.
If anyone is plain clueless about hooks, you better not be using anything
but a hosting, or this will be your best problem.
Again, adding more fields to the frontend is probably never going to
happen. The tendency is to remove fields, in fact, the overall tendency is
going full headless config-wise with just the content management part from
the CMS. As I said, the admin email looks intuitive, but at the same time
it will run inadequate. It's not uncommon to have your Gmail for
notifications for example, as admin email and some server email for
delivery (in fact it's much more common than the other way around). So
definitely, intuition is not necessary the best practice.
Finally, stunts in this regard are left for extenders. Also be aware that
having WP deal with email as a smarthost is not the best idea because it
could add some overhead. Generally, you should be trying to leave this
100% to your local MTA and be as lean as possible. Personally, I only set
manually these parameters for testing, but this is not the best practice.
Currently, I'm leaning more towards supporting and elaborating on @knutsp
idea, which aligns more with the current state of the art of WP
--
Ticket URL: <https://core.trac.wordpress.org/ticket/60420#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list