Lanset spam

[tjsynkral]

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."

[petzl]

A tracking URL would help? You can alway submit the spam yourself

Top of page before you submit 

[tjsynkral]

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.

[petzl]

SpamCop does not send reports to that IP so no one has "resolved issue" unless someone has sent to a working address?  so you can try manually send/forward  spam to abuse@lanset.com sales@lanset.com, also "upstairs"  customerservice@integratelecom.com.  (NETWORK OWNER) Try the supposed unsubcribe link the US does not recognise spam if it has a working unsubscribe link. You can also include report to US cert https://www.us-cert.gov/contact-us

include in comments "your servers are spewing spam gibber all over the world me included. your abuse desk seems asleep at the wheel?"

https://www.spamcop.net/w3m?action=checkblock&ip=70.98.78.98

Other hosts in this "neighborhood" with spam reports

70.98.78.11 70.98.78.12 70.98.78.13 70.98.78.14 70.98.78.15 70.98.78.16 70.98.78.20 70.98.78.21 70.98.78.22 70.98.78.23 70.98.78.25 70.98.78.26 70.98.78.27 70.98.78.2870.98.78.29 70.98.78.30 70.98.78.31 70.98.78.33 70.98.78.35 70.98.78.36 70.98.78.37 70.98.78.38 70.98.78.39 70.98.78.40 70.98.78.41 70.98.78.42 70.98.78.43 70.98.78.4470.98.78.46 70.98.78.48 70.98.78.49 70.98.78.50 70.98.78.51 70.98.78.52 70.98.78.53 70.98.78.54 70.98.78.55 70.98.78.56 70.98.78.57 70.98.78.58 70.98.78.59 70.98.78.6070.98.78.61 70.98.78.62 70.98.78.63 70.98.78.64 70.98.78.65 70.98.78.66 70.98.78.68 70.98.78.69 70.98.78.70 70.98.78.71 70.98.78.72 70.98.78.73 70.98.78.74 70.98.78.7570.98.78.76 70.98.78.77 70.98.78.78 70.98.78.79 70.98.78.80 70.98.78.81 70.98.78.82 70.98.78.83 70.98.78.84 70.98.78.85 70.98.78.86 70.98.78.87 70.98.78.88 70.98.78.8970.98.78.90 70.98.78.91 70.98.78.92 70.98.78.94 70.98.78.95 70.98.78.96 70.98.78.97 70.98.78.99 70.98.78.100 70.98.78.101 70.98.78.102 70.98.78.103 70.98.78.104

 

 

 

[tjsynkral]

9 hours ago, petzl said:

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.