From owner-freebsd-isp Sun Dec 3 18:19: 4 2000 From owner-freebsd-isp@FreeBSD.ORG Sun Dec 3 18:19:02 2000 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from andcoke.aeon.networktel.net (andcoke.aeon.networktel.net [216.83.238.151]) by hub.freebsd.org (Postfix) with ESMTP id 3417237B400 for ; Sun, 3 Dec 2000 18:19:02 -0800 (PST) Received: from localhost (phill@localhost) by andcoke.aeon.networktel.net (8.9.3/8.9.3) with ESMTP id UAA05170; Sun, 3 Dec 2000 20:19:16 -0600 (CST) (envelope-from phill@freebsd.org) X-Authentication-Warning: andcoke.aeon.networktel.net: phill owned process doing -bs Date: Sun, 3 Dec 2000 20:19:16 -0600 (CST) From: Phillip Salzman X-Sender: phill@andcoke.aeon.networktel.net To: Will Andrews Cc: Craig Shaver , isp@freebsd.org Subject: Re: Urgent: Please Read In-Reply-To: <20001202193849.M559@puck.firepipe.net> 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 If you want to really be the BOFH, you could create an allow list. Meaning, deny all, allow from, say only, freebsd.org :) Altho, your customers may not like that too much, but works great for personal email in procmail :) --- Phillip Salzman On Sat, 2 Dec 2000, Will Andrews wrote: > On Sat, Dec 02, 2000 at 04:28:14PM -0800, Craig Shaver wrote: > > Hi - how do you do that? > > Find out their upstream's abuse address (http://www.mail-abuse.net/ has > a nice database for this) and contact them. If that doesn't work, go > higher upstream. > > If you can't reach somebody to have it shutdown, then have it put on > MAPS/RSS/ORBS/etc. > > I'm not an expert at shutting relays down -- thankfully that's never > been in my job description. *grin* So take my suggestion with a grain > of salt. > > -- > wca > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message