We have concluded the Kinsta.com case.
We have installed the WP Mail SMTP plugin and Mailgun for transactional emails.
The emails are now correctly authenticated and no longer go to the spam folder.
Below are the before and after images on Mail-tester.com:
An interesting note about the “after” test: I was intrigued by the score of 8, as I was expecting more.
Upon further investigation, I realized that the reason was the content, as I used a standard test message 🙂
It is important to note that the low score before the changes was not due to technical problems with Kinsta.com. It is a characteristic of the email infrastructure that could be identified because we used good authentication and email-sending monitoring practices.
And the final feedback from the client:
I am setting up an email and LinkedIn sales funnel automation for a client’s sales pipeline.
When a prospect reaches out to the sales team, they enter this automation funnel (still subject to changes):
Although details are confidential, we can confirm that this automation will use LinkedIn and email simultaneously.
Pipedrive, Instantly (to be defined), Dripify, Klenty, and Calendly will be orchestrated through Zapier when necessary.
Do you remember a few days ago when I briefly talked about the solution to a case of messages being blocked by Yahoo?
Today the client contacted me again, saying that:
I am still having some deliverability issues, but it’s intermittent, see image from an email this morning that was attempted to be sent to me:
I found it quite strange, and upon checking his MX records, I discovered they differed from the recommended settings.
Client’s MX settings
Google’s MX settings
When I initially worked on the case, I didn’t even consider issues with the MX records because the reported problem was specifically with the Yahoo! provider.
Applying the correct settings was enough to normalize everything.
BTW, I found this thread mentioning that Google’s MX servers changed was made about 10 years ago.
