ConfigServer Community Forum

We'd really need to see the results of a MailScanner debug run and any errors from the maillog when you try to start MailScanner, in order to determine what the problem might be. See step 7 in this FAQ for instructions on how to run MS in debug:
http://www.configserver.com/techfaq/index.php?faqid=14

I'm not sure what's happening on your server. I presume you've tested the virus scanner by sending the eicar test virus, or otherwise confirmed that virus scanning is occurring. It may be a problem with chkservd itself. You could contact cPanel if you're concerned about it.

Is clamd actually running if you look for it in ps axf? Are there two entries for clamav/clamd in Service Manager?

I don't think any of those are anything to worry about. The first one is a normal line that occurs every time MailScanner starts. If the other two only happen occasionally it probably doesn't indicate a problem.

There is a script that runs overnight that will update the scanning rules, or if you wish to force it you can run the following in SSH:

/usr/mscpanel/mscpanel.pl -i

Regards,
Sarah

Are you seeing any clamav related errors in the maillog?

Maverick, if you're watching the maillog and not seeing any errors, it may just be that it's going to take some time for MailScanner to process the backlog.

It could be outgoing mail that is not being scanned. By default we configure MailScanner to not scan outgoing mail. Or it could be some rule that is causing the mail not to be scanned. It could also be that they were too large to scan. To find out for sure you will need to find some of these emails ...

You can't force MailScanner to deliver the pending queue. The only way to get that mail delivered without fixing whatever the underlying problem is, is to uninstall MailScanner so that the pending mail will be moved to the exim delivery queue. If your pending queue is growing that large that means t...

That's not an error. It's red because it took a few seconds to come back with the information. The colour coding is only for timing, not for errors. If it was an error it would say "error" instead of "diag".