I just fixed mine, with MasterSleepy's help. Seems to be a common thing.
Try this command:
rpm -q qmail-bsmtpyou should get a response like this:
qmail-bsmtp-0.1-1If not, then install this file:
http://ccskavenger.lc-usa.net/SME(E-SMITH)/contribs/clamav-old/qmail-bsmtp-0.1-1.noarch.rpmThis is copied directly from
http://www.pagefault.org 's old howto:
'Problem' e-mails and Bug Reports Clam Antivirus is being continually worked on to improve the quality and stability of the program.
If an error occurs with Clam Antivirus an e-mail will be sent to the administrator with the subject "Message put into problems directory".
The actual e-mail has been stored in
/var/spool/amavis-ng/problems as
<unique number>.msg and
<unique number>.log, which will be stated in the e-mail.
There are several possible reasons for why this has occurred. Possibly the clamd process has either died or failed to start, you should run:
/sbin/service clamd startEnsure that clamd has restarted successfully by running the tests mentioned in the 'A Few Simple Tests' section.
Before re-injecting the e-mails in the problems directory, you should determine if a certain message is the cause of the problem. You can test the messages by runnin g the following (on each mail message in the problems directory):
cat <unique number>.msg | clamscan --mbox -For all messages that return successfully and that are not infected you should resubmit to the mail system by running the following command:
/usr/bin/amavis-inject -S 127.0.0.1 /var/spool/amavis-ng/problems/<unique number>.msgYou can then delete the email and logfile:
rm -f /var/spool/amavis-ng/problems/<unique number>.msgIf a message fails with the above test it must not be re-injected into the mail system directly. First determine if the mail is not spam, and if so re-inject it with the following command:
/usr/bin/amavis-inject /var/spool/amavis-ng/problems/<unique number>.msg | /usr/bin/rsmtpIf the e-mail is not confidential you should attach it (zipped) with the version information of Clam Antivirus (available by running clamscan --version) and send this to damien@pagefault.org and I'll attempt to debug your problem and role out a patch.
the howto can be found at:
http://www.pagefault.org/howto/amavis_clam.shtmlHTH