Hey everyone! I've built an email system for a side project related to the bolt hackathon at whohasjobs.com. My testing has gone well with a friend, sending multiple emails. I clearly described how the system works when requesting production access from AWS SES. Basically, users sign up to receive emails about new job postings, but only when there are updates since their last email. It seems I've hit a roadblock, as AWS is denying my request for production access. I suspect they might think I'm sending spam, as their response noted that I shouldn't be sending unsolicited messages. Do you think that's the issue? Could it be a misunderstanding about how and when I send emails? Any advice on how to proceed, especially since I've already reopened the case and made it clear that there's a prominent unsubscribe option in the emails?
1 Answer
It sounds like you might not be fully confirming email opt-ins before sending real emails via SES. Also, handling bounces and spam complaints is crucial for approval. AWS has strict rules on SES; for a quick project, you might want to consider other SMTP services. Their requirements can be pretty intense, and it seems like you might not have some critical automated tools in place for email management.
Thanks for the insights! I do require users to verify their emails first. I initially thought AWS would be a straightforward option. Do you have any specific SMTP services in mind that are easier for projects like this?