> >I would highly recommended tarpitting, because there is no > way to control > that with control/databytes or perlscanner, since it is >just > 1 email being > sent with multiple rcpt to's. > >Dallas > > 1. What do you mean, "tarpitting"?
http://www.palomine.net/qmail/tarpit.html > 2. Qmail 1 message with 100 rcpt to's divides into 100 > separate messages and > send's them separately. yes, but qmail-scanner only processes the email once, before it is piped into qmail-local/qmail-remote for delivery to all 100 recips. > In my case, these messages were sent > to local users, > so each e-mail was going to be scanned with perlscanner. That is incorrect. Turn on debugging and send a message via SMTP to 10 recips.. you'll see qmail-scanner-queue.pl is only called once. > The > system crashed > because of insufficiens resources. > I can limit the maximum amount of processes the system can reach with > ulimit. I can limit the amount of mails with concurrencylocal, > concurrencyremote. What else? > Get your beating stick out and whack his ass for for sending 100 3mb files. Are you sure it is perlscan that killed your resources, and not once of the scanners qmail-scanner calls? What version of perl are you running? Do you softlimit your SMTP sessions? Dallas ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
