I'm moving away from Mailchimp because it has become expensive for a newsletter with roughly 1,200 subscribers. The planned setup is a DigitalOcean VM running Listmonk with Amazon SES handling delivery. Signup verification, bounce processing, and unsubscribe handling are configured, and the required setup steps appear complete, but Amazon denied the request to move SES out of the sandbox without explaining why. Could the denial be related to using SES for newsletter traffic, or are there additional list-management and compliance steps that need to be in place?
3 Answers
SES access reviews can be difficult to predict, and the rejection message may not reveal the exact concern. I’d avoid assuming that the optional recommendations are secretly mandatory; instead, provide as much concrete information as possible: expected daily and monthly volume, audience source, opt-in method, sample content, bounce and complaint rates if available, unsubscribe handling, and how you’ll prevent imported or purchased lists. If Amazon still declines it without useful feedback, comparing other email-delivery services may save time.
Amazon will generally want to see that list maintenance is fully automated: confirmed opt-in, bounce and complaint handling, unsubscribe processing, suppression management, and a clear explanation of how recipients joined the list. Make sure Listmonk is actually handling each of those flows rather than relying on manual cleanup, then submit a detailed production-access request describing your sending volume, content, signup process, and monitoring.
It may simply be a poor fit from Amazon’s risk-review perspective. SES can send newsletters, but a newsletter-only use case can receive more scrutiny because of unsubscribe, complaint, and list-quality risks. If the request continues to be rejected, a provider designed specifically for newsletters may be easier to get approved and may include more audience-management features out of the box.
Listmonk is set up to automate those parts, similar to what Mailchimp provides. I’ll make the request more explicit about the workflows and list-management safeguards.