- Newest
- Most votes
- Most comments
It honestly feels like AWS no longer cares about the reputation of its own service. I work as a freelancer helping companies set up Amazon SES, and every day I see the results of this problem: worse deliverability, emails going to spam, and more complaints from clients. AWS is not only failing to stop spammers — it is making normal businesses pay for the damage. For a company this large, it is hard to understand how such a broken system is still allowed to continue.
answered 6 days ago
at this point ses production access feels less like a security review and more like a lottery. congratulations, your account has been randomly selected to send emails — please ignore the suspicious guy who just created 67 accounts yesterday
answered 6 days ago
I was wondering about the same thing and would like to hear more experiences from other SES users. We are currently evaluating Amazon SES for our infrastructure and have seen some discussions about shared IP reputation and deliverability concerns.
It would be helpful to understand whether these are individual cases or if there are broader issues affecting senders. Hopefully someone with recent experience can share their results or AWS can provide some clarification.
answered 6 days ago
this is one of the things that makes me concerned about the shared ip reputation issue. has anyone actually received an official aws transactional email in their spam folder? i mean emails like mfa codes, password resets, account verification, etc. if aws-generated emails are also being filtered as spam, that would be pretty concerning for anyone relying on ses for critical transactional emails.
answered a day ago
Relevant content
asked 3 days ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 6 months ago

yeah, if you mean i encountered emails sent through aws/amazon ses landing in my spam folder because of a bad shared ip, then yes, i did encounter that. but if you're asking if i personally sent a lot of emails through ses and had them go to spam, idk. i still dont have production access approved, so i havent been able to use ses for sending yet