Every SMTP service (Mailgun, Sendgrid, Postmark, etc.) does the same things AWS does to try to prevent spam and has the same features you mention (shared IPs to start, warmup on mass sending, developer tooling, etc.)
Email delivery is a commodity business at this point, hence why there's so many PE rollups in the space.
The fact of the matter is it only takes 1 bad send to end up on a blacklist, and SES is the cheapest so it will always be the most attractive target for spammers/fraudsters.
Am I correct that maybe you run a Saas built off SES and might have incentive to defend?
But the problem is that Mailgun/Sendgrid/Postmark and the like is less senstive to spam and ban. The ban on SES is way heavier and the spam rule is stricer.
Comments
Every SMTP service (Mailgun, Sendgrid, Postmark, etc.) does the same things AWS does to try to prevent spam and has the same features you mention (shared IPs to start, warmup on mass sending, developer tooling, etc.)
Email delivery is a commodity business at this point, hence why there's so many PE rollups in the space.
The fact of the matter is it only takes 1 bad send to end up on a blacklist, and SES is the cheapest so it will always be the most attractive target for spammers/fraudsters.
Am I correct that maybe you run a Saas built off SES and might have incentive to defend?
I run a competitor of SES so I won't defend them.
But the problem is that Mailgun/Sendgrid/Postmark and the like is less senstive to spam and ban. The ban on SES is way heavier and the spam rule is stricer.
Maigun/Sendgrid even suggest to use dedicated IP pool to improve delivery, where as AWS SES doesn't https://docs.aws.amazon.com/ses/latest/dg/dedicated-ip.html https://docs.sendgrid.com/ui/account-and-settings/dedicated-... You can see the tone there.