I've found that the reserving the right to nullroute an offending host's
IP address for repeated spam offenses is a good intermediate step
between simple notifications and contract/circuit termination. It lets
the customer know you mean business while still preserving the
customer's account
On 31 May 2006, at 00:02, Dave Rand wrote:
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?
Not a BCP but we have a section for ISP Abuse Desks at http://
www.spamhaus.org/isp
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 :-)
I know that there was a Abuse Desk BCP working group started a few years ago.
Can
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
On 5/31/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
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
Subject: Re: BCP for Abuse Desk
(various good stuff deleted for brevity)
3d) Make sure your ToS allows nuking a spamming/abusive host.
3e) Then *use* that clause in the ToS when needed.
Each of the ISP's I worked for had such a clause. I felt it
was a double edged sword. The only
On Tue, 30 May 2006 20:51:55 CDT, you said:
3d) Make sure your ToS allows nuking a spamming/abusive host.
3e) Then *use* that clause in the ToS when needed.
Each of the ISP's I worked for had such a clause. I felt it
was a double edged sword. The only choices were to use it or
not
