Jump to content

RobiBue

Membera
  • Content Count

    112
  • Joined

  • Last visited

Community Reputation

0 Neutral

About RobiBue

  • Rank
    Advanced Member

Recent Profile Visitors

333 profile views
  1. Well, after several months of complaining and work-arounds, the SC update to v 5.0.0 finally did it (at least one part of this post's problem): IPv6 6to4 WORKS!!! 🤩
  2. and six hours after my post: Drum Roll 🥁 SpamCop v 5.0.0 © 2019 Cisco Systems, Inc. All rights reserved. and better: Gmail's fess-up with IPv6 6to4 WORKS!!!! 🤩 no release notes (yet) but at least some good news !!!
  3. it might have been, because: drum roll please.... tadaaaa.... SpamCop v 5.0.0 © 2019 Cisco Systems, Inc. All rights reserved. Here is your TRACKING URL - it may be saved for future reference: https://www.spamcop.net/sc?id=z6513281086z5dbadb8092da4e5415ec84737bfedba2z and the gmail IPv6 6to4 WORKS 🤩 Thank you Cisco! (took a while, but you finally figured it out without compromising the system 😉 )
  4. I don't think the update happened: I get: SpamCop v 4.9.0 © 2019 Cisco Systems, Inc. All rights reserved. and the gmail IPv6 6to4 address is still breaking the parser (although I don't know if they'll ever fix it...)
  5. RobiBue

    Any point in reporting spam from AMAZONAWS?

    I started doing that too for every amazonAWS spam. I am not sure how effective they are, as their case numbers keep changing for every report and every other reply. reporting to them gives me a case number, but when they reply about the action (which they can't tell me) they have yet another case number, and when I submit the same IP address a few days later (from a new spam) they give me yet another case number, so in this sense, I have no idea how they can even track their own cases... although I have been able to get a live person answer there... so they do read the stuff they get...
  6. RobiBue

    spam reporting question

    Sorry about that, I just copied the link without testing it "stand-alone" it was supposed to be https://www.cert-in.org.in, and then clicking on the link in the left menu [* Incident Reporting] (which ends up being that .jsp link that seems to go nowhere without context...) Confirmation of Spammer's Rules Rule #3: Spammers are stupid, and Spinosa's Corollary: Spammers assume everybody is more stupid than themselves. well, all I can say now: it works, and if it works for you , then great 👍 mission accomplished!
  7. RobiBue

    spam reporting question

    btw, if you click on [past reports] tab/button/link, you can find past TRACKING URLs by clicking on the number link provided for the report, and then on the [parse] link in the resulting screen. just for future reference
  8. RobiBue

    spam reporting question

    same as garbage can (a.k.a. /dev/nul) adding a report to incident@cert-in.org.in is described in https://www.cert-in.org.in/SecurityIncident.jsp from https://dnslytics.com/ip/103.111.41.221, I would add a report to the ASN abuse found through https://dnslytics.com/bgp/as132779 as well... that is, a report also to 'admin@rackbank.com' at least for the spam just provided in https://www.spamcop.net/sc?id=z6512015168z11faf14ef668f295d00a184d7761a5a0z
  9. RobiBue

    spam reporting question

    Hi ArtmakersWorlds, I suppose you are talking about the IPv6 address in the email header's "Received:" line beginning with "2002:", otherwise it would be helpful if you could post the "TRACKING URL" you received when submitting the spam to better understand what you mean. i.e. the URL you receive when reporting the spam (my link depicted in indigo purple) If it's the IPv6 (6to4) address, then see the threads here and here about the reasons why some of it isn't working and what Google is or isn't doing about it... HTH
  10. I believe that is the upstream "himself"... (couldn't find an upstream but APNIC themselves)... it's probably time to report to APNIC that the reporting email address is invalid... that pradeep guy has a huge IPv6 block ... he's probably admin[at]robosapi.com anyway
  11. Parswn67 probably meant to "re-post" Farelf's post from 2013 but something must have gone wrong, so here's the link as a reminder ;)
  12. RobiBue

    leaseweb spam

    <sfx mode="whisper, crowd"> YAY!!! </sfx>
  13. Abuse contact for '185.207.36.0 - 185.207.36.255' is 'info[at]fiberserver.net.tr'
  14. RobiBue

    leaseweb spam

    on 12/01/2018: http://forum.spamcop.net/topic/31073-abuse-contact-for-209581840-20958191255 and http://forum.spamcop.net/topic/31072-abuse-contact-for-209581760-20958183255 https://www.spamcop.net/sc?id=z6505161826z64add7cea35b443dd4f168a08a7582b8z even refreshing seems not to work. As I said, I wish SC would be able to get the abuse address from the correct registry... which in this case is APNIC, not ARIN...
  15. RobiBue

    leaseweb spam

    for a while now I have been getting some spam from one or more leaseweb customers ([209.58.179.227], [209.58.179.237], and [209.58.179.238].) unfortunately, there are (at least) two problems here: the IP addresses involved are listed with ARIN pointing to " search-apnic-not-arin@apnic.net " and I simply do not understand why SpamCop cannot understand the transfer mechanism and search for the abuse address within APNIC. even if it would look up APNIC, leaseweb would probably end up being /dev/nulled... (see [5.79.74.138] ) anyway, manually reporting (with my anti-spammer email address) I have, after about 5 spams and 6 back and forth messaging their abuse desk (in Singapore -- I believe), managed the following 🤩
×