A softlimit of 5000000 or 6000000 is usually enough.  it also depends on
what virus scanner you're using as well.  the more scanners, the higher the
limit.  Mine is around 8000000 because I use two scanners.

Tren.

> -----Original Message-----
> From: Bill Shupp [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, November 28, 2001 11:38 AM
> To: [EMAIL PROTECTED]
> Subject: Re: QMAILQUEUE
>
>
> On Wednesday, November 28, 2001, at 12:34 PM, Dallas Engelken wrote:
>
> > I am having a problem with qmail-scanner, maybe someone has an idea
> > here.
> > I have installed everything and did ../contrib/test_installation.sh
> > -doit
> > and those tests passed just fine.  I can also do this.
> >
> > # QMAILQUEUE=/var/qmail/bin/qmail-scanner-queue.pl
> > # echo "to:root" | /var/qmail/bin/qmail-inject
> >
> > And then I receive a message with the appropriate headers.
> > X-Qmail-Scanner: 1.01 (Clean. Processed in 1.54129 secs)
> >
> >
> > However..........
> >
> > When I try and add this QMAILQUEUE variable to my smtp supervise
> > script, and
> > then try and send a message through it, here are the results..
> >
> > --------------------------
> > [root@localhost qmail-smtpd]# telnet localhost 2525
> > Trying 127.0.0.1...
> > Connected to localhost.localdomain.
> > Escape character is '^]'.
> > 220 localhost ESMTP
> > mail from: root
> > 250 ok
> > rcpt to: root
> > 250 ok
> > data
> > 354 go ahead
> > .
> > 451 qq temporary problem (#4.3.0)
> > --------------------------
> >
> > I added just the two lines to my supervise script.
> >
> > --------------------------
> > #!/bin/sh
> >
> > QMAILQUEUE=/var/qmail/bin/qmail-scanner-queue.pl
> > export QMAILQUEUE
> >
> > QMAILDUID=`id -u qmaild`
> > NOFILESGID=`id -g qmaild`
> > MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> >
> > exec /usr/local/bin/softlimit -m 2000000 \
> >     /usr/local/bin/tcpserver -v -R -l 0 -x /etc/tcp.smtp.cdb -c
> > "$MAXSMTPD"
> > \
> >         -u "$QMAILDUID" -g "$NOFILESGID" 0 qmail
> > /var/qmail/bin/qmail-smtpd
> > 2>&1
> > --------------------------
>
> Try increasing your softlimit or not using softlimit.  I couldn't get it
> set correctly, so I stopped using softlimit.  But I didn't try that
> hard, either.  ; )
>
> -Bill
>
>

Reply via email to