[49268] in North American Network Operators' Group
Re: Controlling Spam to the NOC
daemon@ATHENA.MIT.EDU (Karsten W. Rohrbach)
Thu Jun 27 12:28:33 2002
Date: Thu, 27 Jun 2002 18:28:22 +0200
From: "Karsten W. Rohrbach" <karsten@rohrbach.de>
To: Jeff Workman <jworkman@pimpworks.org>
Cc: nanog@merit.edu
In-Reply-To: <0.1022186468@kyle>; from jworkman@pimpworks.org on Thu, May 23, 2002 at 04:41:08PM -0400
Errors-To: owner-nanog-outgoing@merit.edu
--lEGEL1/lMxI0MVQ2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Jeff Workman(jworkman@pimpworks.org)@2002.05.23 16:41:08 +0000:
>=20
> Hello,
>=20
> Has anybody on this list figured out an effective way to eliminiate, or a=
t=20
> least severely limit, the amount of spam that arrives in your NOC? I am=
=20
> aware of solutions such as Spamassassin, Vipul's Razor, and the various R=
BL=20
> lists, but has anybody used one of these solutions, or anything else, to=
=20
> reduce the amount of spam going into noc@/trouble@/etc mailboxes without=
=20
> severely restricting the rest of the internet's ability to reach the noc=
=20
> via email for legitimate purposes? Particularly in a NOC where it's quit=
e=20
> possible that some of your customers are listed in the RBLs but still nee=
d=20
> to reach you.
TMDA as per-account or generic delivery filter (depending on your MTA
setup), with a whitelist of known customers (which should be easy to
derive from a CRM backend or customer address database and a few lines
of shell voodoo).
regards,
/k
--=20
WebMonster Community Project -- Reliable and fast since 1998 -- All on BSD
http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.apache.=
de/
GnuPG: 0xDEC948A6 D/E BF11 83E8 84A1 F996 68B4 A113 B393 6BF4 DEC9 48A6
REVOKED: 0x2964BF46 D/E 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46
REVOKED: 0x4C44DA59 RSA F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44
My mail is GnuPG signed -- Unsigned ones are bogus -- http://www.gnupg.org/
Please do not remove my address from To: and Cc: fields in mailing lists. 1=
0x
--lEGEL1/lMxI0MVQ2
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Comment: For info see http://www.gnupg.org
iD8DBQE9Gz0ms5Nr9N7JSKYRAgI1AKCvB3PloYAMtIR5u2Im8xu3lawxngCgoUKR
2vigUhXYXJ9oMs9Ua4De9N8=
=iL89
-----END PGP SIGNATURE-----
--lEGEL1/lMxI0MVQ2--
