Unroutable domain - some domains not others

[Cloak]

I'm having a heck of a time with this, it has issues for some domains and not others, all on the same machine.

Currently running: WHM 8.5.4 cPanel 8.5.5-R60

I can't receive anything at all to this email address (or any others on this domain). It worked before I manually upgraded to Release. I've tried downgrading to Stable with no sucess.

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:

cloak@isnot.ws
Unrouteable address

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

Return-path: <cloak@comi.cx>
Received: from [68.35.26.92] (helo=CLOAK)
by lister.go-dedicated.com with asmtp (TLSv1:RC4-MD5:128)
(Exim 4.24)
id 1AgD63-0004O4-Su
for cloak@isnot.ws; Mon, 12 Jan 2004 18:11:56 -0700
From: "Cloak" <cloak@comi.cx>
To: "'Cloak'" <cloak@isnot.ws>
Subject: test
Date: Mon, 12 Jan 2004 18:11:56 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_NextPart_000_0039_01C3D937.90EBD870"
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcPZcjzQE5SrFlfXSHeyrF4Rd+1BuQ==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-Id: <E1AgD63-0004O4-Su@lister.go-dedicated.com>

This is a multi-part message in MIME format.

[casey]

You've got some dns issues.
http://www.dnsreport.com/tools/dnsre...omain=isnot.ws

Mail is probably not being delivered due to the lack of a reverse dns record for the mailserver ip.

[Cloak]

Originally posted by casey
You've got some dns issues.
http://www.dnsreport.com/tools/dnsre...omain=isnot.ws

Mail is probably not being delivered due to the lack of a reverse dns record for the mailserver ip.

I understand about the reverse dns, but that makes no sense as the other domain which was sent to works perfectly fine, along with the 60 or so other domains that receive email at that IP.

Like I said before, there are other domains which are not working that were previously, something about the update has messed things up.

[casey]

I'd be willing to wager that if you fix the dns issues e-mail will function properly.

[Cloak]

I'm waiting on the reverse dns now, I've checked the other issues and changed them around a bit (except for the 0 TTL).

Still makes no sense that would be the issue and it has worked fine for months with no issues, then suddenly today it has problems sending between my 2 machines.

[casey]

I just noticed that your mx record appears wrong, too. Check your mx entry in the dns record and make sure there is a . at the end of the domain.

[casey]

DNS looks okay now. Mail working?

[Radio_Head]

same problem here on red hat 7.2 Progeny.

from 3 weeks one of my clients sending out a mailing list
to 300 email contacts . 200 of 300 bounce back (unroutable mail domain)

it is using this perl script

#!/usr/bin/perl -w 

use DBI; 
use MIME::Lite; 
use CGI qw(:all); 

my $q = new CGI; 

# snipped a bunch of unrelated "session" stuff here 

print $q->header(); 
my $subname = $q->param('send_subname'); # set sender name 
my $subject = $q->param('mail_subject'); # set subject 
my $message = $q->param('mail_message'); # build message 
my $sender = ""; # initialize sender 

if ($subname eq "Credit Daily Business News Report") { 
$sender = "dailybusiness@domain.com"; 
} 
elsif ($subname eq "U.S. Business Journal") { 
$sender = "usbz@domain.com"; 
} 

## THIS IS THE BAD BOY THAT'S BOUNCING EVERYTHING ## 

elsif ($subname eq "Creditors Edge") { 
$sender = "crededge@domain.com"; 
} 

######################################################## 
else { 
$sender = "info@domain.com"; 
} 

my $email = ""; 

print "Sending mail to list $subname

"; 

my $dbh = DBI->connect("DBI:mysql:cred_usbz:localhost","cred","99999") or die "Could not connect to DB: $!"; 
my $sth = $dbh->prepare("SELECT EmailAddress, SubscriptionName FROM UserData WHERE SubscriptionName = ?"); 
$sth->execute($subname); 
while (($email,$subname) = $sth->fetchrow_array()) { 
my $msg = MIME::Lite->new( 
From =>$sender, 
To =>$email, 
Subject =>$subject, 
Data =>$message, 
Type =>'text/plain', 
); 
$msg->send(); 
print "Sent message to $email
"; 
} 

$sth->finish(); 
$dbh->disconnect(); 

print <
Message delivered. 
END_OF_HTML 

[Cloak]

Originally posted by casey
DNS looks okay now. Mail working?

My mx record was fine, I'm not sure where you were reading from showing they were wrong.

I had to edit the domainalias file, it had the wrong user account for the domain. That fixed the one domain, but now I"m having others pop up with errors (infact one this morning I'm trying to track down that is bouncing with the error:

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

That's the full error from hotmail.

I'm still having problems where I'm getting some bounced emails with no reason given, these are ones that were transferred over from another server.

Edit: Ran /scripts/mailperm and that fixed this account.

[Creazioni1]

Some customer have same problem with mailing list
Send mailing list to 500 email
Receive error with
unrouteable mail domain "hotmail.com
unrouteable mail domain "inwind.it
unrouteable mail domain "tin.it

if send mail with outlook, ahve no problem

[wipl_piyush]

Hello ,

Please check that u must have the entry of the domain in the /etc/localdomains file . Also check that i you have the domain in the /etc/remotedomian file remove them from there. I think this will solve the issue.

[phantom2]

Originally posted by Cloak
I understand about the reverse dns, but that makes no sense as the other domain which was sent to works perfectly fine, along with the 60 or so other domains that receive email at that IP.

Like I said before, there are other domains which are not working that were previously, something about the update has messed things up.

The reason it worked before and not now is more than likely because the ISP the mail is being sent to decided to make reverse DNS a requirement in order for mail to be delivered though their mail servers. Eventually, everybody is going to do it. The only way around it a person using that ISP emails you and you can then respond to them.

Hope this clears this up for you. Ask your datacenter to set up reverse DNS for you.

[AlaskanWolf]

this *isnt* a Rdns issue. We are having the exact problem with one of our servers, what caused it is a reformat/restore of the server. Some sites are getting emails, others are not.