From owner-freebsd-isp  Thu Jan 30 12:44:24 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id MAA00141
          for isp-outgoing; Thu, 30 Jan 1997 12:44:24 -0800 (PST)
Received: from tiac.net (root@Nashua-ppp27.Empire.Net [205.164.80.127])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA00129
          for <freebsd-isp@freebsd.org>; Thu, 30 Jan 1997 12:44:20 -0800 (PST)
Received: from tiac (pmcandre@localhost [127.0.0.1]) by tiac.net (8.7.5/8.7.3) with SMTP id UAA02093; Mon, 27 Jan 1997 20:47:14 -0500
Message-ID: <32ED5AA0.22EFA880@tiac.net>
Date: Mon, 27 Jan 1997 20:47:13 -0500
From: patrick mcandrew <pmcandre@tiac.net>
X-Mailer: Mozilla 3.0 (X11; I; Linux 2.0.0 i486)
MIME-Version: 1.0
To: Steve <shovey@buffnet.net>
CC: freebsd-isp@freebsd.org
Subject: Re: Spam from rival
References: <Pine.BSI.3.95.970130082211.24427D-100000@buffnet11.buffnet.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-isp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Steve wrote:
> 
> On Thu, 30 Jan 1997, Peter Hawkins wrote:
> 
> > Today an New York based ISP spammed our entire customer base. The
> > culprits are:"
> > Easyway Communications,Inc.
> > (www.easyway.net)
> >
> > I sent them a bill for the delivery of the mail (which I'm sure they will ignore)
> > a) what more can I do?
> > b) is it possible for us to treat such people by collectively routing
> >    their IPs to lo0 ?
> 
> You can block access at the router level, with wrappers, or with filtering
> 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.