You can subscribe to post backs from SES. These post back tell you message-by-message if a message was delivered/bounced.. so "simple" process of storing the results. Need to track the unique message ID, some you might get multiple responses for the same message (e.g. delivered, then marked spam)
There might also be a CLI call to get summary stats.
Exactly, that's what we did with our solution, too; we maintaned our own bounce list with a TTL that we kept up-to-date by subscribing to SNS notifications generated by SES.
My question was aimed towards the bounces feature presented on the app homepage [0]; if you ignore (or don't realize the importance of) the bounce rate you might shoot yourself in the foot.
You can subscribe to post backs from SES. These post back tell you message-by-message if a message was delivered/bounced.. so "simple" process of storing the results. Need to track the unique message ID, some you might get multiple responses for the same message (e.g. delivered, then marked spam)
There might also be a CLI call to get summary stats.