Title: Strange Delivery Status Notification (Delay) Error - to only one domain

Strange Delivery Status Notification (Delay) Error


I have a rather bizarre issue occurring on a client’s exchange server. The
server is running exchange 2003 with all the latest service packs and
downloads installed. GFI mailessentials is also installed on the server for
spam control.

The company used to host several email domains on this server - - for
simplicity, let’s say it had hosted abc.com, and xyz.com. One of the domains, xyz.com, was
split off the server, and moved to another mail hosting service outside the
organization, but abc.com remained on this server.

After the split, everyone at abc.com was able to email the organization at
xyz.com, and visa versa.

Then, about a week ago, nobody at abc.com could
email anyone at xyz.com anymore. Xyz.com can still send mail into abc.com.

There is no clear explanation for this problem.

1.  Nothing exists in DNS regarding the older xyz.com domain.
2.  I am able to telnet to xyz.com’s new mail server and manually send
mail messages.
3.  They are not on any blocklists.  
4.  The problem occurs with GFI either on or off.
5.  SMTP logging was enabled, and the messages are never recorded in the SMTP log.
6.  We can successfully ping the xyz.com domain.  NSLOOKUP shows the correct mail server IP address for xyz.com.  In other words, this doesn't appear to be a dns issue.
7.  After sending a message to xyz.com, the message sits in the queue. It cannot be forced to connect.  Eventually, they are returned to the sender with this message:

This is an automatically generated Delivery Status Notification.

THIS IS A WARNING MESSAGE ONLY.

YOU DO NOT NEED TO RESEND YOUR MESSAGE.

Delivery to the following recipients has been delayed.

someone@xyz.com

-------------- Then, later, this message ---------------------

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

Subject: test
Sent: 11/3/2006 9:34 AM

The following recipient(s) could not be reached:

someone@xyz.com on 11/3/2006 10:36 AM
Could not deliver the message in the time limit specified.
Please retry or contact your administrator.
<mail.abc.local #4.4.7>


I’m completely stumped here. Any suggestions would be greatly appreciated.
stonenajemAsked:
Who is Participating?
 
VahikConnect With a Mentor Commented:
Sure
in ESM...Routing groups....Connectors
right click on connectors and choose SMTP connectors
give it a nemae....choose a bridgehead server....choose SMART HOST....and put the IP address of server that u
are having problem with( IP address in brackets, do not forget).....
in the Add space section...click add....smtp....and put the domain name of the other company.....leave the cost
1 if this is the only connector...leave everythong else default....
that is all there is to creating a smtp connector....
0
 
VahikCommented:
what happened about a week ago??? any updates?? restart of server??

what if you create an smtp connector and put the ip address of the xyz server in the smart host section (bypassing DNS) and see if u will be successfull..
0
 
stonenajemAuthor Commented:
Nothing happened that I'm aware of.  I'll try a new smtp connector and see what happens.  Do you knowo of a TID that outlines the procedure?
0
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.

 
stonenajemAuthor Commented:
Duh, sorry Vahik, I actually have done this before.  I'll give it a try and let you know what happens.
0
 
stonenajemAuthor Commented:
Vahik, this seems to have worked.  The message wasn't delayed or queued.  So, that indicates the problem is with DNS.  But the question remains, WHERE in DNS?
0
 
VahikCommented:
well only god knows when it comes to DNS..
one time i was troubleshooting an email server (SLMAIL)....those folks had the same problem.....it turned out
COMCASTS dns server had gone capoot.....because we tried the same address having problem from other ISPs and there was no problem.....finally when comcast instructed us to use another dns for our forwarding everything worked..
having said all that ur problem maybe  internal DNS corruption ....or maybe ISP related....u have to figure it out urself..

0
 
stonenajemAuthor Commented:
The Grade of B is an error.  This was supposed to be an A.  Can one of the admins please change?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.