[48213] in North American Network Operators' Group
Re: Controlling Spam to the NOC
daemon@ATHENA.MIT.EDU (jlewis@lewis.org)
Sat May 25 00:24:46 2002
Date: Thu, 23 May 2002 17:17:18 -0400 (EDT)
From: <jlewis@lewis.org>
To: <measl@mfn.org>
Cc: Jeff Workman <jworkman@pimpworks.org>, <nanog@merit.edu>
In-Reply-To: <Pine.BSF.4.21.0205231600040.19726-100000@greeves.mfn.org>
Message-ID: <Pine.LNX.4.30.0205231713220.10407-100000@redhat1.mmaero.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Errors-To: owner-nanog-outgoing@merit.edu
On Thu, 23 May 2002 measl@mfn.org wrote:
> <ramble>
> You hit it dead on: use all the tools at your disposal, but preemptively
> "whitelist" your customers. Unfortunately, the whitelisting isn't always as
> easy as it sounds. If they are within your IP space, you're good to go, but
> if they have the rare portable block, or they are multihomed, etc., you need
> to be more careful.
> </ramble>
>
> In Short: Whitelist like crazy, and then blacklist like mad!
We do both...but I wouldn't say whitelist like crazy. More like whitelist
as needed, and find a blacklist or one of the message body parsing utils
you like...or both.
For the rare emergency when a customer (or non-customer) needs to talk to
our NOC and can't get email through, we have these neat things called
telephones. They work pretty well. In fact, I think mine often works too
well.
--
----------------------------------------------------------------------
Jon Lewis *jlewis@lewis.org*| I route
System Administrator | therefore you are
Atlantic Net |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
