[90528] in North American Network Operators' Group
Re: BCP for Abuse Desk
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Tue May 30 19:00:06 2006
To: dlr@bungi.com (Dave Rand)
Cc: nanog@merit.edu
In-Reply-To: Your message of "Tue, 30 May 2006 15:02:21 PDT."
<m1FlCI9-008hEPC@rdaver.bungi.com>
From: Valdis.Kletnieks@vt.edu
Date: Tue, 30 May 2006 18:59:03 -0400
Errors-To: owner-nanog@merit.edu
--==_Exmh_1149029910_3454P
Content-Type: text/plain; charset=us-ascii
On Tue, 30 May 2006 15:02:21 PDT, Dave Rand said:
> Of late, I have found many large ISPs that are employing anti-spam filters on
> their abuse@ addresses.
>
> Needless to say, they seem surprised that their customers have any abuse
> issues involving spam at all :-)
Paging Randy Bush - one of your competitors is on the phone... :)
> I know that there was a Abuse Desk BCP working group started a few years ago.
> Can anyone give me an update on BCP practices that I can refer ISPs to?
http://asrg.sp.am/subgroups/bcp.shtml says:
"Previous BCP subgroup has been active from September of 2003 until December of
2003 when it was shutdown due to lack of active members. This subgroup is
currently in formation, will be restarting as soon as we have enough interested
participants."
Oooh... Kaay..
Really though, all the BCP you need is:
1) Make sure the 'postmast@' and 'abuse@' addresses accept mail and actually
go to live people that can take action (rather than routing to /dev/null or
bouncing because the mailbox is full).
2) Don't put a spam filter in front of the spam reporting address.
3) Take *meaningful* action that actually fixes the problem.
3a) Don't send back a "this spam isn't from us" canned message when the
headers clearly show it came from you, etc....
3b) No pink contracts.
3c) Do a basic check on new customers. http://www.spamhaus.org/Rokso/ is
a good start.
3d) Make sure your ToS allows nuking a spamming/abusive host.
3e) Then *use* that clause in the ToS when needed.
--==_Exmh_1149029910_3454P
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Exmh version 2.5 07/13/2001
iD8DBQFEfM4WcC3lWbTT17ARAicSAJ9POJQmkc8+UGIS3p7fo2iz4+Lp+wCguwi/
qFS1SMG8VG4BsSp2s9RNAyc=
=8j0M
-----END PGP SIGNATURE-----
--==_Exmh_1149029910_3454P--
