I noticed clamd and the clamav-* packages were updated to 0.88.1. However, clamd.conf also changed 'User qmailq' to 'User clamav'. I thought it had something to do with the recently discovered vulnerability in clam, so let it change it to User clamav. I sent a couple of test e-mails after reconfiguring qmail-scanner and everything seemed fine.

However, this morning I got reports that mail scripts weren't working. I changed User clamav back to User qmailq and restarted clamd and everything seems fine again.

I was just wondering: won't this give new users problems or does installing qmail-scanner change clamd.conf to use User qmailq or something?

Clamav needs to run as the user qmailq, which should be set from a trigger in the qmail-scanner rpm.

That trigger will work correctly on my, or dag wieers (rpmforge) clamav rpms. It probably wont work on the version from fedora-extras.

Ah, ok, there's a trigger in the qmail-scanner rpm. Thanks.

Whenever I restart clamd (after an update usually), I see "Can't save PID in file /var/run/clamav/clamd.pid" in my logwatch email. I notice /var/run/clamav/ is owned by clamav:clamav. However, clamd is running as qmailq when qmail-scanner is installed. Am I right in thinking that /var/run/clamav/ should be owned by qmailq then?

Hmm it could. Its probably a harmless message right now though. I'll look into it

Change ownership of the directory and the error will go away, but it is (as Scott says) a harmless error, all will still work in any case (or at least it has on some of my boxes).

OK so on a related note to this thread, qmail-scanner 2.0 (in atomic-bleeding) requires you to use a different user, qscand, for both qmail-scanner and clamav. I've got this up and running on a new Project Gamera box, however I didnt write the rpm with upgrades or even PSA support at this time. So I'm going to revisit migrations on this issue specifically. What Im not sure about is how that directory even got owned by qmailq in the first place. Has anyone else had that happen?