Discussion:
exchange server 2000 problems
(too old to reply)
wjr
2008-12-17 21:43:42 UTC
Permalink
We have a windows 2000 server running exchange server 2000. Very
recently several of our users have been reporting problems sending
emails. They are getting two types of problems.

type 1) Delivery Status Notification (Delay).
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.

Reporting-MTA: dns;winserver.monarchw.com
Final-Recipient: rfc822;***@adelphia.net
Action: delayed
Status: 4.4.7
Will-Retry-Until: Thu, 18 Dec 2008 16:08:12 -0800


Type 2) Undeliverable
Your message did not reach some or all of the intended recipients.
Subject: *sanitzied* //by me
Sent: 12/15/2008 9:58 AM
The following recipient(s) could not be reached:
Keith Nixon on 12/17/2008 10:04 AM //this user is an employee.
Could not deliver the message in the time limit specified.
Please retry or contact your administrator.
<winserver.monarchw.com #4.4.7>


To continue, our DNS is ok and MX records are all correct. Well,
according to network solutions.

Our regular users are using the exchange server. But myself and another
developer have solaris systems running sendmail, which are not
connecting to the exchange server for anything. Outgoing emails are
working perfectly on these solaris systems.

http://support.microsoft.com/kb/257265 suggests diagnostic logging. But
when I got to check logging level, none of the options are available.
Any ideas what is preventing this?


Is there a tool to verify that exchange doesn't have any corrupted db files?
PM
2008-12-23 12:23:52 UTC
Permalink
Post by wjr
Is there a tool to verify that exchange doesn't have any corrupted db files?
Use eseutil to check the db files. There is a lot of good documentation on
this to help you.

Loading...