[Qmail-scanner-general]Disallowed MIME characters in header

2004-10-19 Thread Torsten Kurbad
Hi all, I'm using qmail-scanner-1.23st on a local server that collects messages from all my boxes via fetchmail. Recently, I got several bulk mails from an institution at my former university, which were quarantined because of "Disallowed MIME characters...". The messages turned out to have some

[Qmail-scanner-general]clamav 0.80 in mail header

2004-10-19 Thread Leandro
(excuse my for my bad english) When I use qmail-scanner 1.23 with spamassassin 2.64 and clamav 0.65 , the mail header has: clamdscan: 0.65. spamassassin: 2.64. When I try to use qmail-scanner 1.23 with spamassassin 3.0.0 and clamav 0.80 , the mail header has : spamassassin 3.0.0(without spe

Re: [Qmail-scanner-general]clamav 0.80 in mail header

2004-10-19 Thread Rui Lopes
Leandro wrote: (excuse my for my bad english) When I use qmail-scanner 1.23 with spamassassin 2.64 and clamav 0.65 , the mail header has: clamdscan: 0.65. spamassassin: 2.64. When I try to use qmail-scanner 1.23 with spamassassin 3.0.0 and clamav 0.80 , the mail header has : spamassassin 3.0.0(

Re: [Qmail-scanner-general]clamav 0.80 in mail header

2004-10-19 Thread Rui Lopes
Leandro wrote: It doesn´t work. When I should make changes ? ... in compilation time ... or in perl script ? After install you need to edit the perl script qmail-scanner-queue.pl. I forgot to mention that you have to run: /usr/local/bin/qmail-scanner-queue.pl -z as the user you use to run qmail-s

Re: [Qmail-scanner-general]Disallowed MIME characters in header

2004-10-19 Thread Jason Haar
On Tue, Oct 19, 2004 at 10:34:30AM +0200, Torsten Kurbad wrote: > The FAQ to qmail-scanner is a bit misleading here, since it > implies that all header lines containing a \r (also at the EOL) > won't pass the filter. That's a bit unfair. The reality is that the FAQ would have to quote a fair chunk

Re: [Qmail-scanner-general] Cannot allocate memory

2004-10-19 Thread Justin Fielding
> I have no such file. > > My setup is: > > VPS running FC1. > clamav-0.80rc4. > > The VPS has 256MB of Dedicated RAM, 15GB HDD, Host machine is (2) 2.8 GHz > Xeon, 8 GBs RAM. I noticed in the QoS logs that there have been a few > resource demand peaks, I bet they are at the same time as this err

Re: [Qmail-scanner-general] Cannot allocate memory

2004-10-19 Thread Justin Fielding
Hmm: [EMAIL PROTECTED] bin]# qmail-scanner-reconfigure Configuring qmail-scanner: failed to call /usr/bin/clamdscan --version - Cannot allocate memory at /var/qmail/bin/qmail-scanner-queue.pl line 1953. OK [EMAIL PROTECTED] bin]# clamscan --version ClamAV 0.80rc4/540/Tue Oct 19 15:59:23 2004 [EMAI

[Qmail-scanner-general]Qmail-scanner permission problem?

2004-10-19 Thread Ryan Park
I've recently installed qmail-scanner 1.23 in an attempt to reduce my spam intake. I'm using Slack 9 (no suidperl), perl 5.8.0, spamassassin 3.0.0 w/Razor, and clamAV 0.80 and everything *looks* alright as it runs from a non-priviliged account. What I'm getting though, as I try to call qmail-scann