Mail delivery to Craigslist fails

nealdxmhost

Verified User
Joined
Jan 1, 2009
Messages
232
Location
Los Angeles CA
This is the synopsis of what I am getting when I send an email to an ad on Craiglist through my server and I have been hearing this from few of my customers as well. Needless to say I am wondering what I am missing or doing wrong....

Code:
This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  [email protected]
    SMTP error from remote mail server after RCPT TO:<[email protected]>:
    host mxi5p.craigslist.org [208.82.236.165]: 554 5.7.1 <unknown[74.124.206.98]>:
    Client host rejected: rDNS/DNS_validation_failed._Please_setup_matching_DNS_and_rDNS_records:_http://www.craigslist.org/about/help/rdns_failure xabd-4

------ This is a copy of the message, including all the headers. ------

Return-path: <[email protected]>
Received: from 71-95-193-79.dhcp.mtpk.ca.charter.com ([71.95.193.79] helo=[192.168.1.2])
    by cp.dxmhosting.com with esmtpsa (TLSv1:AES256-SHA:256)
    (Exim 4.72)
    (envelope-from <[email protected]>)
    id 1OxUNJ-0003z3-4S
    for [email protected]; Sun, 19 Sep 2010 17:36:53 -0700
Message-ID: <[email protected]>
Date: Sun, 19 Sep 2010 17:37:04 -0700
From: The Portly Irishman <[email protected]>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.9) Gecko/20100915 Thunderbird/3.1.4
MIME-Version: 1.0
To: [email protected]
Subject: Professional Wordpress Web Design (Woodland hills)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
 
The ip 74.124.206.98 points to www.dxmhosting.com
The domain www.dxmhosting.com points to ip 74.124.204.2

Craigslist wants them to be the same ip.

I am guessing that you have both of the ip's on the same machine. Really the .98 ip should point back to the hostname of the machine which should NOT be www.dxmhosting.com but should be perhaps server.dxmhosting.com. And the hostname server.dxmhosting.com should point to the .98.

Think of it like a telephone number. 555-111-2222 reverses to your home but your home number is actually 555-222-3333. The records are incorrect and so it looks like you are trying to fake your phone number or location.
 
The ip 74.124.206.98 points to www.dxmhosting.com
The domain www.dxmhosting.com points to ip 74.124.204.2

Craigslist wants them to be the same ip.

I am guessing that you have both of the ip's on the same machine. Really the .98 ip should point back to the hostname of the machine which should NOT be www.dxmhosting.com but should be perhaps server.dxmhosting.com. And the hostname server.dxmhosting.com should point to the .98.
Thanks for pointing that out to me Floyd, while that makes things a little bit clearer for when I run this command I get this result;
Code:
[root@cp ~]# hostname
cp.dxmhosting.com

Think of it like a telephone number. 555-111-2222 reverses to your home but your home number is actually 555-222-3333. The records are incorrect and so it looks like you are trying to fake your phone number or location.

So now what should I do to fix this? Any ideas????
 
You need to create an A record for cp.dxmhosting.com pointing to the server's main ip which I am guessing is 74.124.206.98

The reverse dns need to point 74.124.206.98 to cp.dxmhosting.com.
 
You need to create an A record for cp.dxmhosting.com pointing to the server's main ip which I am guessing is 74.124.206.98

The reverse dns need to point 74.124.206.98 to cp.dxmhosting.com.

Tried "cp.dxmhosting.com." pointing to 74.124.206.98 as an A Record and it failed however if do just the cp it goes through. Will this need to be done across the board with ALL of the hosting accounts?
 
Will this need to be done across the board with ALL of the hosting accounts?

I don't understand the question. There is only one zone file for dxmhosting.com. There is only one hostname. There can be only one PTR record for the ip address.
 
Tried "cp.dxmhosting.com." pointing to 74.124.206.98 as an A Record

You just need to go to your domain dxmhosting.com, and make the dns record as a subdomain in DNS management: "cp A 74.124.206.98"

And like floyd says, its server wide. All your e-mail is being sent from one IP address - that address just needs a matching DNS/rDNS record.

Question from me: Does the main IP address really needs to point to the servers' hostname?
 
