Can not install qmail-scanner
Can not install qmail-scanner
Hello
I have tried installing qmail-scanner and can not seem to get it to work.
I have installed this in the past on other servers, so did not think it would be so hard.
Upon running yum install qmail-scanner i get
Installing: qmail-scanner 100 % done 1/1
cannot write to /var/spool/qmailscan/qmail-scanner-queue-version.txt.tmp - Permission denied at /var/qmail/bin/qmail-scanner-queue.pl line 2089.
PSA Qmail works perfectly I just can't install this. Any ideas???
Al
I have tried installing qmail-scanner and can not seem to get it to work.
I have installed this in the past on other servers, so did not think it would be so hard.
Upon running yum install qmail-scanner i get
Installing: qmail-scanner 100 % done 1/1
cannot write to /var/spool/qmailscan/qmail-scanner-queue-version.txt.tmp - Permission denied at /var/qmail/bin/qmail-scanner-queue.pl line 2089.
PSA Qmail works perfectly I just can't install this. Any ideas???
Al
SOLVED!!!!!!!!
yum remove qmail-scanner
cd /var/spool
rm -rf qmailscan/
rm -rf qscan/
yum install qmail-scanner
STOP clamd and spammassassin
qmail-reconfigure
start clamd and spamassassin
qmail-recondfigure
and finished.... awesome!
cd /var/spool
rm -rf qmailscan/
rm -rf qscan/
yum install qmail-scanner
STOP clamd and spammassassin
qmail-reconfigure
start clamd and spamassassin
qmail-recondfigure
and finished.... awesome!
That worked thanks. I now have a working qmail-scanner. Hopefully this should cut down on the ammount of spam.
One question, is it possible to find out how many emails qmail-scanner/spamassassin rejects as spam?
We were getting a lot of 'bounce spam' problems and I would just like to know if the spammer is still trying to get mail bounced through our server.
Thanks again pridedata
Alan
One question, is it possible to find out how many emails qmail-scanner/spamassassin rejects as spam?
We were getting a lot of 'bounce spam' problems and I would just like to know if the spammer is still trying to get mail bounced through our server.
Thanks again pridedata
Alan
well:
[root@server1 log]# ps -aux | grep spamd
root 13310 0.0 6.4 38184 32184 ? S Aug17 0:04 /usr/bin/spamd -d -c -m5 -H -r /var/run/spamd.pid
root 13341 0.0 6.4 38184 32112 ? S Aug17 0:00 spamd child
root 13342 0.0 6.4 38184 32112 ? S Aug17 0:00 spamd child
root 21152 0.0 0.0 1504 452 pts/0 S 08:58 0:00 grep spamd
[root@server1 log]# kill -9 21152
-bash: kill: (21152) - No such process
[root@server1 log]#
[root@server1 log]# ps -aux | grep spamd
root 13310 0.0 6.4 38184 32184 ? S Aug17 0:04 /usr/bin/spamd -d -c -m5 -H -r /var/run/spamd.pid
root 13341 0.0 6.4 38184 32112 ? S Aug17 0:00 spamd child
root 13342 0.0 6.4 38184 32112 ? S Aug17 0:00 spamd child
root 21152 0.0 0.0 1504 452 pts/0 S 08:58 0:00 grep spamd
[root@server1 log]# kill -9 21152
-bash: kill: (21152) - No such process
[root@server1 log]#
-
- Long Time Forum Regular
- Posts: 2813
- Joined: Sat Aug 20, 2005 9:30 am
- Location: The Netherlands
You tried to kill exactly the wrong process. 21152 was the 'grep spamd' you did, which indeed has already finished by the time you return to the prompt. You should have killed 13310, 13341 and 13342.
You can also filter out any results containg grep of course: ps aux | grep spamd | grep -v grep
You can also filter out any results containg grep of course: ps aux | grep spamd | grep -v grep

Lemonbit Internet Dedicated Server Management