Handling email complaints and bounces? exiting AWS SES sandbox?

AI-generated summary

A user is seeking guidance on exiting the AWS SES sandbox and handling email bounces and complaints. They have submitted a support request detailing their use case—transactional emails for account registration, password resets, and user notifications—and outlined their email practices, including VERP for bounces and CloudWatch for complaint monitoring. Despite providing detailed information, their request was denied due to potential negative impact on SES service, with no further explanation provided. The user references an outdated forum thread and expresses frustration over the lack of clarity in AWS’s response. shyguy shyguy

i’ve been stuck in SES sandbox purgatory for a few days without a response except for the initial automated one.

i’m looking for two things.

  1. tips on how to get out of sandbox and
  2. how do i actually achieve what they want in terms of handling bounces and complaints?
    • assuming i can get VERP working, that handles bounces in an automated way. i would think that’s fine for them.
    • how are complaints handled in an automated, closed-loop way though? what answer are they looking for?

i saw this topic, and it sounds like the instructions might be out of date:

here’s my support ticket

thanks

it was denied! darn.