Incoming and Outgoing Messages Stuck in Local Delivery Queue

We experienced a failed drive on our Raid 5 on Friday, and replaced and rebuilt the array.  Everything looked fine, but we soon discovered that were no longer able to receive messages in Outlook.  We were able to send with no errors or bounces, but they too were not reaching their destination.  We're still able to see our public folders and calendars, as well as any existing messages/folders in each respective user's mailbox.

Outlook is also showing each user as "connected" to the server.

The messages appear to be getting stuck in our local delivery queue, and our end users are getting Delivery Status Notification Delays and Failures.  

Usually these problems go away after a reboot, but not in this case.  I've tried starting and stopping various services, SMTP, etc.  forcing queue connections, freezing/unfreezing, as well as reinstalling MS Exchange and service pages, all to no avail.
mkstylesAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

sukumadeCommented:
There are a lot of things that could be happening, but I hope I can at least try to start you off in the right direction.

First, does your Exchange server connect to a SPAM filter appliance? If so, make sure the rules on it are not preventing inbound/outbound emails.

Second, open Exchange System Manager and check the message delivery options (Global Settings -> Message Delivery right-click and choose properties) and verify none of the settings in there are preventing emails.

Third, check your recipient policies in Exchange System Manager (Recipients -> Recipient Policies) and make sure they are valid.

Fourth, check your routing groups (Administrative Groups -> Routing Groups) and verify everything there is set correctly.

And just out of curiosity, did the IP address of your Exchange server change when you rebuilt the array?
0
DarinTCHSenior CyberSecurity EngineerCommented:
any errors in event viewer - related to this?
Is this EX2003 / IIS6 / Windows Server???

IF is is actually 'crashing' you can use Adplus tool to catch the crash dump file to find more information on this issue.

Debugging Tools for Windows(x64)

http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx

286350 How to use ADPlus to troubleshoot "hangs" and "crashes"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;286350 


0
mkstylesAuthor Commented:
Yes, Exchange 03, IIS 6, Windows Server 03.  

IP did not change and I'm able to telnet to and from fine.  It appears that all settings and policies are as they were.

What I don't understand is that we're getting postmaster delivery failures delivered to our Outlook inboxes - if -those- can be delivered, why not the regular messages?
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

sukumadeCommented:
Go to ESM and go to Administrative Groups -> Servers -> <SERVERNAME> -> Protocols -> SMTP -> right-click on Default SMTP and choose properties.

Verify EVERYTHING in there is set correctly
0
mkstylesAuthor Commented:
Verified, nothing has changed.
0
sukumadeCommented:
Try this in telnet and see if you are able to receive an email this way

HELO hotmail.com
MAIL From: <somerandomuser@hotmail.com>
RCPT To: <myemailaddress@mydomain.com>
DATA
From: somerandomuser@hotmail.com
To: myemailaddress@mydomain.com
Subject: Manual SMTP Test Sent Via Telnet
This was a manual test of an smtp server. It was sent via a telnet session. Please delete upon receiving.
.

Open in new window

0
mkstylesAuthor Commented:
Thanks for your help guys.  Ive been able to get our email moving again.  

I took our database offline, then used eceutil to repair and then rebuild priv1.edb, and then ran isinteg to fix any remaining data errors.  I then remounted priv1 and all was well  our queued messages sent immediately.

My guess is that something got corrupted in the database during the RAID rebuild.  Although it was not visibly apparent, it was bad enough to prevent mail delivery.  
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.