Problem now that we've updated our PTR records
Posted on 2011-09-20
We, for as far back as I'm aware (5 years) never had our reverse lookups for our mail server setup. It was simply going out the default IP address of our external block of IPs and the PTR record was mapped to the default Comcast value. We since changed our outbound mail flow to another IP and updated the PTR record of Comcast to match the HELO/EHLO value (for some clients in China would were using reverse lookups as the poor man's SPAM filter which it is) we've had problems with other customers (mostly in the USA) that are now rejecting our emails because it looks like our PTR records no longer match what they used to be.
This is why I didn't want to touch this in the first place. Where fixing something causes other people's systems to 'break' to which you can do nothing about....?
Well, that's why I'm posting this. Is there anyway to hasten or mitigate the problems that these occasional external customers are now having? Any global way I can make these changes?
I'm assuming no, but please inform me of whatever you guys are aware of; including how long you think it'll take before these problems go away? When people setup their mail servers to cache PTR records is there a time limit on that cache?
I certainly hope so, or else I'm going to have to be contacting a lot of various IT departments from all these companies.