On Fri, 9 Apr 2004, Niek Baakman wrote:
> Hello list,
>
> if I run qmail-queue-scanner.pl with this line:
> my $spamc_options=' -f';
> instead of
> my $spamc_options=' -c -f';
>
> will QS add the spamassassin report to the original mail, or won't this work?
Yes..
I've done this on my servers for
Hello list,
if I run qmail-queue-scanner.pl with this line:
my $spamc_options=' -f';
instead of
my $spamc_options=' -c -f';
will QS add the spamassassin report to the original mail, or won't this work?
Regards,
Niek Baakman
--
The greatest trick the devil ever pulled was convincing the world he d
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of
> Cees Hek
> Sent: Friday, April 09, 2004 12:21 PM
> To: James Paige
> Cc: [EMAIL PROTECTED]
> Subject: Re: [Qmail-scanner-general]clamscan --mbox
>
>
> James Paige wrote:
> > It did not detect ANY of the
James Paige wrote:
It did not detect ANY of the three viruses, which was depressing. I then
read the clamscan manpage, and took particular note of the --mbox option.
--mbox Enable scanning of various mail file types (also treat stdin as
a mailbox - for backward compatibility).
So I tried aga
Hello, qmail-scanner friends!
I have been using qmail-scanner on our mail server at West Coast
Aerospace for about two years, scanning with spamd and McAffe uvscan. A
few months ago, unsatisfied with Network Associate's abysmal service and
support I also added ClamAV scanning. I was delighted to
Jason Haar wrote:
If you have $skip_text_msgs=1 and *don't have uudecode installed* then you
are correct. Yup, it's a bug.
However, I'd like to know who doesn't have uudecode installed on their
systems (besides you - obviously). I doubt this affects too many sites...
So, until I fix it properly, a
