Jump to content

Steve

Membera
  • Posts

    140
  • Joined

  • Last visited

About Steve

  • Birthday 03/26/1985

Profile Information

  • Gender
    Male
  • Location
    Long Island, NY

Recent Profile Visitors

2,211 profile views

Steve's Achievements

Advanced Member

Advanced Member (3/6)

0

Reputation

  1. Manually reporting the email to abuse AT messagelabs DOT com (which is what the parser determines is the POC for this IP address and consequently refreshing the cache also displays) results in Messagelabs' mailer-daemon to come back with this result: https://www.spamcop.net/sc?action=rcache;ip=85.158.142.120 Tracking URL: https://www.spamcop.net/sc?id=z6923785699z10c23d9ee01c64bf64ccc0f8056969b2z Does anyone know the correct POC to report abuse to for this IP string 85.158.142.0 - 85.158.142.255? Steve
  2. Same here.
  3. https://www.spamcop.net/sc?id=z6908293512z9801fb2a05396e75142452408d71c2a7z The abuse contacts for 2001:288:3001:17:0:0:0:12 are invalid. Gmail's mailer-daemon sent back an "Address not found" response for both Abuse POCs: SC dev/nulls the email addresses, but I've gone ahead and reported this to APNIC. Only time will tell if they update their database with valid contacts.
  4. https://www.spamcop.net/sc?id=z6905627030zd74fc2682bd8124aff38d930ac44f277z The following email addresses came back as undeliverable by Google's Mailer-daemon (I manually reported the spam to the addresses SC's parser determined is responsible to handle abuse. Refreshing the cache did nothing to show the correct addresses): abuse AT sonicduo DOT com, noc AT sonicduo.com, abuse AT megafonmoscow DOT ru, top-ip-support AT megafonmoscow DOT ru, and sib-abuse AT megafon.ru (domains cannot be found) The only address that didn't bounce was abuse-mailbox AT megafon DOT ru.
  5. I'm getting the same thing when using SC to report a spam email to Plala and Dion: Tracking URL and screenshot for Plala: https://www.spamcop.net/sc?id=z6904687565z0021e111f0f5e046e68d701aac6ce83az Tracking URL and screenshot for Dion: https://www.spamcop.net/sc?id=z6904736377ze33822d2a3200ff6fa8469083c521061z
  6. I did email the deputies immediately after I posted the reply. Maybe they fixed the parser for this IP address?
  7. Delivery failed permanently to fbl-spamcop AT ext DOT godaddy DOT com. Can the deputies please fix the parser so that Godaddy IP addresses shown in spam get sent to the correct address?
  8. https://www.spamcop.net/sc?id=z6901005417z982a756d7c2815468eab3e566ee4b505z https://www.spamcop.net/sc?id=z6901005150z1ce0d66a6c58975f95660ee079afb428z https://www.spamcop.net/sc?id=z6901004892zba269beaee90905a3a1cb87e9d171e57z https://www.spamcop.net/sc?id=z6901003274za9f57c81085ea73417041569439a236dz Upon attempting to report several spam emails to godaddy (SC's parser determines fbl-spamcop AT ext DOT godaddy DOT com is the Abuse POC) Gmail's mailer-daemon sends this auto-reply Refreshing the cache does nothing to fix this.
  9. Tracking link: https://www.spamcop.net/sc?id=z6899652201z91a7397fd3218a04d27789c0294a4c45z I reported the email to abuse AT mtnnigeria DOT net and customercare AT mtnnigeria DOT net using SC and manually. Reporting manually resulted in this message from MTN's postmaster:
  10. What I found, is they (plala) have stopped sending replies to reports that action was taken against the offending subscriber.
  11. HERE's the actual tracking URL: https://www.spamcop.net/sc?id=z6895557471zc44d078afa7e21e08c705d94f974c9c8z. This should help. Steve
  12. Post has been edited to show tracking url.
  13. I reported the email in the tracking link: https://www.spamcop.net/mcgi?action=gettrack&reportid=7329371122 (I also manually reported it to OCN) using SC on 4/24/24 and just got a response from them which I will put below: I went to the links but am unsure on how to proceed to send it to the appropriate team, I guess? Steve
  14. https://www.spamcop.net/sc?id=z6894784019z32eae73f09e4cd0e3dfd9e5bf8da549ez I manually reported the spam to abuse AT timbrasil DOT com DOT br with the IP address 177.30.108.45 as Amazon determined that's where the email originated from (SC parses the email and uses 35.89.44.37 as the IP address to report spam with to abuse AT amazonaws DOT com) This is the reply when I manually report the email to Amazon using 35.89.44.37: Reply from timbrasil postmaster address:
  15. https://www.spamcop.net/sc?id=z6892951213zb63f6e4d8eab8744c73323c82d4deb01z Manually reporting spam in above tracking link to abuse AT ttnet DOT net DOT tr (SC's parser determines this is one of the abuse POCs for this IP address) results in Gmail's mailer-daemon returning with this result: Running a query through RIPE doesn't show that email address as a POC: https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=91.220.182.196&source=RIPE Refreshing the cache does nothing to remove this address from the parse. Can the Deputies remove this address (abuse AT ttnet DOT net DOT tr) as the domain is no longer active? As determined by the RIPE query, abuse AT doruk DOT net DOT tr is the correct abuse POC for this IP address. Steve
×
×
  • Create New...