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

Exchange 2000 Message Queue Puzzle

I am running Windows 2000 and Exchange 2000.  This server is also the DC for about 25 users.  The server has seen better days, but is currently stable.  However, I have noticed that the ESM queues doesn't clear expired messages.  The \\Mailroot\Vsi\Queue folder is empty and so is \\Inetpub\mailroot\vsi\queue.  The Badmail folder is receiving new entries daily, but none of the queues in ESM are expiring.  The local delivery is empty, but other queues that should automatically expire are still visiable.  Even the properties of the queue states that it is expired, but it just keeps attempting to resend messages.  At least according to the retry timestamp on the queue.  I have retry and timeout interval set at the default.

Why aren't these messages automatically timing out?  And if they are timing out and going to the badmail folder, why isn't this being communicated to ESM?

Thanks in advance.
0
gdf99
Asked:
gdf99
  • 3
  • 3
1 Solution
 
SembeeCommented:
Are there are actually items listed, or do you see a list of domains with the number of messages showing 0?

Simon.
0
 
gdf99Author Commented:
Domain with actual items listed.  I can enumerate and see messages.
0
 
SembeeCommented:
Have you checked all three folders in mailroot?

The most common cause of this is av software scanning where it shouldn't.

Simon.
0
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 
gdf99Author Commented:
I checked the Queue folder, and Pickup folder.  They are both empty.  The Badmail folder has plenty of items and gets more every day.  That is what is more puzzling.  It appears that the messages are timing and being sent to the badmail folder, but the ESM doesn't reflect that.

I'll double check the AV, we have NAV running at the file level, I know for sure it's not scanning the database.
0
 
SembeeCommented:
Make sure that it isn't scanning any of the queue folders. I usually suggest that it shouldn't scan any part of the Exchange structure.

Simon.
0
 
gdf99Author Commented:
I tried to check what folders were being scanned by NAV but it is a Corporate Edition client and Server Group it belonged to no longer exist.  Basically, the client wasn't telling what scheduled scan was actually scanning and the real-time scan was already turned off.  

I stopped the client from running at all.  Messages from October 13, 14, & 15th didn't expire, but all the rest up to timeout threshold did.  

I guess until I figure out what NAV is scanning, I'll leave it off.  

Thanks!
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.

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