Hi there
I've spent all weekend trying to figure this out but I've exhausted all my
options.
My problem is that when I start QMail with
QMAILQUEUE=/var/qmail/bin/qmail-scanner-queue
I get the error message "451 unable to exec qq (#4.3.0)" when testing the
whole setup.
I have increased
Jeremy Bowen wrote:
Hi there
I've spent all weekend trying to figure this out but I've exhausted all my
options.
My problem is that when I start QMail with
QMAILQUEUE=/var/qmail/bin/qmail-scanner-queue
I get the error message "451 unable to exec qq (#4.3.0)" when testing the
whole setup.
I am not sure what's going on but for some reason I can't configure
spamassassin to work under Gentoo.
The email is being sent to and processed by Spamassassin, but for some
reason my qmail-scanner-queue.pl is taking over and not allowing
Spamassassin to modify the email the way I want.
Now I may
On Fri, Jun 18, 2004 at 03:09:45PM -0400, Jesse Guardiani wrote:
> Hello,
>
> Does anyone know if QSS works on qmail-scanner's detail log file
> (i.e. not quarantine.log)? Jason stated a few weeks ago that the
> quarantine log shouldn't be trusted, but I'd still like to install
> QSS. It makes pre
Qmail-scanner-queue.pl
# st: fast_spamassassin options=" -c -f " / verbose_spamassassion options="
-f "
my $spamc_options=' -f';
Remove the -c
By default, spamassassin should do a X-Spam-Level: which looks like the
following:
X-Spam-Status: Yes, hits=29.5 required=5.0 tests=BIZ_TLD,DNS_FROM_R
Hi again
I've tried the various suggestions about raising the memory limit (I went as
high as 100M) but I don't think this is the problem. I still get the error
message in the telnet session after typing . to terminate the email.
I guess one thing I failed to mention in my previous message was th
