How it does not work now
Here is how it works with the domain name of this forum, webseodesigners.com.
The domain name has a valid SSL certificate.
The domain name points to IP address 22.214.171.124. The Reverse DNS hostname of the IP address is ip-166-62-7-52.ip.secureserver.net.
ip-166-62-7-52.ip.secureserver.net does not have a valid SSL certificate. That is why Gmail is throwing the following error and refusing to use the SMTP server:
How it should have always workedPoople Gmail wrote:TLS Negotiation failed, the certificate doesn't match the host., code: 0
Naturally GoDaddy should have a valid SSL certificate also for the host in their Reverse DNS, or use the same host name they are using with the cPanel that already has a Reverse DNS with valid SSL cerficate:
- For checking Reverse DNS: https://mxtoolbox.com/ReverseLookup.aspx
- For checking SSL certificates: https://www.sslshopper.com/ssl-checker.html
- Solution for GoDaddy shared hosting users
It seems that many hosting companies got surprised and reacted to this like they react to everything: blaming third parties, blaming each other, blaming google and dodging responsibility. Also Poople did very badly doing such a big change with huge impact without informing hosting providers and Gmail users beforehand and giving them time to fix their broken systems.
I hope to find or make something to replace Gmail. For my search needs I am using DuckDuckGo and I wrote my own photo album management system to replace Poople Photos/Picasa.