tc6atim
asked on
SBS 2008 Craigslist bounces e-mails with rDNS issue
Network Background
Domain A registered with Godaddy, authorative DNS is with GoDaddy
Domain B registered with Godaddy, authroative DNS is with Peplink at our office
Domain a has several cname entries remote, ftp, etc that point to domain B. This way if either of our ISP's go down we still have service.
If the peplink goes down, our web page still works since DNS is with Godaddy
rDNS is properly configured on our ISP for remote.domaina.com and SPF is configured for domain a
Issue is with sending mail from our SBS 2008 mail server to craigslist. Research into the problem suggest the mail is being rejected by craiglist because our internal fqdn for the server and its ip address appear in message headers. The resolution seems to be to add a transport rule to remove message headers, but this seems extreme to me.
I've also read that this is customary for every mail server so I doubt that is the problem or else craigslist would be recieving thousands of complaints. Keep in mind I can send mail to msn, aol, google with no problems. So my thought is craiglist must be choking on my cname of remote.domaina.com pointing to remote.domainb.com
My work around is to clear the cname entry and use the hosts in Godaddy usually used for name servers to make an entry for remote. In IP 1 is ISP a and IP 2 is ISP b. My hope is if ISP a goes down the next Ip in the host record will work. As I'm waiting to test this out I though I would see if anyone has a better solution.
Domain A registered with Godaddy, authorative DNS is with GoDaddy
Domain B registered with Godaddy, authroative DNS is with Peplink at our office
Domain a has several cname entries remote, ftp, etc that point to domain B. This way if either of our ISP's go down we still have service.
If the peplink goes down, our web page still works since DNS is with Godaddy
rDNS is properly configured on our ISP for remote.domaina.com and SPF is configured for domain a
Issue is with sending mail from our SBS 2008 mail server to craigslist. Research into the problem suggest the mail is being rejected by craiglist because our internal fqdn for the server and its ip address appear in message headers. The resolution seems to be to add a transport rule to remove message headers, but this seems extreme to me.
I've also read that this is customary for every mail server so I doubt that is the problem or else craigslist would be recieving thousands of complaints. Keep in mind I can send mail to msn, aol, google with no problems. So my thought is craiglist must be choking on my cname of remote.domaina.com pointing to remote.domainb.com
My work around is to clear the cname entry and use the hosts in Godaddy usually used for name servers to make an entry for remote. In IP 1 is ISP a and IP 2 is ISP b. My hope is if ISP a goes down the next Ip in the host record will work. As I'm waiting to test this out I though I would see if anyone has a better solution.
ASKER
That is already configured.
However headers still show the internal fqdn. I've researched this issue and found this thread
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/b28cf60c-967b-429a-9279-a6b9ca088513
When I run >get-sendconnector | fl , the correct external fqdn shows. Further down in the thread it is discussed that even when this setting is correct the internal server and IP are kept in the message header. It is suggested to remove message headers but this does not solve mail bounces from craigslist.
The probelm I have is that I have not found any documentatoin on the steps craiglist takes to actually check rDNS and what it compares. Does it compare rDNS values to a records or MX records or both?
However headers still show the internal fqdn. I've researched this issue and found this thread
http://social.technet.microsoft.com/Forums/en-US/exchangesvradmin/thread/b28cf60c-967b-429a-9279-a6b9ca088513
When I run >get-sendconnector | fl , the correct external fqdn shows. Further down in the thread it is discussed that even when this setting is correct the internal server and IP are kept in the message header. It is suggested to remove message headers but this does not solve mail bounces from craigslist.
The probelm I have is that I have not found any documentatoin on the steps craiglist takes to actually check rDNS and what it compares. Does it compare rDNS values to a records or MX records or both?
ASKER
Diagnostic information for administrators:
Generating server: SERVER.onsite.local
gigs-knyng-1554543753@crai gslist.org
mxi3p.craigslist.org #554 5.7.1 <unknown[75.149.32.97]>: Client host rejected: rDNS/DNS_validation_failed ._Please_s etup_match ing_DNS_an d_rDNS_rec ords:_http://www.craigslist.org/about/help/rdns_failure xabd-4 ##
Original message headers:
Received: from SERVER.onsite.local ([fe80::f4b9:e645:ea3:dd06 ]) by
SERVER.onsite.local ([fe80::f4b9:e645:ea3:dd06 %14]) with mapi; Sun, 17 Jan
2010 11:18:35 -0800
Generating server: SERVER.onsite.local
gigs-knyng-1554543753@crai
mxi3p.craigslist.org #554 5.7.1 <unknown[75.149.32.97]>: Client host rejected: rDNS/DNS_validation_failed
Original message headers:
Received: from SERVER.onsite.local ([fe80::f4b9:e645:ea3:dd06
SERVER.onsite.local ([fe80::f4b9:e645:ea3:dd06
2010 11:18:35 -0800
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It should match your rDNS record.
In Exchange Management Console navigate to Organisation Configuration > Hub Transport > Send Connector.
Under the properties of the send connector the first tab provided the FQDN.
Change this to match your rDNS