File Server Stats: Win2k SP4 with Exchange2k SP3 with postSP3 rollup. Anti-virus software: eTrust InoculateIT v.6 Currently we have no file-level scanning scheduled on our Exchange server, and we are only using the Realtime Monitoring plug-in for Exchange. Realtime scanning is only EXcluding the M: drive for the Exchange2k server.
Here is our delimma:
Our server is filling up with a lot of mail within it?s Badmail and Queue folders (C:ExchsrvrMailrootvsi 1BadMail and C:ExchsrvrMailrootvsi 1Queue respectively). This mail that resides in the Queue sub-directory does get sent to the respective users, but when I reboot the server, they get their mail again, but the queue is then flushed ready to be clogged up all over again. After doing some research within some tech web-sites, people state that you need to turn off file-level scanning for InoculateIT, and that will solve the problem. However, we do not have file-level scanning on, so that can?t be the solution.
Should we exclude the C:ExchsrvrMailroot sub-directories within the Realtime Monitoring? Wouldn?t excluding that folder expose us to email attachments that have viruses in them? Or, does Realtime Monitoring scan e-mail attachments a different way and scanning attachments wouldn?t be affected with that exclusion?