I know you can set it up but it's alot of work to do it for every domain on the servers.
Not it's little work because it's not needed for every domain on the servers. You only need 1 PTR record per server and that is to the hostname your server is sending email from. Not for every domain.
Suppose your hostname is server3.provider.com with ip 82.82.44.44 and your domain is dutchprogrammer.nl then mail is send from server3.provider.com for you because dutchprogrammer.nl is hosted on that server and not sending out mail itself.
So the helo will also be helo server3.provider.com everywhere.
In the datacenter (or the control panel of the provider who provides ip 82.82.44.44 for you), put in the PTR record like this:
RDNS 82.82.44.44 -> server3.provider.com
and you're done for all domains on the server.
I checked your link on my email addres.
As said in DA itself we don't use any PTR records and my domain is als hosted on a server with another domain name as the name of my company. The only issue the test is giving me is:
"Cert NOT VALIDATED: self signed certificate" The rest is 100%.
And I also got " Recipient OK, E-mail address proofed.
So you don't need a ptr for every domain name. And we never have issues delivering mail to hotmail or gmail on any server.
To be sure I tested again by sending a mail from an email adres to my gmail account which does not have any accounts whitelisted. I don't get any question mark.
Even stronger. If you are going to use PTR records for multiple domains on the same server, then you will get issues. Because in that case, you will declare that ip 82.82.44.44 is pointing to xx different domains on a server, which is suspecious to spamfilters because mail is still being send from "server3.provider.com" and not from mail.dutchprogrammer.nl or any other domain on the server.
Believe me, PTR records are to identify the hostname that is associated with the ip address sending the helo/ehlo, NOT any domain name not sending the ehlo.