Fixed it...
Darren Honeyball [ML] wrote:
> It's on solaris... spamd is running...
>
> root 1102 1 0 Aug 20 ?0:00 screen -S spamd
> root 1115 1104 0 Aug 20 pts/10 0:06 /usr/local/bin/perl
> /usr/local/bin/spamd -a -x -D
>
> spamc works fine if I run it against a fil
Can you check whether spamd is running?
What distro are you running? I set up qmail-scanner with clamav and
spam-assassin yesterday on a Debian box, and got similar results until I
realised that the Debian install scripts for spam-assassin include a
file at /etc/default/spamassassin that includes
It's on solaris... spamd is running...
root 1102 1 0 Aug 20 ?0:00 screen -S spamd
root 1115 1104 0 Aug 20 pts/10 0:06 /usr/local/bin/perl
/usr/local/bin/spamd -a -x -D
spamc works fine if I run it against a file manually... Just not within
qmail-scanner...
Nick Hol
I'm running qmail / vpopmail, spam-assassin 2.55, clamav 0.60
Qmail is correctly passing the mail to qmail-scanner - clamav is working
fine and blocking messages containing a virus... spamc seems to get called,
but never detects any spam, and in fact, the headers inserted into the email
are:
Rece