Solved

Messages staying in "unreachable destination"

Posted on 2004-04-29
8
803 Views
Last Modified: 2013-11-15
Hi,

We appear to be having a bit of an issue with our Exchange 2000 server. All of a sudden messages are not going form our exchange server to our relay server. They are sitting in microsoft Exchange queue under "unreachable destination".

If the server is rebooted then this allows for the messages to go through. but it appears to stop again at a random period of time later. There appears to be nothing changed on either the Exchange system or the relay server in the DMZ.

Anyone else experienced this or have any ideas of what i can do to try and fix it?

0
Comment
Question by:monkeyspunk
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
8 Comments
 
LVL 4

Expert Comment

by:knikkij
ID: 11026847
Have you recently performed an upgrade or migration?

If you enumerate the messages in the "unreachable destination" queue and open one up, what is the address that it is trying to send the email to?    This is of key importance!

I've seen the same problem many times - let me know what you find in the queue.
0
 

Author Comment

by:monkeyspunk
ID: 11039131
Hi,
knikkij - Its somewhat of an odd one, as appears to be any messages, Ive enumerated them and it doesnt appear to be one destination which is quite odd, as that was what i thought was the problem.

As for upgrade or migrations, there has been no major upgrades or migrations done as such, however some security fixes were installed on the relay that Exchange server forwards all mail to.

The "problem" I have now is that the server seems to be fine at the minute. It has not had this problem for just under a week now, and the only thing i can thing of is that I applied some security fixes to the exchange box to bring it inline with the relay server. Now that I can't replicate the problem it's hard to further diagnose, but Ive switched on lots of logging for the smtp engine amongst other things to try and give me some more diagnostic capabilities should it go again.

Any further ideas on what could have caused it to get into that routine?

Many Thanks
0
 
LVL 4

Expert Comment

by:knikkij
ID: 11039833
We had some major major issues after someone ran the IIS Lockdown / URLScan utility on the Exchange server that took us eighteen hours with Microsoft to correct.  That's a nasty little tool - and I'm convinced the URLScan was secretly snuck into a security rollup - but that may just be the conspirator in me.

Messages unreachable (obviously) means it's an invalid address.  We see this often after migrating users from 5.5 to 2000 when people reply to old 5.5 addresses (that's when you see IMCEA in the message destination).

When you looked at the messages in the queue, however, they did look like valid SMTP addresses, correct?  Were they internal or external or both?

Can you look up and see which security patches you applied on the Exchange server?  I think it would be marvelous to figure out the root cause on this one.
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!

 

Author Comment

by:monkeyspunk
ID: 11039911
Hi knikkij,

The messages that get stuck are just for outbound messages, which is what made it even stranger all internal mail traffice was still working fine. As for the messages, they did all seem to contain valid addresses and most of them i could trace to people that we are regularly in contact with.

However what i did notice only once, out of the several times the messages got stuck was that there were two messages that didnt appear to have any destination?!? Now whether they were there at all times and it only enumerated enough to show me the first 100 that had got to the queue or not i don't know.

As for the patches I will have a look and see which ones were applied and the fact that since then it appears to be ok.
0
 
LVL 4

Expert Comment

by:knikkij
ID: 11211294
Problem appears to have been resolved after the author updated the service packs on the relay server - beyond that we didn't find any major configuration errors.
0
 
LVL 5

Accepted Solution

by:
Netminder earned 0 total points
ID: 11337789
PAQed, with points refunded (125)

Netminder
EE Admin
0

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Lotus Notes – formerly IBM Notes – is an email client application, while IBM Domino (earlier Lotus Domino) is an email server. The client possesses a set of features that are even more advanced as compared to that of Outlook. Likewise, IBM Domino is…
Developer portfolios can be a bit of an enigma—how do you present yourself to employers without burying them in lines of code?  A modern portfolio is more than just work samples, it’s also a statement of how you work.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
This is used to tweak the memory usage for your computer, it is used for servers more so than workstations but just be careful editing registry settings as it may cause irreversible results. I hold no responsibility for anything you do to the regist…

739 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question