bonafide247
IS-IT--Management
Ok...here goes nothing! 
I am using a "scan mail" program on my Exchange 2000 server, which scans every single email based on content, virii, etc.
I recently recovered from a "spam relay" incidient. The relay has been closed now. However, I am noticing as I monitor the scanmail program, that sometimes it will read multiple instances of the same email. I also notice that it seems to also be scanning old email...maybe this old email has been caught up in a loop somehow?
My main problem...after Exchange um-mounts/mounts during on line maintainence, the scan mail goes crazy. It seems to get stuck in a constant loop of scanning...scanning old emails, scanning emails in multiple instances. The result: my processor is at 100% and it brings everything to a crawl.
This goes on and on until I simply stop the Scan Mail service...allow the information store to push all that mail through...and then restart the process.
I have performed the eseutil /d function, but it hasn't solved my problem. The scanmail program worked fine before the incidient...if anyone has a clue about this situation, please enlighten me!
I am using a "scan mail" program on my Exchange 2000 server, which scans every single email based on content, virii, etc.
I recently recovered from a "spam relay" incidient. The relay has been closed now. However, I am noticing as I monitor the scanmail program, that sometimes it will read multiple instances of the same email. I also notice that it seems to also be scanning old email...maybe this old email has been caught up in a loop somehow?
My main problem...after Exchange um-mounts/mounts during on line maintainence, the scan mail goes crazy. It seems to get stuck in a constant loop of scanning...scanning old emails, scanning emails in multiple instances. The result: my processor is at 100% and it brings everything to a crawl.
This goes on and on until I simply stop the Scan Mail service...allow the information store to push all that mail through...and then restart the process.
I have performed the eseutil /d function, but it hasn't solved my problem. The scanmail program worked fine before the incidient...if anyone has a clue about this situation, please enlighten me!