You just need to go to your domain dxmhosting.com, and make the dns record as a subdomain in DNS management: "cp A 74.124.206.98"

He already did that.

Question from me: Does the main IP address really needs to point to the servers' hostname?

According to the craigslist error the answer is yes. It is also the proper thing to do.
 
The hostname ip should actually be set when you set the hostname from within DirectAdmin.
 
I added it from the Admin section this time, before I had done it at the user level which I presume was my error when trying to do it.

This time I also did the reverse DNS as well (hopefully I got it right).

Anyhow this is the entry:
Code:
cp.dxmhosting.com.    A    74.124.206.98    
98.206.124.74.in-addr.arpa.    NS    na1.dxmhosting.com.    
98.206.124.74.in-addr.arpa.    NS    ns2.dxmhosting.com.    
98.206.124.74.in-addr.arpa.    PTR    cp.dxmhosting.com.

And if I got it right this time I presume it will take a little while for it all to propagate or do I need to advise my upstream provider to do something at their end as well?
 
Last edited:
When I query your dns server directly it gives the correct information. You have to wait now for other dns servers to clear their cache.
 
When I query your dns server directly it gives the correct information. You have to wait now for other dns servers to clear their cache.
Thanks for the tip Floyd now I just got to sit and wait for all of the other DNS servers to do their thing I guess and if you ever make it out to LA look me up and I will buy you a beer LOL
 
Last edited:
@nealdxmhost:

You don't host your rDNS; you upstream does. They've not allocated it to you. You can ask them to allocate it to you, in which case your PTR setting may work. Or you can ask them to change the rDNS for 74.124.206.98 to cp.dxmhosting.com.

Best bet: call William (you know who I mean).

Jeff
 
@nealdxmhost:

You don't host your rDNS; you upstream does. They've not allocated it to you. You can ask them to allocate it to you, in which case your PTR setting may work. Or you can ask them to change the rDNS for 74.124.206.98 to cp.dxmhosting.com.

Best bet: call William (you know who I mean).

Jeff
Thanks Jeff,

I just shot an email off to William right now about that

Neal

Once I get through this then I will be working on all of the other little bugaboos that I have procrastinated on.
 
@nealdxmhost:

You don't host your rDNS; you upstream does. They've not allocated it to you. You can ask them to allocate it to you, in which case your PTR setting may work. Or you can ask them to change the rDNS for 74.124.206.98 to cp.dxmhosting.com.

Best bet: call William (you know who I mean).

Jeff
On another note Jeff, should I go ahead and pull out the PTR records that I put in?
 
Floyd is right; leaving them there won't matter because they'll never be used. But for that reason I'd remove them to avoid confusion in a year or three.

Jeff
 
Floyd is right; leaving them there won't matter because they'll never be used. But for that reason I'd remove them to avoid confusion in a year or three.

Jeff

OK I took out the PTR record but I got one more question LOL

Code:
98.206.124.74.in-addr.arpa.    NS    na1.dxmhosting.com.    
98.206.124.74.in-addr.arpa.    NS    ns2.dxmhosting.com.

Should I take those out as well or leave them alone
 
Take them out.

Take out the entire rDNS zone file(s).

And while you're at it, is na1 right, or is that a typo? Make sure it's right everywhere it needs to be or it's causing problems.

Jeff
 
Take them out.

Take out the entire rDNS zone file(s).

And while you're at it, is na1 right, or is that a typo? Make sure it's right everywhere it needs to be or it's causing problems.

Jeff

I am glad you spotted that, it was typo on my part when I created the original record.

I took the whole entry out and created a new one with the following;
Code:
cp.dxmhosting.com.    A    74.124.206.98    
ftp    A    74.124.206.98    
localhost    A    127.0.0.1    
mail    A    74.124.206.98    
pop    A    74.124.206.98    
smtp    A    74.124.206.98    
www    A    74.124.206.98    
cp.dxmhosting.com.    NS    ns1.dxmhosting.com.    
cp.dxmhosting.com.    NS    ns2.dxmhosting.com.    
mail    MX    10    
cp.dxmhosting.com.    TXT    "v=spf1 a mx ip4:74.124.206.98 ~all"

Hopefully I got it right this time
 
Back
Top