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

Your message did not reach some or all of the intended recipients.

We've been trying to send e-mail to a client in FLA. from our office in CA and get the following bouncback every time. it only happens with this client. Our domain is not blacklisted anywhere that I can see and when I tracert to their mail server I get the results in the attached screenshot.  All our servers DNS point to our two domain controllers. Our domain controllers point to themselves in the TCP IP properties of the nic cards but the DNS settings in admin tools of the DC's point to DNS servers of ISP.

Can anyone please help with this?


Your message did not reach some or all of the intended recipients.

      Subject:             e-mailing through hotmail
      Sent:                 11/11/2008 8:38 AM

The following recipient(s) could not be reached:

      user@receivingdomain.com on 11/13/2008 8:51 AM
            Could not deliver the message in the time limit specified.  Please retry or contact your administrator.
            <oursendingdomain.com #4.4.7>

tracert.jpg
0
ekitech
Asked:
ekitech
  • 8
  • 3
  • 3
  • +1
1 Solution
 
war1Commented:
Hello ekitech,

Check if recipient's account is full or blocking you.  Ask sender to put you on Safe Sender list or whitelist.

Hope this helps!
war1
0
 
ekitechAuthor Commented:
Hey thanks for your reply. They have already checked their barracuda we are listed as a safe sender.

Thanks again,
0
 
hodgeyohnCommented:
can you telnet to port 25 to thier mail server.  it is possible to test internet email in this way.
it would be a start.
i would test it via both fqdn, and ip address.
0
Microsoft Certification Exam 74-409

Veeam® is happy to provide the Microsoft community with a study guide prepared by MVP and MCT, Orin Thomas. This guide will take you through each of the exam objectives, helping you to prepare for and pass the examination.

 
ekitechAuthor Commented:
when I telnet using a fqdn i get a blank screen for about 30 seconds until my cmd prompt comes back. If I use their IP address I get:  " 220 *********************************************** " for about 30 seconds until my cmd prompt comes back. A also niticed that I can't get to their web site either unless I go throught a web proxy (hidemyass.com), does that help you help me?

...Thanks
0
 
hodgeyohnCommented:
a little.  this is why you are having issues.  it is either your firewall (probably not), or your isp.  i would start with them.  explain the issue to your isp, and they should be able to help you get there.
0
 
ekitechAuthor Commented:
Thanks again. Just a quick question: how can it be a problem with my firewall or even my ISP when the conection fails 17 hopes down the road on the trace route that is practically at it's destination in tampa?

Thanks,
0
 
hodgeyohnCommented:
is it probalby not the firewall, but if it were introducing latency it could cause a timeout down the road.
it may or may not be your isp, but it is somewhere between you and the destination.
the only way to engage on this is thru your ISP.
0
 
tntmaxCommented:
smtpdiag is a great tool that can help you find out where you are failing.

http://www.microsoft.com/downloads/details.aspx?familyid=bc1881c7-925d-4a29-bd42-71e8563c80a9&displaylang=en

Very useful in a number of situations, such as this one.
0
 
ekitechAuthor Commented:
Ok, one thing i did was set up an smtp connector on my exchange to route the e-mails through my isp's mail servers and as soon as I did that the e-mail queue cleared all the held e-mails.  Now I need to check an confirm this solved the problem but the party at the other end is not in today to reply to my e-mails ...if they got them.
0
 
tntmaxCommented:
do you have a reverse dns entry on your external IP address? does mail.<domain name>.com resolve to the IP address that you are sending email from? Of course, if you are smart hosting, this won't matter.
0
 
ekitechAuthor Commented:
0
 
ekitechAuthor Commented:
Thanks for everyones help though and thank you tntmax for that helpful tool it tells me that the receiving domain has a problem with the servers hosting their MX records.
0
 
ekitechAuthor Commented:
NEW DEVELOPMENT: Today I started getting reports that a lot of our users e-mails were not getting to their destination and so I jumped onto the exchange server and noticed that re-routing my e-mail through my ISP worked for a little while but now everything was starting to get backed up. I knew there would be a problem somewhere down the line since routing e-mail through the ISP email server we would be subject to whatever filtering they do. As soon as I removed the SMTP Connecter I had created to re-route traffic everything slowly came back to normal. So, What I thought had worked actually caused another problem. Now, tntmax, brought my attention to the tool smtpdiad which I ran and discovered that the problem is somewhere with the servers that hosts our clients MX record, chances are they also host thier web site too that is why we cant access that either, unless we use a mail proxy (hidemyass.com). All this is also supported by the tracert too. So tntmax gets the points for helping my find the problem.

Thanks,
0
 
ekitechAuthor Commented:
The tool tntmax recommended helped me narrow down the problem to our clients MX (mail exchange) record.
0
 
tntmaxCommented:
thanks for the points :-) that little tool has been very helpful. Glad you got it sorted out.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 8
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now