Continued Problems with People Blocking our Domain after a PTR record Change
Posted on 2011-09-27
We changed a PTR record because reverse lookups were failing with a supplier we were trying to contact in China. (Their mail server required our PTR records were what the HELO/EHLO message on the server was or else the mail was rejected). Since we've done this we've had a lot of problems with getting emails rejected from other companies (now mostly in the states).
Our internal domain is "domain.lcl" while our email addresses all originate from a "domain-global.com" namespace. The HELO/EHLO message and the PTR record of the external IP of our outbound mail traffic is set "emailserver.aimco.lcl".
I'm thinking that even though this PTR record was set to some random Comcast info prior to us changing it is there SPAM solutions out there? For example I found that BigFish (a maker of a rather cheap looking SPAM filtering solution was blocking us as a SPAMer).
How do others prevent changes to their PTR records from wrecking havok on their email flows? I've also noticed that my SPF record for our domain isn't setup properly, and that's something I'm working on; but, how many people's email solutions are using SPF record lookups? Seems redundant to the PTR record, in a way, but better because it doesn't get botched if you change IP addresses.
Any advice people have would be appreciated.