<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=Windows-1252"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-IE" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> Please provide actual data.<o:p></o:p> Numbers<o:p></o:p> <o:p> </o:p> <o:p> </o:p> --<o:p></o:p> Mr Michele Neylon<o:p></o:p> Blacknight Solutions<o:p></o:p> Hosting, Colocation & Domains<o:p></o:p> <a href="https://www.blacknight.com/">https://www.blacknight.com/</a><o:p></o:p> <a href="https://blacknight.blog/">https://blacknight.blog/</a><o:p></o:p> Intl. +353 (0) 59 9183072<o:p></o:p> Direct Dial: +353 (0)59 9183090<o:p></o:p> Personal blog: <a href="https://michele.blog/">https://michele.blog/</a><o:p></o:p> Some thoughts: <a href="https://ceo.hosting/">https://ceo.hosting/</a><o:p></o:p> -------------------------------<o:p></o:p> Blacknight Internet Solutions Ltd, Unit 12A,Barrowside Business Park,Sleaty Road,Graiguecullen,Carlow,R93 X265,Ireland Company No.: 370845<o:p></o:p> <o:p> </o:p> I have sent this email at a time that is convenient for me. I do not expect you to respond to it outside of your usual working hours.<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <div id="mail-editor-reference-message-container"> <div> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: anti-abuse-wg <anti-abuse-wg-bounces@ripe.net> on behalf of jordi.palet--- via anti-abuse-wg <anti-abuse-wg@ripe.net> Date: Friday, 1 December 2023 at 13:38 To: anti-abuse-wg@ripe.net <anti-abuse-wg@ripe.net> Subject: Re: [anti-abuse-wg] Abuse Report ignored. What to do as next?<o:p></o:p> </div> <div> [EXTERNAL EMAIL] Please use caution when opening attachments from unrecognised sources. Well � exactly the same way it has been already implemented in 2 other RIRs, working and no issues. Regards, Jordi @jordipalet > El 1 dic 2023, a las 14:28, Laura Atkins <laura@wordtothewise.com> escribi�: > > > >> On 1 Dec 2023, at 13:22, U.Mutlu <security@mutluit.com> wrote: >> >> Laura Atkins wrote on 12/01/23 13:22: >> > None of this will make a company who doesn�t want to deal with abuse >> > complaints deal with abuse complaints. It�s a total waste of resources. >> >> Then RIPE has to sanction that member. > > So we�re back to: how much will it cost to do this and how much will it actually improve anything? > > Which ignores a lot of big questions like: does RIPE actually have the authority to sanction folks, who is going to sanction them, what is the appeals process, how do we get to the sanctioning decision, how are we going to pay for the inevitable lawsuit, and a bunch of other things. > > It�s clear, though, that this is actually a much older argument. I�m pretty sure I�m not the first person to ask HOW this will all be implemented. The fact that someone can�t point me to a FAQ or actual proposal addressing these questions tells me how seriously this is being taken by the folks who are proposing it. > > laura > >> >> Example of ignored Abuse Reports regarding email hacking attempts: >> >> You get countless hacking attempts to your email server >> (ie. brute-force attacks trying to login as a mail client >> by using either a valid email login name or some random names; >> they usually fail b/c of wrong password). >> It all gets logged in the emailserver logs together with >> exact timings, so there is enough evidence available for verification. >> >> You send an Abuse Report to the owner of the IP from where >> these hacking attempts occur.But there is no reaction, >> the hacking attemps day and night continue. So, it's not just a one-time thing. >> Even if you block that IP, it still generates traffic and eats-up resources on the server. >> >> We need an effective solution to stop such abuses. >> RIPE NCC should ask the client to fix the problem and >> formally inform the RIPE NCC about the fix within 7 days. >> >> If the Abuse Reports still get ignored, then RIPE NCC >> should issue a 2nd warning and thereafter then terminate >> or suspend the membership until the issue gets fixed. >> >> >> Laura Atkins wrote on 12/01/23 13:22: >>> None of this will make a company who doesn�t want to deal with abuse >>> complaints deal with abuse complaints. It�s a total waste of resources. >>> >>> laura >>> >>>> On 1 Dec 2023, at 10:53, U.Mutlu <security@mutluit.com> wrote: >>>> >>>> For each complaint to RIPE NCC then such an >>>> (automated) email should be sent by the RIPE NCC >>>> to the abuse-c of that member. >>>> This should be the absolute minimum that should be done by the RIPE NCC. >>>> >>>> >>>> Matthias Merkel wrote on 11/30/23 11:47: >>>>> The proposal is to send verification emails to abuse mailboxes and have a link >>>>> in them clicked, right? I would have no objection to that. >>>>> >>>>> Is there more that is being proposed in this proposal specifically? >>>>> >>>>> � >>>>> Maria Merkel >>>> >>>> >>>> >>>> -- >>>> >>>> To unsubscribe from this mailing list, get a password reminder, or change >>>> your subscription options, please visit: >>>> <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> >>> >>> -- >>> The Delivery Expert >>> >>> Laura Atkins >>> Word to the Wise >>> laura@wordtothewise.com >>> >>> Delivery hints and commentary: <a href="http://wordtothewise.com/blog">http://wordtothewise.com/blog</a> >>> >>> >>> >>> >>> >>> >>> >>> >> >> > > -- > The Delivery Expert > > Laura Atkins > Word to the Wise > laura@wordtothewise.com > > Delivery hints and commentary: <a href="http://wordtothewise.com/blog">http://wordtothewise.com/blog</a> > > > > > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a> ********************************************** IPv4 is over Are you ready for the new Internet ? <a href="http://www.theipv6company.com">http://www.theipv6company.com</a> The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it. -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: <a href="https://mailman.ripe.net/">https://mailman.ripe.net/</a><o:p></o:p> </div> </div> </div> </div> </body> </html>