This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] Excuses
- Previous message (by thread): [anti-abuse-wg] Excuses
- Next message (by thread): [anti-abuse-wg] Excuses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
David Hofstee
david at mailplus.nl
Wed Sep 30 10:03:35 CEST 2015
Hi Marilson, Thanks for your apology, accepted on my part. Although I don't think individual cases belong in the list, I'm not sure I have seen any other content on this list at all. Which is saddening as well. Regarding abuse in general and how to police it (which is basically what it comes down to since it won't go away automatically)... I have come to a few conclusions for myself: - Every resource, such as an IP, routing via tier-1, a server or a registration at RIPE is part of abuse. - I think that after a certain threshold of complaints is generated, the resource holder must take its responsibility. It should be easy to complain against abuse. - Every resource holder should monitor for abuse and do its best to keep the resource up to spec to avoid abuse. - In abuse, even the reaction of one of the resource holders is enough to break the chain of said abuse. It takes only one. Now here is the part that sucks and RIPE does not care much about: The database of RIPE is inaccurate, it definitely is a resource, and does not work very well in (abuse) corner cases. They are not willing to break the abuse chain because they are not willing to police, for whatever reason they (or an individual) name(s). I won't say that RIPE is the only party not taking responsibility though. Now I understand that when you even struggle with the definition of abuse, it is hard to respond (don't let facts bother you, RIPE). But not keeping the registration up to spec makes it abuse-friendly. Please make it possible to break the chain of abuse! /rant David Hofstee Deliverability Management MailPlus B.V. Netherlands (ESP) Van: anti-abuse-wg [mailto:anti-abuse-wg-bounces at ripe.net] Namens Marilson Verzonden: Tuesday, September 29, 2015 8:53 PM Aan: anti-abuse-wg at ripe.net Onderwerp: [anti-abuse-wg] Excuses THE ANTI-ABUSE-WG ARCHIVES: In August 2015 the only discussion held was generated by a copy of my complaint addressed to an ISP - 13 messages In September 2015 the only discussion held was generated by a copy of my complaint addressed to an ISP - 42 messages Against the grain of these numbers I was politely warned that my messages to the list should certainly be blocked because I clearly do not understand what the list currently does. I was also warned that the list is not the place to make complaints and that I should look for spamcop in the Google search. I would like to clarify to the group that I always start my complaints in submit.snA38em0rJTkVJ7B at spam.spamcop.net<mailto:submit.snA38em0rJTkVJ7B at spam.spamcop.net>, once finalized in spamcop I send the complaint to the ISP responsible for the spammer with copies to pertinent institutions. And copy to anti-abuse-wg at ripe.net<mailto:anti-abuse-wg at ripe.net>. I copy for anti-abuse-wg at ripe.net<mailto:anti-abuse-wg at ripe.net> because I have noticed that my complaints have generated much discussion in the group. I thought I was being helpful. Since I am doing the wrong thing, I apologize to the group members and retreat myself wishing a good job for everyone. Greetings Marilson -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/anti-abuse-wg/attachments/20150930/ec00d77a/attachment.html>
- Previous message (by thread): [anti-abuse-wg] Excuses
- Next message (by thread): [anti-abuse-wg] Excuses
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]