>
> (Yes, SUID perl scripts are enabled!)
>
Hi, SUIDPerl is safe or unsafe?
Jarbas
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&re
I'm trying to upgrade my Perl installation to 5.8.0, and now smtp
connections die with "451 qq crashed". There are no memory limits
currently in place on qmail-scanner, and I have re-compiled all supporting
libraries (maildrop, tnef, etc..) If I run qmail-scanner-queue.pl and
feed in a messa
Sorry... I was in a rush on Friday and neglected to check the obvious
before emailing the list. :(
A quick and simple check of the quaranteened emails proved that this
IFrame acts in a similar manner to Klez in that it spoofs the email
headers.
---
Bill Arlofski
Unix/Novell Systems Administra
I noticed a while back that qmail-scanner-queue was adding a huge header
to my email messages. After help for them the list I was able to track
down the problem. Apparently H+BEDV AntiVir had changed the output from
the "antivir --version" command. This output is used to generate the
qmail-scan
You need to make sure you have installed the QMAILQUEUE patch for
qmail-1.03 so qmail-scanner-queue.pl can intercept the messages.
See:
http://qmail-scanner.sourceforge.net/
http://www.lifewithqmail.org/lwq.html#patches
Then you need to modify the /var/qmail/supervise/qmail-smtpd/run file
descri
I have installed
qmail-scanner, and it reports no errors. In the install guide i read
this:
At this stage qmail-smtpd will need to
be "told" that Qmail knows to use qmail-scanner-queue.pl instead of
qmail-queue.
i guess this is the
final step that will get tings up and running :), -but
Hi All,
I have a brand new setup here:
Red Hat 7.3
qmail 1.0.3
Spamassassin 2.31 - spamd/spamc
Clamscan 0.22
Qmail-scanner 1.13
The setup is filtering and tagging spam fine, but it is not quarantining the
klez virus as I expected it to. I (successfully) re-ran
test_installation.sh, but I conti
Jason Haar wrote:
>
> On Sun, Aug 18, 2002 at 10:49:57PM -0400, Dave Sill wrote:
> > OK, one last thought... I disabled softlimit and tried
> > again. Bingo: worked like a charm. Why the hell didn't
> > clamscan/qmail-scanner/tcpserver/perl/whatever complain that it was
> > running out of memory?
Hello Patrice,
Monday, August 19, 2002, 4:15:45 PM, you wrote:
PB> I know that lone CR are forbidden in Mime headers, but are CRLF forbidden
PB> too ?
PB> I was not able ton find something dealing with that explicitely in the RFCs.
ehmmm...try CR/LF patch for qmail (CMIIW). Try find it at qmail
Hello all,
Using QS 1.13
I know that lone CR are forbidden in Mime headers, but are CRLF forbidden
too ?
I was not able ton find something dealing with that explicitely in the RFCs.
if ($BAD_MIME && /\r|\0/) {
$illegal_mime=1;
&debug("w_c: illegal MIME chars found in header");
10 matches
Mail list logo