Page 1 of 1
Qmail-scanner for Fedora 8?
Posted: Sat Sep 06, 2008 11:47 am
by soarchrist
Scott, (or anyone)
I noticed there's no Qmail-scanner rpm in the Fedora 8 repo... any reason for this?
I'm trying to setup SpamA + ClamAV on a FC8 box... but when I go to run "yum install qmail-scanner", of course it can't find it. What shall I ever do?
S.
Posted: Sat Sep 06, 2008 1:10 pm
by scott
Panic!
Posted: Sat Sep 06, 2008 6:15 pm
by soarchrist
Should I just download qmail-scanner from it's source and just install it separately? I don't know if your rpm is different...
Posted: Sun Sep 07, 2008 5:38 pm
by soarchrist
Assuming your silence you're trying to get me to figure it out on my own.
Does anyone know of a good tutorial on installing SpamA, ClamAV with Qmail-scanner? Everything is like half-way there.
I have all three installed and SpamAssasssin seems to be running fine, but ClamAV is having problems.
The clamd.conf and freshclam.conf have qscand as the user, and all log files and database files are under the ownership qscand also. If so, why do I get this error message?
Code: Select all
# service clamd start
Starting Clam AntiVirus Daemon: LibClamAV Error: cli_loaddbdir(): Can't open directory /var/clamav
ERROR: Unable to open file or directory
Any ideas? I'm stuck at this point... tried reinstalling, reconfiguring, changing permissions to root, etc.
Posted: Sun Sep 07, 2008 5:45 pm
by scott
Or maybe its the weekend and I'm taking a break
Posted: Sun Sep 07, 2008 5:48 pm
by soarchrist
Such a punk, Scott
.... that's fine that you're taking a break... and I'm not in a "panic" attack here... just want to get done setting up. Any insight there weekend chap?
Re: Qmail-scanner for Fedora 8?
Posted: Mon Sep 28, 2009 4:08 pm
by Griffith
turn of selinux
echo 0 >/selinux/enforce
and edit /etc/selinux/config
Re: Qmail-scanner for Fedora 8?
Posted: Mon Sep 28, 2009 6:31 pm
by mikeshinn
Yep, thats an SELinux error alright. If you want to use SELinux you'll need to check your logs, see what SELinux is choking on with clamd and adjust your SELinux policies - or turn SeLinux off.