Jump to content

tjsynkral

Members
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About tjsynkral

  • Rank
    Member

Recent Profile Visitors

437 profile views
  1. tjsynkral

    search-apnic-not-arin for 45.248.3.143

    Can someone point me to the nearest wall so I can bang my head against it? You're whoising ARIN for an IP in the APNIC pool (just as Spamcop is doing). Anytime you do that, you will get search-apnic-not-arin@apnic.net . APNIC is NOT an ISP. If you whois APNIC at whois.apnic.net for that IP, you will get current ISP information about 45.248.3.143. role: Manager Admin address: 485-A/15,1st floor,G.T. Road, Dilshad garden,New Delhi,Delhi-110095 country: IN phone: +91 9958033533 e-mail: support@apnainfotech.co.in admin-c: AA1235-AP tech-c: AA1235-AP nic-hdl: MA965-AP mnt-by: MAINT-IN-APNAINFO last-modified: 2016-04-29T09:31:10Z source: APNIC (edit: P.S. The abuse contact for 146.196.52.181 via APNIC is still matthew.wu@globalnetworkhk.com.)
  2. tjsynkral

    search-apnic-not-arin for 45.248.3.143

    In the case of this IP, they're trying to send mail to a black hole created to trap broken software that searched the wrong IP registry. Perhaps the abuse contact for 45.248.3.143 would like to know about the spam report and take action on it before it gets to SCBL. There's no chance that search-apnic-not-arin is a deliberate thing.
  3. tjsynkral

    search-apnic-not-arin for 45.248.3.143

    Do you not see the problem here? There is a correct abuse contact for 45.248.3.143 and search-apnic-not-arin is not it. Spamcop has a configuration error and it's searching the wrong IP registry to find a reporting address. If it was a scenario you described I expect to see a devnull.spamcop address in the contact field... not this. Does anyone who actually works on Spamcop ever look at this forum or is it just full of users who tell you that yes, Spamcop is broken you should report spam yourself instead of using it.
  4. It's happening again. https://www.spamcop.net/sc?id=z6435051222z44941cc474161f94fbf68ab9350463b1z Reports regarding this spam have already been sent: Re: 45.248.3.143 (Administrator of network where email originates) Reportid: 6767219654 To: search-apnic-not-arin#apnic.net@devnull.spamcop.net
  5. tjsynkral

    Lanset spam

    I'm sure you mean to help, but the only way to stop a spam friendly network is to block their IP's. The problem here is Spamcop has loopholes being exploited here. Spamcop needs to make adjustments to how the BL works.
  6. tjsynkral

    Lanset spam

    Here's an example: https://www.spamcop.net/sc?id=z6433446354z9a6d81052c4bdde1164e46a847d2902dz ISP has indicated spam will cease; ISP resolved this issue sometime after 1/4/2018, 5:43:54 PM -0600 Received: from unknown (HELO sabre-go.date) (70.98.78.98) by me with SMTP; Thu, 04 Jan 2018 18:46:48 -0500 The spammer sent the spam 3 minutes AFTER the "ISP resolved this issue" Clearly it is the spammer himself triggering this "resolved issue" status right before sending the spams out. Spamcop needs to stop allowing itself to be exploited like this. All 70.98.78's should be remaining in spamcop-bl as long as ANY IP in the range is sending spam.
  7. tjsynkral

    Lanset spam

    So, Lanset has been blasting spam from about 100-200 IP addresses over the past month nonstop, but by the time my reports get to Spamcop I always see this message: ISP has indicated spam will cease; ISP resolved this issue sometime after 1/2/2018, 1:39:55 PM -0600 Of course this is not true. I think Lanset should be permanently banned from using this "feature."
  8. tjsynkral

    non-functional parsing

    It seems to me like it's not being worked on at all and the Spamcop development is abandoned...
  9. tjsynkral

    Cyrillic domain in email body

    Just ran into this again. Do you guys need programming help?
  10. tjsynkral

    Cyrillic domain in email body

    At this point I've noticed the spammers know about this bug and are deliberately forming their spam to break SpamCop...
  11. IP: 146.196.52.181 Matched to email: search-apnic-not-arin#apnic.net@devnull.spamcop.net Obviously this is incorrect and Spamcop is searching whois on the wrong registry.
  12. Is the spammer actually sending from Gmail? Gmail in my experience does not respond to problem reports from Spamcop and their reputation means they don't ever get blocked by anyone. You may have better results reporting the problem directly to Gmail, and much better results by receiving spam from this person into a Gmail account and marking it as spam.
  13. tjsynkral

    search-apnic-not-arin 45.120.13.13

    Here's a fresh one. Is this forum the right place to report the problem to SpamCop? https://www.spamcop.net/sc?id=z6364989672z4dd237fee6fadb2d9e4c81613da12238z Re: 43.246.125.209 (Administrator of network where email originates) Reportid: 6636304941 To: search-apnic-not-arin#apnic.net@devnull.spamcop.net
  14. It's happening again. Re: 45.120.13.13 (Administrator of network where email originates) Reportid: 6588799207 To: search-apnic-not-arin#apnic.net@devnull.spamcop.net
  15. tjsynkral

    search-apnic-not-arin

    It's happening again. 45.249.70.4
×