Atomicorp

Hey Scott,

Just thought I'd let you know I had a real problem with email since the last Yum update.
The update seemed to go fine with no errors, however the following day I had a client complaining he couldn't use email.

I checked it out and sure enough, no domains could send or recieve email.
I had done a recent Plesk update too and thought it may be related to some of the issues with 8.4

I decided I was barking up the wrong tree after a while and checked the mail log to discover loads of ClamAV errors.

I eventually got the email back up and running but only after removing ClamAV and QMail Scanner.
I haven't dared re-install them yet.

Maybe it's just me but thought you should know

I ran into the same problem but I thought it was just me. My RHEL5 box updated just fine.

I had (possibly) this same problem, and when I tried to restart clamd, it complained about not being able to read the log file. I changed the owner of all the files in /var/log/clamav/ to be clamav:clamav, and that fixed it.

I've read elsewhere that these logs need to be owned by qscand, but my install is working fine after making this change. YMMV.

If I remember correctly, there were also several .conf files that had to be renamed on install (because they were installed as .conf.rpmnew), due to obsoleted options in the old files.

I suspect that if you uninstalled it, you would be able to re-install in it would be fine.

EDIT: I have since re-set the owner of my clamav log files back to qscand. I think the key is that after the update and replacement of the .conf files, you need to run qmail-scanner-reconfigure to set the user for clamav to run as back to qscand.

I had a problem as well (CentOS5). I upgraded to 8.4.0, and then did a yum update. During the yum update i spotted an error message half way through, but everything seemed fine. I was able to send / receive e-mails from domains outside (from hotmail yahoo etc.). Its only when I got a phone call that I found there was a problem.

The problem was it wouldnt send e-mails via port 587, but 25 was fine. Moving the old conf files with the new ones (rpmnew), and then doing:
/usr/bin/qmail-scanner-reconfigure

sorted it. I also did a restart just to be sure there were no problems

/sbin/service clamd restart

and

tail -f /var/log/clamav/clamd.log

I had similar problem. The only problem for me was clamd unable to accept two config lines in clamd.conf file.

So I needed to comment out lines 300 and 315:
#ArchiveMaxCompressionRatio 300
#ArchiveBlockMax no

Clamd then started OK.

edit: Using Plesk 8.3, CentOS 5 and this only started after today's full update.