/etc/service/qmail-smtpd/run:
#!/bin/sh
# tcpserver arguments
QMAILDUID=`id -u qmaild`
NOFILESGID=`id -g qmaild`
LOCAL=`head -1 /var/qmail/control/me`
# qmail options
ALLOW_INSECURE_AUTH="0"; export ALLOW_INSECURE_AUTH
REQUIRE_AUTH="0"; exp
On 21/03/12 08:54, Matias Lesniak wrote:
> # ll /var/qmail/bin/qmail-scanner-queue
> -rwsr-sr-x 1 qscand qscand 8,2K 2012-03-08 11:54
> /var/qmail/bin/qmail-scanner-queue
>
>
What does QMAILQUEUE point to? It need to point to
/var/qmail/bin/qmail-scanner-queue, not
/var/qmail/bin/qmail-scanner-qu
I've made the wrapper like this, as root user:
chmod 0755 /var/qmail/bin/qmail-scanner-queue.pl
cd /usr/local/src/qmail-scanner-2.10/contrib
gcc -o qmail-scanner-queue qmail-scanner-queue.c
install -D -o qscand -g qscand -m6755 qmail-scanner-queue /var/qmail/bin/qmail-scan
On 16/03/12 10:57, Matias Lesniak wrote:
> # ll /var/spool/qscan/tmp/
> total 16K
> drwxr-x--- 4 qscand qscand 4,0K 2012-03-15 18:43 .
> drwxrwx--- 6 qscand qscand 4,0K 2012-03-08 11:56 ..
> drwxr-x--- 2 root root 4,0K 2012-03-15 18:43 bmail133184783157023867
> drwxr-x--- 2 root root 4,0K 2
Hi,
i'm writting due to i've problems with qmailscanner (2.08)
I've installed qmail on Ubuntu 11.10 and my first problem was that i
don't have the suidperl support for that version, so i used a c-wrapper
that comes with qmailscanner.
Now i have problems with clamd...
Problems:
# /u
Hi,
i'm writting due to i've problems with qmailscanner (2.08)
I've installed qmail on Ubuntu 11.10 and my first problem was that i
don't have the suidperl support for that version, so i used a c-wrapper
that comes with qmailscanner.
Now i have problems with clamd...
Problems:
# /us
Hi Salvatore,
On Fri, 2 Oct 2009 09:27:48 +0200
Salvatore Toribio wrote:
> At 7:05 +0200 2-10-2009, li...@penpal4u.net wrote:
> >Hi Jason,
> >>> > When I
> >>> > upgraded to 2.06, I ended up with plenty of
> >>> >
> >>> > WARNING: lstat() failed on: ...
> >>> >
> >>> > in the clamd log file
At 7:05 +0200 2-10-2009, li...@penpal4u.net wrote:
>Hi Jason,
>>> > When I
>>> > upgraded to 2.06, I ended up with plenty of
>>> >
>>> > WARNING: lstat() failed on: ...
>>> >
>>> > in the clamd log file and viruses go through.
>>> >
>>>
>>> ? Well that is weird. Qmail-Scanner is specificall
Hi Jason,
>> > When I
>> > upgraded to 2.06, I ended up with plenty of
>> >
>> > WARNING: lstat() failed on: ...
>> >
>> > in the clamd log file and viruses go through.
>> >
>>
>> ? Well that is weird. Qmail-Scanner is specifically designed to
>> tempfail if an AV returns a non-standard error code.
Hi Jason,
> > I've been using qmail-scanner-queue for several years without any
> > problems. However, I had to update clamav and now
> > qmail-scanner-queue has difficulties interacting with it. At first,
> > I tried qmail-scanner-queue 2.05 and it would regularly crash
> > clamd.
>
> Qmail-Scan
On 10/02/2009 03:14 AM, Christian Lerrahn wrote:
> Hi,
> I've been using qmail-scanner-queue for several years without any
> problems. However, I had to update clamav and now qmail-scanner-queue
> has difficulties interacting with it. At first, I tried
> qmail-scanner-queue 2.05 and it would regula
Hi,
I've been using qmail-scanner-queue for several years without any
problems. However, I had to update clamav and now qmail-scanner-queue
has difficulties interacting with it. At first, I tried
qmail-scanner-queue 2.05 and it would regularly crash clamd. When I
upgraded to 2.06, I ended up with p
Hi,
I have an environment with the following softwares:
I have a server running:
- Fedora Core 2 + kernel 2.6.10-1.8_FC2
- netqmail 1.05 + ucspi 0.88 + daemon-tools 0.76 + patches (site lwq)
- netqmail-1.05-tls-smtpauth-20060105.patch (SMTP authentication)
- badrcptto.patch
- vpopmail 5.4.0 + sqw
At 5:54 +0100 17-11-2006, Noc Phibee wrote:
>Ok Thanks, if i don't want of timeout, i delete the "-t 30" it's correct ?
Not really, the default timeout is 600, if you
really want to disable the timeout you have to
set it to 0. " -t 0"
Regards
ST
>Salvatore Toribio a écrit :
>>At 13:11 +0100 1
Ok Thanks, if i don't want of timeout, i delete the "-t 30" it's correct ?
Salvatore Toribio a écrit :
> At 13:11 +0100 15-11-2006, Noc Phibee wrote:
>> Hi
>>
>> i have a big problems with the qmail-scanner version 2.01 ..
>>
>>
>> I use it on a relay server with spamassassin. Before i use it wi
At 13:11 +0100 15-11-2006, Noc Phibee wrote:
>Hi
>
>i have a big problems with the qmail-scanner version 2.01 ..
>
>
>I use it on a relay server with spamassassin. Before i use it with the
>version 1.25
>without problems
>after update to 2.01 version, that's work's a time (1 hours < 2 days)
>a
Hi
i have a big problems with the qmail-scanner version 2.01 ..
I use it on a relay server with spamassassin. Before i use it with the
version 1.25
without problems
after update to 2.01 version, that's work's a time (1 hours < 2 days)
and after
he stop the dialogue with spamassassin and a
hello, it seems that i cant install qmail-scanner
on my gentoo server,its either a glibc problem
(that i checked with revdep-rebuild and said everything
is ok, everything in the system compiles ok)
or a qmail-scanner bug..
here's what i got :
* sys-libs/glibc
Latest version available: 2.3.5
At 13:03 +0200 16-10-2005, Maciej Soltysiak wrote:
Hi,
I did an upgrade of the distribution and now when I send email
I get:
451 qq temporarary problem (4.3.0) and mail is not sent
When I switch to qmail-queue it works but with qmail-scanner-queue.pl
it does not.
I tried running qmail-scanner-
Hi,
I did an upgrade of the distribution and now when I send email
I get:
451 qq temporarary problem (4.3.0) and mail is not sent
When I switch to qmail-queue it works but with qmail-scanner-queue.pl
it does not.
I tried running qmail-scanner-queue.pl and I got a message 'can't find
suidperl', s
>
> 10-15 mails PER SECOND and your running on a P3-1gHz?? This is
> seriously underpowered for this type of mail load. Not to mention you
> should have more ram...atleast a gig. I realize that this load is not
> consistent, but to be able to handle these periods you really are going
> to have t
ag 28 juni 2005 19:21
To: qmail-scanner-general@lists.sourceforge.net
Subject: RE: [Qmail-scanner-general]Problems with F-PROT
Maybe it is related whith my other problem:
=
I'm using qmail-scanner with f-prot.
Fro
Pamcho wrote:
That's the point... I don't know why they are NOT delivered... Are
local mails, and in the status of the local delivering in the log I see
that the max concurrency is not reached.
It's a temporary problem. Some time later they are delivered.
How much time t
> >
> > Take a look at the content of the messages in the queue.
> > And investigate why they are not delivered ...
> >
> > Bye,
> >
> > Joost
> >
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTE
e not delivered ...
>
> Bye,
>
> Joost
>
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Pamcho
> Sent: dinsdag 28 juni 2005 18:26
> To: qmail-scanner-general@lists.sourceforge.net
> Subject: [Qmail-scanner-gener
@lists.sourceforge.net
Subject: [Qmail-scanner-general]Problems with F-PROT
I have qmail-scanner with f-prot.
In some moments I receive up to 10-15 mails/second.
In this moments, when I do:
# qmHandle -s
I see the local queue growing up very fast.
Why is
I have qmail-scanner with f-prot.
In some moments I receive up to 10-15 mails/second.
In this moments, when I do:
# qmHandle -s
I see the local queue growing up very fast.
Why is this?
-
I've found a few questions regarding this problem in the mailing list archives,
but not really any answers.
When I installed qmail-scanner 1.25, I used the "--notify admin" setting. I
want all virii detected to be reported to my admin address, but not to the
users. When I run test_installatio
Hi allI found in this forum many people that told about my problem. So I try to fix it as in the reply post but without success.I Installed Q-S 1.25 in my mandrake 10.1 with perl 5.8.5. I compiled maildrop-1.8.0 with the --enable-maildrop-uid=qscand option and everything went ok.when i compile Q-S
Matt Martin wrote:
Hi,
Ive used Qmailrocks.org on this one. (Have used before with Clam without
issues, however, using Kaspersky this time)
I understand that ask Kaspersky changed the way things worked in the latter
versions of the scanner, that is no longer works (or works with difficulty)?
If I t
Hi,
Ive used Qmailrocks.org on this one. (Have used before with Clam without
issues, however, using Kaspersky this time)
I understand that ask Kaspersky changed the way things worked in the latter
versions of the scanner, that is no longer works (or works with difficulty)?
If I take the line out
Hi,
I'm trying to use the st patch with qmail-scanner 1.24, but have run
into a problem.
qmail-scanner on its own works fine, but when patched with the st patch
it seems to have problems finding/reading files.
I'm trying to use the st patch with the --scanners-per-domains config
option, and qm
Hello
redhat 9.0
Had Q-S 1.21 which worked fine for a long time, trying to update Q-s to
1.23 and getting this error:
./configure --archive no --notify none
[snip]
If that looks correct, I will now generate qmail-scanner-queue.pl
for your system...
Continue? ([Y]/N)
y
Testing suid nature of /u
Hi,
so after endless tries to get my configure script recognizing spamd/spamc,
I've done an apt-get update. In my apt-archive was at this time already
SA 3.0.0.
After installing SA 3.0.0 i've had an error and I was forced to reboot
my machine.
After rebooting my configure script recognized my SA
Salvatore Toribio wrote:
At 22:07 -0700 23-09-2004, Jazzy Jay wrote:
> Hi,
today I've updated my Debian Sid System with apt. In
my apt-archive was
spamassassin 2.64-1 included. I also wanted to get
qmail-scanner to be
up-to-date. I've tried to update qmail-scanner from
1.20rc3 to 1.23 but
t
At 22:07 -0700 23-09-2004, Jazzy Jay wrote:
> Hi,
today I've updated my Debian Sid System with apt. In
my apt-archive was
spamassassin 2.64-1 included. I also wanted to get
qmail-scanner to be
up-to-date. I've tried to update qmail-scanner from
1.20rc3 to 1.23 but
the current releasy won't
> Hi,
>
> today I've updated my Debian Sid System with apt. In
> my apt-archive was
> spamassassin 2.64-1 included. I also wanted to get
> qmail-scanner to be
> up-to-date. I've tried to update qmail-scanner from
> 1.20rc3 to 1.23 but
> the current releasy won't detect my spamassassin on
> thi
Hi,
today I've updated my Debian Sid System with apt. In my apt-archive was
spamassassin 2.64-1 included. I also wanted to get qmail-scanner to be
up-to-date. I've tried to update qmail-scanner from 1.20rc3 to 1.23 but
the current releasy won't detect my spamassassin on this system.
Is there an
I tried qmail-scanner and I´m stuck with the problem that outgoing email is
not filtered. I have a gentoo box, on my first install I install everything
from portage (ebuilds on gentoo tree) and the second time on a clean system
from sources at http://www.qmailrocks.org.
My system use courier
Francisco Perez wrote:
In fact the only way it works is running clamd as root ... :-(
Run over to www.qmailrocks.org - poke through the slackware
installation. That should help.
One thing I found I had to do is once I installed qmail-scanner, I HAD
to chown -R qscand.qscand /var/spool/qmailscan
In fact the only way it works is running clamd as
root ... :-(
ez" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Monday, July 05, 2004 5:05 PM
Subject: Re: [Qmail-scanner-general]problems with C wrapper
> Looks like you forgot to remove the taint option from the
> qmail-scanner-queue.pl file. Edit the file, and remove the -T opti
Looks like you forgot to remove the taint option from the
qmail-scanner-queue.pl file. Edit the file, and remove the -T option in
the first line.
BW
Francisco Perez wrote:
Hello:
Maybe you've seen this problem before, I'm having problems ruinning
Qmail-scanner on suse 9.1, althought I've c
Hello:
Maybe you've seen this problem before, I'm
having problems ruinning Qmail-scanner on suse 9.1, althought I've chowned
qscand.qscand and suid'ed the C wrapper, when qmail-scanner makes the
/var/spool/qmailscanner/tmp/{dymanic-directory} It writtes with root.root
permissionns, and most
Hi,
I installes qmail on my gentoo-2004.1-server with the emerge-files.
so I have installes qmail-1.0.3 and qmail-scanner 1.20
I am fetching my mails from different pop3-servers and scan them locally
for virusses and spams with clamav and spamassassin.
One big mail did not received me, and I cann
At 09:00 19/02/2004, Salvatore Toribio wrote:
Hi Mark
This is really strange, so I have some questions:
How are you starting up qmail, and how do you call qmail-scanner?
Does qmail-scanner-queue.pl looks like this:
-rwsr-xr-x1 qscand qscand 95007 Feb 10 18:21
/var/qmail/bin/qmail-s
At 19:53 + 18-02-2004, Mark Pratt wrote:
At 08:42 18/02/2004, Salvatore Toribio wrote:
At 2:39 + 18-02-2004, Mark Pratt wrote:
At 08:11 16/02/2004, Salvatore Toribio wrote:
At 12:23 +1300 16-02-2004, Jason Haar wrote:
On Sun, Feb 15, 2004 at 10:40:53PM +, Mark Pratt wrote:
When I run s
%% From: Mark Pratt <[EMAIL PROTECTED]>
%% To: [EMAIL PROTECTED]
%% Subject: Re: [Qmail-scanner-general]Problems with AV scanning
%%
%% At 08:42 18/02/2004, Salvatore Toribio wrote:
%% >At 2:39 + 18-02-2004, Mark Pratt wrote:
%% >>At 08:11 16/02/2004, Salvatore Toribio wrote:
At 08:42 18/02/2004, Salvatore Toribio wrote:
At 2:39 + 18-02-2004, Mark Pratt wrote:
At 08:11 16/02/2004, Salvatore Toribio wrote:
At 12:23 +1300 16-02-2004, Jason Haar wrote:
On Sun, Feb 15, 2004 at 10:40:53PM +, Mark Pratt wrote:
When I run sophie (and ClamAV) as the user qscand, I rece
At 2:39 + 18-02-2004, Mark Pratt wrote:
At 08:11 16/02/2004, Salvatore Toribio wrote:
At 12:23 +1300 16-02-2004, Jason Haar wrote:
On Sun, Feb 15, 2004 at 10:40:53PM +, Mark Pratt wrote:
When I run sophie (and ClamAV) as the user qscand, I receive the
message as
shown below. If I run Sop
At 08:11 16/02/2004, Salvatore Toribio wrote:
At 12:23 +1300 16-02-2004, Jason Haar wrote:
On Sun, Feb 15, 2004 at 10:40:53PM +, Mark Pratt wrote:
When I run sophie (and ClamAV) as the user qscand, I receive the
message as
shown below. If I run Sophie as root, the processing completes as nor
What exactly kind of error ?
For permission problem I setting up /var/spool/qmailscan to 777 also.
Could you try to running clamd as root ?
Br,
Fabrizio
On Mon, 16 Feb 2004 14:29:29 -0800 (PST)
Justyn Kemple <[EMAIL PROTECTED]> wrote:
> Has anyone had any problems getting emails to be scanned
Has anyone had any problems getting emails to be scanned using CAV .66 or .67 with qmail scanner?
I get unable to access file errors...I think its something to do with premissions but yet I have /var/spool/qmailscan set to 777
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing
At 12:23 +1300 16-02-2004, Jason Haar wrote:
On Sun, Feb 15, 2004 at 10:40:53PM +, Mark Pratt wrote:
When I run sophie (and ClamAV) as the user qscand, I receive the message as
shown below. If I run Sophie as root, the processing completes as normal
and the message is delivered. What appears
Sunday 15 February 2004 23.40 skrev Mark Pratt:
> Hello all.
>
> Just to add a little more weirdness as reported earlier by Awie (Problem
> using ClamAV 0.66). I have not continued the message thread as the root
> problem does not appear to the same.
http://www.mail-archive.com/[EMAIL PROTECTED]/m
On Sun, Feb 15, 2004 at 10:40:53PM +, Mark Pratt wrote:
> When I run sophie (and ClamAV) as the user qscand, I receive the message as
> shown below. If I run Sophie as root, the processing completes as normal
> and the message is delivered. What appears to be happening is that the
> message
Hello all.
Just to add a little more weirdness as reported earlier by Awie (Problem
using ClamAV 0.66). I have not continued the message thread as the root
problem does not appear to the same.
When I run sophie (and ClamAV) as the user qscand, I receive the message as
shown below. If I run Sop
<[EMAIL PROTECTED]>:
66.35.250.206 failed after I sent the message.
Remote host said: 550-This message matches a blacklisted regular
expression ([Vv]
*[Ii] *[Aa]
550 *[Gg] *[Rr] *[Aa])
I got this when trying to reply to the post:
[Qmail-scanner-general]David Raistrick's "spambox" patch for qmail-s
>
> After messing arround with qmail-scanner, the patch upgrade and trying
> to configure it all - im now turning to you.
>
> Im using FreeBSD 5.1 and have installed qmail, spamassassing and misc
> perl modules. Currently im patching the qmail-1.03 with patch 19
> (downloaded in tar.gz file, from
>
Hi all,
After messing arround with qmail-scanner, the patch upgrade and trying
to configure it all - im now turning to you.
Im using FreeBSD 5.1 and have installed qmail, spamassassing and misc
perl modules. Currently im patching the qmail-1.03 with patch 19
(downloaded in tar.gz file, from
Hi!
I'm having problems with qmail-scanner to detect messages
attachments. Take a look at the header and Content-type:
<...>
Subject: =?iso-8859-1?B?c2ls6m5jaW8h?=
Date: Tue, 11 Nov 2003 11:35:12 +
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=_NextPart_000_58eb_1c9c_af
Hi!
I've followed the guide at ... to get the Clam Antivirus daemon running
under daemontools... I then configure qmail-scanner to use clamuko ... fine,
things seems to be working... But during the last 24Hours after my change
(and upgrade to 1.20), I have some of these entries in my smtp-log:
@
Thanks got it. for some reason (long day) I was looking in he
spamassassin dir. doh!
-Original Message-
From: Dallas L. Engelken [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 27, 2003 5:34 PM
To: Jennifer Fountain; [EMAIL PROTECTED]
Subject: RE: [Qmail-scanner-general]problems with
> -Original Message-
> From: Jennifer Fountain [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 4:15 PM
> To: Dallas L. Engelken; [EMAIL PROTECTED]
> Subject: RE: [Qmail-scanner-general]problems with SA
>
>
> I just confirmed. Although, I did
when I applied this to the end, I get this error on line 2002 which is
this line:
open(SOUT,">$scandir/$wmaildir/new/$file_id.spamc")||&tempfail("cannot
open for write $scandir/$wmaildir/new/$file_id.spamc - $!");
could this be an old version. spamassassin is starting
> -Original Message-
> From: Jennifer Fountain [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 1:41 PM
> To: Dallas L. Engelken
> Subject: RE: [Qmail-scanner-general]problems with SA
>
>
> this is the only thing in my scanner_array:
>
> my @sc
> -Original Message-
> From: Jennifer Fountain [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, August 27, 2003 12:32 PM
> To: [EMAIL PROTECTED]
> Subject: [Qmail-scanner-general]problems with SA
>
> --scanners "clamscan,verbose_spamassassin"
>
>
I don't think SA is working correctly.
According to my logs:
maillog:
Aug 26 14:40:14 chopin spamd[580]: server started on port 783 (running
version 2.55)
[EMAIL PROTECTED] qmailscan]# tail qmail-queue.log
Wed, 27 Aug 2003 13:24:03 -0400:24929: w_c: primary Content-Type of
text/plain found
Wed
Hi!
I'm trying to get RAV to work with qmail-scanner and I've bashed my head to
the wall for some times now... I could need some help :-)
The perl-scanner itself works fine, and I could send mail to and from the
server. When the scanner then invokes RAV, it checks for the exit code to
decide wheth
<[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Tuesday, February 11, 2003 10:20 PM
>Subject: [Qmail-scanner-general]Problems with perl!! ugh!
>
>
>> Hi All,
>> I'm setting up a new email server for the company, and webhosting clients
>with virus scan
t; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 11, 2003 10:20 PM
Subject: [Qmail-scanner-general]Problems with perl!! ugh!
> Hi All,
> I'm setting up a new email server for the company, and webhosting clients
with virus scanning and
> anti-spam s
OK, I commented out line 82 in qmail-scanner-queue.pl like you said and ran it again
and now I get:
setuidgid qmaild /var/qmail/bin/qmail-scanner-queue.pl -g
Global symbol "$V_HEADER" requires explicit package name at
/var/qmail/bin/qmail-scanner-queue.pl line
84.
BEGIN not safe after errors--
Hi All,
I'm setting up a new email server for the company, and webhosting clients with
virus scanning and
anti-spam support; however, I'm having one heck of a time trying to get qmail-scanner
working correctly. I
had it working correctly for a while, but I had to upgrade perl to get Spa
Hi,
Can anybody help me fixing the below problem?
07/02/2003 18:09:47:24496: +++ starting debugging for process 24496 by
uid=1001 at 07/02/2003 18:09:47
07/02/2003 18:09:47:24496: setting UID to EUID so subprocesses can access
files generated by this script
07/02/2003 18:09:47:24496: program name
Hi guys,
I've got a problem with ripmime and qmail-scanner 1.15. Sometimes I receive some
emails with
viruses, but once a week or so. Other emails with virus are not bypassing the scanner.
There is no
relation between the type of virus and if they can or cannot bypass the scanner. I use
F-P
This problem seems to have been posted quite a few
times in the last few days. I'm running Qmail-scanner 1.1.5 scanning with
ClamAV-054 and Spamassassin-2.43, on Redhat 8.0 (thusly with Perl 5.8.) The same
setup works perfectly on a system running perl 5.6.1. Through my megar knowledge
of pe
On Wed, Dec 18, 2002 at 07:31:36AM -0500, [EMAIL PROTECTED] wrote:
> Unless you tell me otherwise, I'll assume you don't mind me sharing this
> with the SA list? They came up empty on this.
Yeah - it's been fixed for a couple of weeks in 1.16 - but I haven't
released it yet.
...and now it's this
On Tue, 17 Dec 2002, Hine,Chris wrote:
> I have attached the patch that I use that specifically checks for score
> and threshold = 0. This should only cause a problem if you have set your
> threshold to 0.
> The relevant line is below.
> - if ($sa_max > $sa_score) {
> + if (($sa_max > $s
If I understand you correctly, will this also fix it so email gets
delivered if spamd is down? That's the way it's supposed to behave
according to the docs for spamc and what I can glean from the QS code, but
when spamd is down, ALL email is marked as 0/0 and rejected.
Thanks!
On Tue, 17 Dec 20
Basically, as of QS 1.15 (I think) Jason decided he wasn't going to
trust the return value from spamassassin, as there have been a number
of versions that don't work properly, so QS checks the values and marks
the mail as spam itself.
Unfortunately the test that is used is score >= threshold, whic
Found that out too with SA 2.20 which is shipped with Debian woody. It
seems to be caused by too large mails, which aren't scanned by SA so it
gets 0/0 as score.
I haven't found out what to do about this, but in my mail program
(Ximian Evolution 1.20) I filter on:
Header X-Spam-Status contains "Ye
I have a new server up with qmail-scanner, spamassassin 2.4.3 (spamd for
system-wide use) and maildrop. It works fine most of the time, but when
certain attachments arrive (NOT ones listed in quarantine.txt), the email
is rejected as spam because the threshold and hits are reset to 0 like
this:
On Wed, Nov 06, 2002 at 02:41:58PM -0700, Tren Blackburn wrote:
> I did a bit more hunting and found that some of the messages, the
> filename is:
>
> goldfish.doc
> .pif
>
> or .bat, or whatever. I didn't count exactly how many spaces, but this
> seems to be the case for the messages getting th
ECTED]
[mailto:qmail-scanner-general-admin@;lists.sourceforge.net] On Behalf Of
Tren Blackburn
Sent: Wednesday, November 06, 2002 2:32 PM
To: [EMAIL PROTECTED]
Subject: [Qmail-scanner-general]Problems with Reformime
Hi List;
I have noticed that I've had a couple instances of the Lentin.F vir
Hi List;
I have noticed that I've had a couple instances of the Lentin.F virus getting
through qmail-scanner/fsav.
I did some digging through the log files and found that it seems like reformime
isn't properly putting the attachment back together. The filename ends up .pif
or .bat and never gets
torsdagen den 31 oktober 2002 22.36 skrev John Johnson:
> ok how do I fix the problem with line 82 in the
> quarantine-attachments.txt
> I don't see the problem but it is telling me there is one.
The different fields should be separated by a tab, look at the other lines to
see how it should be.
ok how do I fix the problem with line 82 in the
quarantine-attachments.txt
I don't see the problem but it is telling me there is one.
-John
_
John Johnson
SysAdmin
ICQ#: 24823932
More ways to contact me: http://wwp.icq.com/24823932
__
>Increase your softlimits.
>
>--
>Ed.
>
>> -Original Message-
>> From: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED]] On
>> Behalf Of Salvatore Toribio
>> Sent: Tuesday, October 15, 2002 11:06 AM
>> To: [EMAIL PROTECTED]
>&
Increase your softlimits.
--
Ed.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On
> Behalf Of Salvatore Toribio
> Sent: Tuesday, October 15, 2002 11:06 AM
> To: [EMAIL PROTECTED]
> Subject: [Qmail-scanner-general]Problems updating
Hi,
I'm running qmali-scanner 1.14 in a RedHat 7.1 with Sophos Sweep.
Everythins was working ok until i've updated Sophos Sweep from
version 3.60 to 3.62
I got this error
/var/spool/qmailscan/qmail-queue.log
.
15/10/2002 12:45:24:19285: tempfail: X-Anti-Virus-PUSC-1.14: corrupt
or unkno
Hi
all,
i tried to install
qmail-scanner-1.14 with Inoculan antivirus, it doesn´t work, i tried vscan from
TrendMicro, and it doesn´t work again, please is there anybody who has installed
qmail-scanner with one of this antivirus?, please could you tell me how did you
do?, please could y
s you need
to better explain (in detail) what you're actually attempting to do, because I
seem to have missed the goal.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> Doug Monroe
> Sent: Friday, August 30, 2002 8:37 PM
> To: [EMAI
ugust 30, 2002 8:37 PM
To: [EMAIL PROTECTED]
Subject: Re: [Qmail-scanner-general]problems with the to: field using
qmail-scanner and spamassassin
Jeremy Olmen wrote:
>
> Only problem is that I'm not trying to do any local delivery, this is
simply
> a spam-and-virus filtering front e
Jeremy Olmen wrote:
>
> Only problem is that I'm not trying to do any local delivery, this is simply
> a spam-and-virus filtering front end for the destination (sadly, exchange).
> My job would be so much easier if I could've just used maildrop or procmail!
> (although it appears maildrop only wo
h sendmail).
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
Doug Monroe
Sent: Friday, August 30, 2002 2:06 PM
To: [EMAIL PROTECTED]
Subject: Re: [Qmail-scanner-general]problems with the to: field using
qmail-scanner and spamassassin
Jeremy Olmen wrote:
>
> I
Doug Monroe wrote:
[snip]
> MAILDIR=$HOME/Maildir/
> DEFAULT=$MAILDIR
[snip]
> ## WHAT TO DO
> # options: -delete- or -hold- or -forward- spam
> # to delete
> /dev/null
> # to hold:
> #spam <-- SEE NOTE BELOW
> # or...
> # to forward:
> # ! [EMAIL PROTECTED]
I should men
Jeremy Olmen wrote:
>
> I am trying to use qmail-scanner in conjunction with spamassassin as well as
> a small script to determine the score of the message, and if it's above my
> defined threshold to send it to another mailbox. If the conditions are met
> and the message is to be sent to another
I am trying to use qmail-scanner in conjunction with spamassassin as well as
a small script to determine the score of the message, and if it's above my
defined threshold to send it to another mailbox. If the conditions are met
and the message is to be sent to another mailbox, all I'm doing is
re-w
Hi everybody!!!
I'd a little problem installing qmail-scanner.1.1
When I run configure with my options I get the following errors:
perlscanner: generate new DB file
ERROR: incorrect format on line 74 - skipped
ERROR: incorrect format on line 75 - skipped
ERROR: incorrect format on line 77 - skippe
99 matches
Mail list logo