PTR, reverse DNS records for dedicated server

[rodd24]

I have an account with a dedicated IP address. He is having email sometimes be refused by other servers. I want to set up PTR records for this account. How do I add them properly in the account's DNS zone? Specifically, what should the entries look like? Thanks

[Matt]

There is no need for a PTR for the dedicated IP because mail is sent from the hostname, which resolves to the main server IP, so the problem is likely something else.

What sort of bounce messages does he get?

[andychev]

I had a similar problem a while back but due a change in circumstances I never needed it to be resolved. It happens with hotmail and aol address's. They cant do a reverse dns on the ip so reject the message. Try your ip here to confirm this is the problem:

http://postmaster.aol.com/tools/rdns.html

[rodd24]

There is no error message. The emails go out but don't get to the destination or bounce.

[Matt]

If they don't bounce the problem is probably on the recipient mailserver. You should always receive a bounce if the problem is on your end.

Did you check your spam folder(s) to see if the bounce was in there? If its not there, then the best thing to do is to send another email, verify it did not make it, then open a support ticket with the sender and recipient address so we can have a look at the logs.

Make sure you do not wait too long after sending the email / opening a new ticket otherwise the logs we look at may be too old and won't contain the information that we need to troubleshoot the problem.

[charlesh]

I had the same problem with a client whose purchasers would receive a confirmation email with an attachment. The problem was exactly AOL, Hotmail, and Comcast. It seems as though if any email is generated through a script, they recognize that and deny it without any warning. If we were lucky, we'd at least get the emails placed in the spam box, but it wasn't a viable solution. At the time, I looked into SPF records and added a few lines of code to the mail headers, but it didn't help really. So, we elected to go with a download link instead of an attached email.

[rodd24]

This account is having problems again. Email sent to a known address that often gets through is being rejected. Here's the bounce headers. Please advise.

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:

vsanpere@holistika.us
SMTP error from remote mail server after RCPT
TO:<vsanpere@holistika.us>:
host mx1.biz.mail.yahoo.com [67.28.113.136]: 550 relaying denied for
<vsanpere@holistika.us>

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

Return-path: <doug@dougjmoore.com>
Received: from cpe-24-165-165-21.neo.res.rr.com ([24.165.165.21]:1355
helo=Dell)
by hostnet.clevelandwebseo.com with esmtpa (Exim 4.69)
(envelope-from <doug@dougjmoore.com>)
id 1KsrNM-0007iX-BG
for vsanpere@holistika.us; Thu, 23 Oct 2008 00:00:44 -0400
From: "Doug Moore" <doug@dougjmoore.com>
To: "Veronica Sanpere" <vsanpere@holistika.us>
Subject: Skype Students
Date: Thu, 23 Oct 2008 00:00:41 -0400
Message-ID: <002201c934c3$ec417670$c4c46350$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0023_01C934A2.652FD670"
X-Mailer: Microsoft Office Outlook 12.0
thread-index: Ack0w944+tpyIA2FQmuVjNJNxIVHRg==
Content-Language: en-us
x-cr-hashedpuzzle: Aa/r Apy2 BslT CuS3 DDe0 Dzc1 E6l+ FMPv FrDu G2Vw IKSA
IsB7 JINr JsbX KC5l
KzJw;1;dgBzAGEAbgBwAGUAcgBlAEAAaABvAGwAaQBzAHQAaQB rAGEALgB1AHMA;Sosha1_v1;7;
{AFAA8C7C-7228-48FB-A0A6-30936CB3B15E};ZABvAHUAZwBAAGQAbwB1AGcAagBtAG8AbwBy A
GUALgBjAG8AbQA=;Thu, 23 Oct 2008 04:00:20
GMT;UwBrAHkAcABlACAAUwB0AHUAZABlAG4AdABzAA==
x-cr-puzzleid: {AFAA8C7C-7228-48FB-A0A6-30936CB3B15E}

This is a multipart message in MIME format.

------=_NextPart_000_0023_01C934A2.652FD670
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit

[Alexander]

Well, there is no enough information to find the reason of the issue. It can be both problems on recipient's mailserver side and some paranoiac anti-spam settings. Have you tried to contact the recipient's mail server authorities?