Solved

Problem now that we've updated our PTR records

Posted on 2011-09-20
2
273 Views
Last Modified: 2012-05-12
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.
0
Comment
Question by:ChocolateRain
2 Comments
 
LVL 7

Expert Comment

by:mmaris
ID: 36569321
0
 
LVL 21

Accepted Solution

by:
Papertrip earned 500 total points
ID: 36569594
What needs to match are the A record and the PTR record for your sending server.  I wouldn't worry too much about receivers who block on HELO mismatch -- if they are doing that then they are blocking TONS of legitimate mails.  A big "problem" with email delivery is that unless you have a contact on the other end, you can't fix their bad practices.

When people setup their mail servers to cache PTR records is there a time limit on that cache?  
Yes, the TTL value of the PTR record dictates a maximum time the record can be cached.
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

As tax season makes its return, so does the increase in cyber crime and tax refund phishing that comes with it
In-place Upgrading Dirsync to Azure AD Connect
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…
how to add IIS SMTP to handle application/Scanner relays into office 365.

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question