alt Hacker NewsAlmost every SaaS (Spam as a Service) API ends up arguing its minority of legitimate users are a justified excuse for the majority of nuisance traffic.
Most cloud IP blocks already have very poor reputations, and or already on Spamhaus blacklists.
People have a right to choose to be upset. =3
My experience has been the opposite of what you're saying: AWS SES (one of AWS's flagship products, and probably the biggest email sender in the world) is a pretty responsible anti-spam citizen. Spamhaus even wrote this article[1] praising SES's anti-spam efforts. From the article: "Amazon SES has a long-standing relationship with Spamhaus, working closely to prevent suspicious IPs and domains from impacting their network." Though I'm sure that new incidents come up daily, Spamhaus themselves seem to disagree with the notion that SES's IP blocks have "poor reputations."
[1] https://www.spamhaus.org/resource-hub/service-providers/how-...