From owner-freebsd-isp  Thu Jan 30 14:00:45 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA04665
          for isp-outgoing; Thu, 30 Jan 1997 14:00:45 -0800 (PST)
Received: from panda.hilink.com.au (panda.hilink.com.au [203.2.144.5])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA04653
          for <freebsd-isp@freebsd.org>; Thu, 30 Jan 1997 14:00:40 -0800 (PST)
Received: (from danny@localhost) by panda.hilink.com.au (8.7.6/8.7.3) id JAA05449; Fri, 31 Jan 1997 09:01:09 +1100 (EST)
Date: Fri, 31 Jan 1997 09:01:08 +1100 (EST)
From: "Daniel O'Callaghan" <danny@panda.hilink.com.au>
To: patrick mcandrew <pmcandre@tiac.net>
cc: Steve <shovey@buffnet.net>, freebsd-isp@freebsd.org
Subject: Re: Spam from rival
In-Reply-To: <32ED5AA0.22EFA880@tiac.net>
Message-ID: <Pine.BSF.3.91.970131085946.263H-100000@panda.hilink.com.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk



On Mon, 27 Jan 1997, patrick mcandrew wrote:

> > in your freebsds.
> access control lists blocking  port 25(smtp) from that domain would be
> eaiser, if you have a router like a cisco or whatever, not a unix box.

FreeBSD can do this, probably more easily than if you have a Cisco, if 
you have IPFIREWALL in the kernel.  But that does not solve the problem 
(can you say "multiple MX records"?)

Danny