[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

Problem now that we've updated our PTR records

Posted on 2011-09-20
2
Medium Priority
?
278 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 7

Expert Comment

by:mmaris
ID: 36569321
0
 
LVL 21

Accepted Solution

by:
Papertrip earned 2000 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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

How to deal with a specific error when using the Enable-RemoteMailbox cmdlet to create a mailbox in the cloud-based service, for an existing user in an on-premises Active Directory.
Here in this article, you will get a step by step guidance on how to restore an Exchange database to a recovery database. Get a brief on Recovery Database and how it can be used to restore Exchange database in this section!
Established in 1997, Technology Architects has become one of the most reputable technology solutions companies in the country. TA have been providing businesses with cost effective state-of-the-art solutions and unparalleled service that is designed…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses

656 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