look, i and others are trying to get ripe ncc to actually fix a rather lackadaisical attitude to ip allocation and whois accuracy what you are doing here seems to be using the list as an abuse desk substitute for reaching an isp with ip space in malaysia, which last i checked was still getting ip space from apnic, not ripe --srs (iPad) On 12-Apr-2012, at 17:21, "Reza Farzan" <rezaf@mindspring.com> wrote:
Hello Laura,
Reading most of the comments posted here, I see that most, if not all, want a clear accountability from the networks that provide our link to the Internet. Certainly, the RIPE NCC Report Form is a good start.
But as so many have stated the lack of accountability and sheer indifference on behalf of some networks in handling Abuse / Spam reports. A case in point that I like to bring to everyone's attention is Maxis Communications Bhd, in Malaysia.
Since 2009, I have traced and reported Abuse violations to Maxis Communications Bhd abuse team [ABUSE@maxis.com.my], but I just discovered that this network had ignored all my previous violations reports, as I just received the following "Not read" and "deleted without being read" confirmation notices in my inbox:
To: Mail Abuse For Maxis Communications Bhd; Cc: Federal Trade Commission; junk@brightmail.com; nonregistered@coldrain.net; spam@mailpolice.com; spam@sendusspam.com; submitspam@fortinet.com; abuse@craigslist.org; postmaster@craigslist.org Subject: REPORTING SPAM Sent: Thu, 15 Apr 2010 18:23:44 +0800
was deleted without being read on Thu, 12 Apr 2012 19:03:21 +0800
++++
To: Mail Abuse For Maxis Communications Bhd; Cc: Malaysian RMP; Federal Trade Commission; junk@brightmail.com; nonregistered@coldrain.net; report@dcm.mailprove.com; spam@mailpolice.com; spam@sendusspam.com; submitspam@fortinet.com Subject: Spam: REPORTING SCAM/FRAUD Sent: Tue, 1 Sep 2009 06:47:31 +0800
was deleted without being read on Thu, 12 Apr 2012 19:12:52 +0800
++++
To: Mail Abuse For Maxis Communications Bhd; Cc: Federal Trade Commission; junk@brightmail.com; nonregistered@coldrain.net; report@dcm.mailprove.com; spam@mailpolice.com; spam@sendusspam.com; submitspam@fortinet.com Subject: REPORTING SPAM Sent: Mon, 27 Jul 2009 18:49:27 +0800
was deleted without being read on Thu, 12 Apr 2012 19:15:08 +0800
++++
To: Mail Abuse For Maxis Communications Bhd Cc: Federal Trade Commission; junk@brightmail.com; nanas@killfile.org; nonregistered@coldrain.net; report@dcm.mailprove.com; spam@mailpolice.com; spam@sendusspam.com; submitspam@fortinet.com Subject: REPORTING SPAM Sent: Thu, 23 Apr 2009 19:46:12 +0800
was deleted without being read on Thu, 12 Apr 2012 19:12:51 +0800
++++
To: Mail Abuse For Maxis Communications Bhd; Cc: Federal Trade Commission; junk@brightmail.com; nanas@killfile.org; nonregistered@coldrain.net; report@dcm.mailprove.com; spam@mailpolice.com; spam@sendusspam.com; submitspam@fortinet.com Subject: Spam: REPORTING SCAM/SPAM Sent: Thu, 7 May 2009 08:23:39 +0800
was deleted without being read on Thu, 12 Apr 2012 19:12:51 +0800
++++
As these confirmations show, a network like Maxis Communications Bhd can simply choose not to respond, and completely ignore network violations reports, and after a few years [yes, YEARS] delete such reports as if nothing had happened.
To be fair, I have copied this network's technical contact Muhadzir Abdul Majid [zay@maxis.com.my] as well as their Whois only contact, Chiau Tik Tan [cttan@maxis.net.my] so that they can for themselves what actually happens when someone reports and sends an abuse report to Maxis Communications Bhd.
Thank you,
Reza Farzan rezaf@mindspring.com