Desktop with Slackware 64 14.1 full install. Installed Claws-mail 3.11.1 and clamav from slackbuilds. When I install the clamav plugin and try to start claws-mail I get an error message that clamd isn't running. I have followed the instructions from the slackbuild README.Slackware which says to edit the /etc/clamd.conf and /etc/freshclam.conf. I have modified the /etc/rc.d/rc.M as directed so that clamd is started. When the rc.M runs I see clamd started, in fact it takes a little. But when I then start Claws-mail it gives me the clamd init failure message. I see that rc.clamav is executable, and the two modified files are owned by root root, consistent for the /etc/rc.d folder. What have I overlooked that isn't allowing claws-mail to access clamd? Note that I don't believe claws-mail uses the sendmail.

Question 1) Clamd.conf has a statement to limit the number of clamd sessions to one and I'm wondering if that is where the problem starts? Thoughts or confirmation from anyone on this thought?

Question 2) I found where Klamav is available for older versions of KDE and Kmail. Claws-mail uses MH local mail storage and IMAPCACHE for the IMAP connection. KMail uses maildir for local storage, althuogh I've read some don't consider it a standard maildir. If I migrated/switch to using Kmail on this newer install is the Klamav still a maintained usable option to scan my mail attachments for virus?

Question 3) I've been unable to get ClamTK, also installed from slackbuilds to run. I think it is failing for the same reason.
Suggestions for how to troubleshoot this is appreciated.

On question 1, I don't think so. Clam works fine here but I never touched the config file. Have you run freshclam to get definitions?

On 2, ClamTK doesn't like the Oxygen theme. It needs an edit for ClamTK to work:
Then save it. Now ClamTK should work.

1 members found this post helpful.

bamunds,

if you are indeed using KDE with the default oxygen theme, try setting some other theme, at least for the GTK applications. Log off and on and start ClamTK. Have you installed all dependencies for it?

JackHair,
Thank you for the reply and suggestions they have moved me closer but not yet solved.
Adding your suggestion now allows ClamTK to start the GUI interface. Progress However not solved yet because it reports that there are no signatures in the database. If I have root check the /var/lib/clamav location of the signatures they are present but ClamTK in user isn't seeing them. I'm wondering if I have a group permissions issue and that I must add my user to the clamav group?

solarfields,
Thank you for the help and suggestions, yes I am using the standard KDE 4.10. All dependencies are install.

I'm going to go back and check the ClamAV documents to see if I not only need to add a uid/gid for clamav, but if I must add my user to that group also. Any other suggestions?

If you're suspecting permissions, what are the permissions of /var/lib/clamav and the files contained in that folder? If the group ownership is clamav, and your user is not part of that group, that explains why you wouldn't have access.

Thanks bassmadrigal, that was the issue, the files were owned by clamav,clamav and my user wasn't part of the clamav group. The slackbuilds package had a note for adding clamav to amavisd and vice-versa, but didn't say anything about adding yourself to the clamav group, I'll send a note to maintainer that it might help to include that advice. ClamTK now sees the signature file and scans files with correct results, ie it shows x files scanned instead of 0. Clawsmail isn't throwing an error, but I'll have to test a couple of files to see if they actually are scanned. As soon as that is accomplished I'll mark this as solved.

This is now solved per bassmadrigal's suggestion about ownership and permissions. Thanks again. I also updated ClamTK from source since it was reporting a new version available.