lets say an email bounces so the address gets blacklisted, but its a legit email address from a real customer. customer emails in and asks why they arent getting their emails, and customer support should have the tools to handle.

sendgrid: search email address, find the bounces, click the button that says allow and user gets emails.

ses: set up an sqs queue. Pipe all bounces into a db. manage said db. Make a service with ui to search for emails. include a ui to unblock address.

That, and ses attachment size limit is a joke.

UX is huge. Sendgrid is absurdly easy to use, and at least 3 years ago, SES was an impenetrable mass to me. I got my company up and running on Sendgrid in like 20 minutes.

Maybe it's easier nowadays, but at least a few years ago it was a night and day difference.

Using it today, still complete garbage UX wise.

My least favorite aspect is that the API always claims a success even if that address is in the global blocklist, the only way to learn about bounce backs is to subscribe via SNS.

Also the UI is effectively useless.

> SES was an impenetrable mass to me

AWS UX in general is kind of a mess. Vast in its services, no doubt, but just messy.

I have an anecdote, email me if you care! Your profile doesn't have one.