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

Comment (by mvl22):

 > “I do not think WordPress should be making any attempt to test the
 deliverability of the address” @mvl22 would you care to share more about
 why? in the case that email is setup appropriately, would it be difficult
 to positively identify a proper return-path address? in which cases would
 an attempt be misleading? in other words, I would imagine that a failure
 to detect delivery might not say anything, but a confirmation of delivery
 would. I have no idea how to detect deliverability so maybe you are saying
 WordPress doesn’t have an avenue to do so?

 Because it's complex. I've no strong objection to it, but this is not the
 problem the ticket is actually describing. The problem is simply that
 WordPress assumes that the domain used by the site is enabled for
 deliverability, which is no longer a correct assumption in 2025. Therefore
 that address simply needs to be easily configurable.

 If, having solved that problem, people want deliverability detection etc.
 to be solved also, fine. But we really must make the address configurable
 easily in the first place (i.e. not by having to write and deploy a
 plugin).

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