From owner-freebsd-questions Wed Jan 21 18:57:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00428 for questions-outgoing; Wed, 21 Jan 1998 18:57:42 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from cedb.dpcsys.com (cedb.dpcsys.com [206.16.184.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00410 for ; Wed, 21 Jan 1998 18:57:31 -0800 (PST) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by cedb.dpcsys.com (8.8.5/8.8.2) with SMTP id CAA26358; Thu, 22 Jan 1998 02:57:39 GMT Date: Wed, 21 Jan 1998 18:57:39 -0800 (PST) From: Dan Busarow To: Cliff Addy cc: questions@FreeBSD.ORG Subject: Re: Preventing spam relaying In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk On Wed, 21 Jan 1998, Cliff Addy wrote: > However, it's too good now. I need OUR clients to be able to send email > and it's getting blocked. I didn't realize that Netscape talks directly You're using an old version of check_rcpt. Take a look at Claus Assman's. I have a page describing it at http://www.beach.net/~dan mainly cause I can't memorize Claus' URL :) You can specify both GOOD and BAD IP address blocks. Just put all of your address space in the LocalIP file (only understands full addresses, or traditional A, B, C subnets) and the blocks of spammers in SpamIP That gives you pretty fine grained control over who can use your sendmail (right down to a single IP #) and lets you block know spammers by IP. Dan -- Dan Busarow 714 443 4172 DPC Systems / Beach.Net dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82