Jump to content
Sign in to follow this  

munging cloudflare spammed links

Recommended Posts

I would like to propose a change in SpamCop's handling of cloudflare links.

1. when looking up the whois for the domain, or test the link, do not use the full path, only use the domain name, as a visitor trigger trap causes more spam to be sent as soon as the report is performed.

I munged for that purpose every link in my "cloudflare" spams:





and so on and so forth.

it would be grand if SpamCop could do this automagically.

Share this post

Link to post
Share on other sites

I would like to second this change request with respect to any full path of web links as they can be linked to the recipient..  I was recently hit by one of these bots from AWS a month ago and received hundreds of spam until I saw this post from RobiBue and stopped all SpamCop processing on them. Once I stopped reporting them to SpamCop, they stopped immediately. 

I received another one this morning and unfortunately I didn't catch the source and bot servers and now I have received 50 of them in on swoop.


Too many to mung up for my liking.  I simply sent them to all other anti-spam agencies and skipped SpamCop.


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this