From owner-freebsd-isp Sat Dec 12 23:32:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25246 for freebsd-isp-outgoing; Sat, 12 Dec 1998 23:32:04 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from excelsior.apana.org.au (excelsior.apana.org.au [203.11.114.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25203 for ; Sat, 12 Dec 1998 23:31:51 -0800 (PST) (envelope-from dean@odyssey.apana.org.au) Received: from odyssey.apana.org.au (odyssey.apana.org.au [203.11.114.1]) by excelsior.apana.org.au (8.8.8/8.8.8) with ESMTP id PAA03910; Sun, 13 Dec 1998 15:30:45 +0800 (WST) (envelope-from dean@odyssey.apana.org.au) Date: Sun, 13 Dec 1998 15:30:45 +0800 (WST) From: Dean Hollister To: Rowan Crowe cc: freebsd-isp@FreeBSD.ORG Subject: Re: sendmail morons In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 13 Dec 1998, Rowan Crowe wrote: > If it's a machine performance issue then you could try limiting the number > of children: > > # maximum number of children we allow at one time > O MaxDaemonChildren=30 > > If it's for a major mail server then I would _not_ recommend this, as once > the limit is reached all connections to port 25 will be refused. I had a > play with this the other day when someone decided to forward 150Mb+ of > their email from work to their home account, and it was severely loading > the system. I would *not* recommend this. It would be better to configure the child process to exit if the IP is in its db. I vaguely recall something at www.sendmail.org about it. > Otherwise, you could ipfw deny the IP [range], or do it at a higher level > with sendmail as another poster suggested. Or even better, use smtpd. Then run tcp wrappers above it. Regards, d. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message