Jump to content

Keats

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by Keats

  1. I got this response from Amazon on one of the reports I sent: "We've determined that an Amazon EC2 instance was running at the IP address you provided in your abuse report. We have reached out to our customer to determine the nature and cause of this activity or content in your report" So, they've basically asked the spammer if he's spamming. I'm sure he'll give them a scrupulously honest answer...
  2. I've also started getting this rubbish in the last few weeks... On receiving each one (to my Gmail address), I do the following: Hit "Show Original", and copy the header info. Come to SpamCop and enter it, as usual. I also report the IP address(es) at abuseipdb.com Forward the original message to the following addresses: ec2-abuse at amazon.com , email-abuse at amazon.com , abuse at amazonaws.com , abuse at google.com , and network-abuse at google.com , after pasting the header info in. If the phishing e-mail purports to be from a well-known company - Costco, PayPal, Chase Bank, etc - I also forward it to whatever their abuse / anti-phishing report address is. I've noticed that the latest batches now also include cisco.com and yelp.com addresses.
  3. While amazonaws are certainly slime for refusing to accept reports from SpamCop, and refusing to act on spam reported directly to them, Google are no better: all the amazonaws spam I receive is coming from the same sender, with their scams being hosted on either storage.googleapis.com/wadrari , storage.googleapis.com/wadraritest or variants thereof - I report each one to Google, and have never received any sort of response.
×
×
  • Create New...