Any point in reporting spam from AMAZONAWS?

[MDMesser001 0]

About 95% of my spam ends up showing AMAZONAWS as the source.

I've been reporting it regularly but I always get more.  

I've been pleased with results from most of the other spam I get.  I forward it to Spamcop.net and I rarely see it come from that source again.  But AmazonAWS seems exempt.

[petzl 0]

8 hours ago, MDMesser001 said:

About 95% of my spam ends up showing AMAZONAWS as the source.

I've been reporting it regularly but I always get more.  

I've been pleased with results from most of the other spam I get.  I forward it to Spamcop.net and I rarely see it come from that source again.  But AmazonAWS seems exempt.

Yes show a tracking URL

[Lking 0]

Unless your ISP uses the SpamCop Blocklist to filter/sort your incoming email, you will not see a direct affect in your inbox for submitting spam. 

[showker 0]

Yes, we believe it helps to report.   I've been tracking them and if you follow SafeNetting or UGNN on Facebook or any of the "News" social medias you've seen my "Amazon complicit with Cyber Crime Cartels" alerts and warnings.  

Yet, when we report, it's the last time we get spam from that particular IP and domain.  Yes, they switch -- and have a billion opportunities to continue switching -- but I do believe those reports get some attention.   I have been unable to reach a spokesperson, it seems to all be automated without human intervention.

Cloudflare is much worse.  They actually admit that they are getting rich off cyber crime and nobody seems to care enough to speak up.   I contacted a major, national law firm to launch a class action suit, but they said the judges have so little knowledge of technology that they believe the Amazon, Google and Cloudflare yarn about having nothing to do with the content. 

Why is Google blocking Amazon?
https://medium.com/@showkster/why-is-google-blocking-amazon-d912e4b26ab2

 

 

[Lking 0]

I get auto response for all the spam reports I send to Amazon. I don't track the IPs or spend to much time looking at the the spam so don't know what effect it has.

As in other threads, No the spam is not going away. As long as people respond to spam, with money or political action, spam will continue. SpamCop never really expected spam to stop. There first objective has always been to block the spam.  Like the spammers them self, there will always be ISPs that will take spammer's money.

[its8up 0]

You could manually forward spam reports, but the people in the abuse@amazonaws department are USELESS.  Try sending a copy of the full header/email to stop-spoofing@amazon dot com.  Every time I've done that it all stops in a few days and can take as long as a week or more to return in the same numbers.

 

Yo spamcop!  Amazon owns amazonaws.  Any chance you could start forwarding amazonaws spam to a better Amazon owned abuse address that will actually do something about it?  Seriously -- I've had great results with stop-spoofing.

[MDMesser001 0]

Thanks, its8up, I appreciate your input.  In fact, my spam from amazonaws has dropped off pretty significantly over the last few weeks.  Hopefully that means they've taken some action to cut down on spam.

[its8up 0]

You lucky dog!  Mine always drops to nil after manual reporting, then comes right back.

Several weeks back I had a chat with Amazon about Spamcop and they replied with genuine interest and whatnot.  This may have led to better communication with spamcop and some overall Amazon spam activity reduction, though I cannot be certain.  Unfortunately, as I'm sure you've noticed, spamcop still sends amazonaws reports to the trash which is a clear indicator that the amazonaws department is not active in this process.

My reporting from gmail to spamcop is automated on 3 accounts.  Automating direct mailings for amazonaws is not simple due to the vast number of small IP ranges they own.  Going back through spam to locate amazonaws mail for manual reporting is a real hassle, and the nuances of spamcop's IPv6 fiasco certainly does not help identify which of the 3 reporting accounts is the source.

Lacking any other automated choice, my fight against the amazonaws bad apples now includes mailings to their favorite URL shorteners, image hosts, and spoofed domain hosts.  Hootsuite is the absolute best about quickly redirecting their ow.ly and owl.li links to nothing, and ddnsfree is pretty quick about dropping/resetting domains.  Bit.ly and lnkd.in do OK too.  Others, including amazonaws image and link hosting, not so much.

Good luck in your spam battle!

[RobiBue 0]

Well, amazonaws spam reports get sent to /dev/null in my case:

https://www.spamcop.net/sc?id=z6503507988zf04f1366f6ca8e5a872324eb4f96d690z

Tracking message source: 54.180.88.238:

Routing details for 54.180.88.238
[refresh/show] Cached whois for 54.180.88.238 : abuse@amazonaws.com
Using abuse net on abuse@amazonaws.com
abuse net amazonaws.com = abuse@amazonaws.com
Using best contacts abuse@amazonaws.com
Reports disabled for abuse@amazonaws.com

Using abuse#amazonaws.com@devnull.spamcop.net for statistical tracking.

[petzl 0]

1 hour ago, RobiBue said:

Using abuse#amazonaws.com@devnull.spamcop.net for statistical tracking.

The REAL abuse address is "ipmanagement[at]amazon[dot]com"  

[Lking 0]

17 minutes ago, petzl said:

The REAL abuse address is "ipmanagement[at]amazon[dot]com" 

The current refresh (just now) shows - as you suggest

Quote

Re: 54.180.88.238 (Administrator of network where email originates)

ipmanagement{AT}amazon{DOT}com"

It is a dynamic system.

[petzl 0]

8 minutes ago, Lking said:

It is a dynamic system.

OK must be a long time-lag? I also refreshed cache ?

[RobiBue 0]

35 minutes ago, Lking said:

The current refresh (just now) shows - as you suggest

It is a dynamic system.

Does this mean, that I should [refresh/show] every cached whois of every report?

thanks for the heads-up

[petzl 0]

8 minutes ago, RobiBue said:

Does this mean, that I should [refresh/show] every cached whois of every report?

Should work now until the abuse address changes and SpamCop does not have it "hard coded" as a abuse address.

[MIG 0]

I still get abuse#amazonaws.com@devnull.spamcop.net; so, I submit via SC & manually forward all spam email to ec2-abuseATamazonDOTcom

Amazon are very responsive to this method.

[RobiBue 0]

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

[lisati 0]

On 1/15/2019 at 12:49 AM, RobiBue said:

I started doing that too for every amazonAWS spam.

 

Good suggestion, I might start doing that too.

[klappa 0]

I've constantly reporting and they even promised to resolve the issue or spammer that hosted it's domains on their services. But still i get spam from the spammer. Are they doing it for the money?

[RobiBue 0]

yeah, pretty sure there's money involved. if someone complains they'll probably slap them on their wrist... if too many complain, they'll probably close the account, but the spamvertiser can easily open a new account and start anew...