[alyandon]

I finally started sending anything from AWS SES straight to trash because the spam on their platform is persistent and they are non-responsive to spam reports. I was getting 30+ fraudulent/spam emails a day in just one inbox alone.

[nostrebored]

That's untrue. I can tell you that spam reports and bounces are monitored, and customers do have to go through validation of their workflows if they breach thresholds.

I had to help multiple customers who had access to SES shut off for valid use cases because they didn't handle events coming back from customers appropriately.

[alyandon]

  I can tell you that spam reports and bounces are monitored

If they are, I saw no evidence of that (except for the initial auto-response) based on the numerous spam reports I manually submitted with headers, dates/times and body content.

If you work for SES, you all aren't acting swiftly enough to shut down egregious spam operators using your platform that are making other people's lives miserable.

[dpifke]

I have never gotten a response to an SES spam report.

A quick search turns up 50 or so in my sent mail folder within the past year or two.

3 of the most recent 5 reports are all the same message content (likely the same sender, although possibly using different—maybe hacked—accounts).

By way of comparison, I've sent a similar volume of complaints to Twilio Sendgrid, received a response to every single complaint, and a random sampling of recent reports doesn't show any repeat message content.

Google doesn't even provide a way to report spam from Gmail users, which is ironic given the OP is complaining about Google's aggressive spam blocking. Spam from Gmail is comparable in volume to what I receive from SES and Sendgrid, and almost all of those messages are obvious phishing and 419 scams. (One would think one of the largest tech companies in the world would be able to implement basic filters to catch these, if they cared enough to do so.) Cf. spam from SES, which is mostly either cryptocurrency pump-and-dump, or semi-legit companies sending to spamtrap addresses that appear on publicly-indexed web pages, in WHOIS, etc. but which have been never used for real correspondence (and have obviously never opted in to any lists).

[whoknew1122]

No response != nothing being done with the report

[alyandon]

Sending the report to /dev/null would technically be doing something with the report though.

My problem is "no response to report" combined with "I continue to receive the same or substantially similar volume and types of emails from the same sender(s) from the same email provider weeks after submitting the reports" == "non-responsive email service operator".

[0ct4via]

Your experience of customers not handling events appropriately - and then having SES access revoked - does not negate or disprove alyandon's experience of getting no responses to spam reports.

You may have had a different experience, but that doesn't make their (differing) experience "untrue."

[moltar]

Not sure if this is an edge case or not. But getting approved for SES isn’t that simple. And then shut downs happen very quickly even for legitimate cases. AWS is very aggressive with SES.

[alyandon]

Maybe they care now. They certainly did not appear to care when my mailbox was getting spammed into uselessness by their customers.