[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 SirLouen):

 Replying to [comment:28 michael.orlitzky]:
 > This will almost never help, because sender address verification is
 almost never the problem. Moreover, "nobody" hosts their email on their
 web server (check the market share of Gmail + O365), so this advice is
 impossible for most people to follow.

 @michaelorlitzky I think we are mixing concepts here. Surely Google and
 Microsoft, could be leading in terms of email service. But here we find
 two main scenarios:

 === Beginner User

 A novice user pretty much purchases the domain in the same hosting that is
 going to provide his WordPress installation, namely, Bluehost, Hostinger,
 etc... (or at worst, they may purchase it outside, and be asked by the
 host to set the DNS pointing to them). The host will set your DNS to their
 own instance and they will get everything configured for you, including
 the `wordpress at yourdomain.whatever`.

 Here the big question as I commented to @desrosj is, for those hostings
 with limited number of inboxes for local parts (say a limit of 50
 inboxes), I'm not sure if they include `wordpress` one for free, or if
 they actually expect you to create one. In any case, a notice in the
 Health Check will be useful for either changing it via
 plugin/hook/functions.php, or suggesting to create such inbox or to be
 aware if that inbox is a valid receiving option. Here is where the check
 that @knutsp was proposing takes place. And this is only relevant, for the
 reply part (so the replies are not lost for the beginner).

 === Advanced User

 The advanced user, in this case, a person like you that has his main mail
 service outside, say Google Workspace, but needs the local MTA installed
 with WP to operate.

 Firstly, I'm assuming that SPF and DKIM are out of this equation correctly
 configured. Neither SPF and DKIM care about the local-part. You can pretty
 much use any randomized local part and it will still get through as long
 as the domain has the SPF pointing to your WP host and a DKIM selector
 with the public key rightly configured to match the WP local MTA

 A different topic here is, as I said in my previous post, if you want to
 have a different domain for your MTA. Instead of using your domain
 `example.com`, like I do in many installations, you want to have
 `mail.example.com` here. In this case, you definitely need to change your
 `From:`. Here is where the hook takes place and this should be also
 documented in the Health Check plus the Administration Handbook. But as I
 say: If you are so pro to by using a setup like this, you should know that
 WP is a hook based framework, so the expectation of having to add the code
 must be high.

 =====

 Now let's move into the health check part, as @desrosj already commented,
 we should put these concerns in #62129 as this is where we will be working
 on.

 I'm going to copy all the concerns and answers there to continue the
 conversation on that topic.

 Replying to [comment:29 knutsp]:
 > That's all. I wonder why I started participating on this ticket. I'm
 out.
 As @desrosj
 [https://core.trac.wordpress.org/ticket/60420?replyto=29#comment:26
 suggested you] just focus on #62129, which is the direction we will be
 taking. This has turned out to be a philosophical report.

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