Hello All,
I have a strange Qmail-scanner problem.
Everything works except when infected mails arrive wich have a double
extension. Although most E-mails are scanned Qmail-scanner doesn't seem
to handle E-mail which have 20 to 30 blank spaces infront of the last
extension.
Now with the Yahe vir
hi
thanks for thinking with me.
disk space problem is one of the first thing I checked :)
a df -k
/dev/dsk/c0t0d0s5 144274 49684 8016339%/var
about 78 Mb free on var
but.. apart from memory and disk space, file descriptors could
also be an issue.. "squid -k shutdown".. "rc_qmai
On Thu, Jul 04, 2002 at 12:20:27AM -0300, Jarbas Celante wrote:
> Hi,
>
> I'm using qmail-scanner 1.10 (1.12 too) with eTrust InoculateIT 6.0 (CAI)
> for Linux but qmail-scanner is not detects inocmd32:
Is it in your PATH?
--
Cheers
Jason Haar
Information Security Manager, Trimble Navigati
Hi,
I'm using qmail-scanner 1.10 (1.12 too) with eTrust InoculateIT 6.0 (CAI)
for Linux but qmail-scanner is not detects inocmd32:
"
Content/Virus Scanners installed on your System
Qmail-Scanner details.
log-details=syslog
fix-mime=1
debug=1
notify=sender,admin,recips
[EMAIL PROTECTED]
lo
We are having the same problem with the same version. Could it be a bug?
Trey Nolen
hi
From: "Jason Haar" <>
>
> Check your reformime version. This was a problem with old versions I
think.
>
hmmm I've used maildrop 1.4 from source ...
# reformime -v
$Id: reformime.c,v 1.40 2002/03/19 01:29
From: "Jason Haar" <[EMAIL PROTECTED]>
> A few of you have complained/noted that you didn't like that Q-S gave
out
> file and dir details as shown at the bottom of this message.
> There are (as usual) several ways to deal with this, but I want to
hear what
> people think of this one:
This is wha
At 04:38 AM 7/3/2002, Ron Culler wrote:
>You might want to add another table (domain admins) I am working on a
>patch that will add the code to the existing version. The concept is
>that much like the is_unreplyable_email function - If the sender or
>recpt. domain matches a domain in the (domain
Hi there,
I am having the famous qq temporary problem with qmail-scanner. since this
is covered in the FAQ I have tried to up the mem through softlimit without
much success.
If I set the memory below 900 I will get a permanent error, otherwise I
will get a temporary error. upping the mem
On Wed, Jul 03, 2002 at 02:45:15PM -0300, Abel Lucano wrote:
> > Everyone must remember. ALL virus scanners get bigger with
> >time. Therefore their memory requirements will ALWAYS get bigger with
> >time...
> >
>
> I'dont understand what do you mean exactly here with "..get bigger with
> time.."
On Mon, 1 Jul 2002, Jason Haar wrote:
> On Sun, Jun 30, 2002 at 09:54:33PM -0300, Abel Lucano wrote:
> > X-Qmail-Scanner-1.10: corrupt or
> > unknown Sophos scanner/resource problems - exit status 2
>
> Hmm "resource problems"...
>
> > Sophos sweep (3.58, 3.59): in every case I got an "Error
>
Marcello
Follow the instructions in "Living with QMail" religiously and it will work. You have
to adjust slightly to allow for qmail-scanner:
add an env directory under /service/qmail-smtpd and put in a file called QMAILQUEUE
which contains the path and filename to qmail-scanner-queue.pl
spl
Hi to all...
I tried too to use manually the qmail-inject from the system to send a
message and in this way the qmailscanner is triggered. If i use the smtp
connection with a Mail client it don't see the variable.
So it seems to be a problem of the way the system set the variable
QMAILQUEUE in the
Hi to all,
i have installed the qmailqueue scanner on a turbolinux system.
The test_installation -doit run properly but the system seems to not
take care of the variable QMAILQUEUE vars inserted in my startup
scripts.
I tried to insert in this script the variables and after i seen that it
don't q
13 matches
Mail list logo
