[54079] in North American Network Operators' Group
Re: Spam. Again.. -- and blocking net blocks?
daemon@ATHENA.MIT.EDU (Nigel Titley)
Tue Dec 10 12:28:39 2002
From: Nigel Titley <nigel@packetexchange.net>
To: Bryan Bradsby <Bryan.Bradsby@capnet.state.tx.us>
Cc: Kyle Christy <kchristy@sprint.net>,
Mark Segal <MSegal@FUTUREWAY.CA>, nanog@nanog.org
In-Reply-To: <20021210105448.B91734-100000@lark.capnet.state.tx.us>
Date: 10 Dec 2002 17:27:47 +0000
Errors-To: owner-nanog-outgoing@merit.edu
--=-qnp9yBjmRIqTK1b82rvV
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
On Tue, 2002-12-10 at 17:03, Bryan Bradsby wrote:
>=20
> > Check out www.antispews.org
> > -kyle
>=20
> There are two SPEWS lists.
>=20
> SPEWS[1] lists direct spam sources as accurately as /32
Which is the list that our corporate servers and my home lan ended up
on, despite never having sent direct spam
> SPEWS[2] includes SPEWS[1] plus collatteral damage.
Which was the rest of our address range and that of my home ISP
=20
> to clarify, nothing more.
The intent of the double spews listing is good, but it isn't adhered to
in practice.
--=-qnp9yBjmRIqTK1b82rvV
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQA99iQTP+B4VJuYb4kRAp8RAKCr8bzavImomPtFfmQgn16/fuaaGQCfV/mO
S5HXgsTudskyhPcxWtV1mUY=
=nL1p
-----END PGP SIGNATURE-----
--=-qnp9yBjmRIqTK1b82rvV--
