• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3057
  • Last Modified:

Connected to 69.46.98.90 but sender was rejected. Remote host said: 451 4.4.0 DNS temporary failure

Hi,

we are trying to email parkinson-swor.ca using the rogers.ca Mail Relay.

we are getting a bounced message:

"Connected to 69.46.98.90 but sender was rejected.
Remote host said: 451 4.4.0 DNS temporary failure (chkuser) I'm not going to try again; this message has been in the queue too long."


The following is the tracert from my side;


C:\Documents and Settings\Administrator>tracert parkinson-swor.ca

Tracing route to parkinson-swor.ca [69.46.98.6]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  isa2k4.parkinson.ca [10.10.250.1]
  2     6 ms     5 ms     7 ms  10.29.32.1
  3     7 ms     *        8 ms  vl-201.gw03.ym.phub.net.cable.rogers.com [66.185.90.17]
  4     8 ms    27 ms     7 ms  te-15-1-0.gw01.ym.phub.net.cable.rogers.com [24.153.5.37]
  5     6 ms     7 ms     7 ms  so-1-2-0.gw02.ym.phub.net.cable.rogers.com [24.153.5.242]
  6    48 ms    52 ms    47 ms  pos-3-0.igw01.chfdrl.phub.net.cable.rogers.com [66.185.81.1]
  7    48 ms    55 ms    47 ms  so-0-2-2.mpr1.ord2.us.above.net [64.124.11.25]
  8    48 ms    49 ms    68 ms  so-3-0-0.mpr2.ord7.us.above.net [64.125.30.145]
  9    50 ms    38 ms    37 ms  64.124.17.13.rtr.t186.q9networks.com [64.124.17.13]
 10    40 ms    37 ms    35 ms  chgr31-pos-bgr11.q9.net [65.110.160.37]
 11    37 ms    45 ms    35 ms  dist1-1.brm1-f2.q9.net [74.200.14.35]
 12    41 ms    40 ms    35 ms  dist1-1-g-acess1-2.brm1.q9.net [74.200.14.70]
 13    38 ms    35 ms    36 ms  6.98.46-69.static.nerdsonsite.com [69.46.98.6]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *    



Would it be correct to say that their is a problem connecting to them after [69.46.98.6] - i.e one of their internal servers / routing or a firewall or some rule is a problem?

thx
0
melu
Asked:
melu
  • 5
  • 5
1 Solution
 
LeeDerbyshireCommented:
Try your own IP address here, and see if you're on any blacklists:
http://www.robtex.com/rbl.html
0
 
meluAuthor Commented:
Seems fine. We are not blacklisted.

Also please see the results of the telnet:

C:\Documents and Settings\Administrator>telnet mx01.nerdsonsite.com 25

220 mailscan1-0.nerdsonsite.com ESMTP
helo
mail from : <myName@domain.com>
451 4.4.0 DNS temporary failure (chkuser)
0
 
LeeDerbyshireCommented:
My telnet from here returned OK .  Try a DNS Report test on your domain name here;
http://member.dnsstuff.com/pages/dnsreport.php
0
Independent Software Vendors: 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!

 
meluAuthor Commented:
Can you please see the report

http://www.box.net/shared/sdyc0m3ujn


For security reasons - I dont want to reveal the domain name [here].

thanks
0
 
LeeDerbyshireCommented:
I would guess that the 'Mail server host name in greeting' warning is the most significant here.  Have a look at the properties of your Default SMTP Virtual Server, and enter the name 'mail1.parkinson.ca' as the Fully-Qualified Domain Name.
0
 
meluAuthor Commented:
Hi,

I have corrected the 'Mail server host name in greeting' warning.

I am still not able to resolve that error. Any idea what could be causing the problem?

Thanks

0
 
LeeDerbyshireCommented:
Well, that seemed the most obvious to me, but I guess it's time to work through the other failed items.  The error message
451 4.4.0 DNS temporary failure (chkuser)
does seem to suggest a DNS problem, and you had a lot more fails and warnings than I would have expected.  Trouble is, I don't know what most of them mean, and I think only your ISP (assuming they are your DNS provider) can fix them.
0
 
meluAuthor Commented:
Interesting thought.

The ISP is rogers..ca - and the DNS provider is upscalehost

They are not the same.

But, we dont have any problems sending to anyone else apart from this one organisation
0
 
LeeDerbyshireCommented:
Actually, it doesn't matter that they're not the same, but they often are.  I was suggesting that they might be your best point of contact for DNS issues.

This organization might do more DNS checking than most.  Some admins enforce rigorous domain DNS checking to combat spam.  The obvious risk is that they will lose some valid emails without even knowing about it.
0
 
meluAuthor Commented:
Thanks!
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 5
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now