- Newest
- Most votes
- Most comments
It may be best to open a support case (from the AWS console) so the AWS support team can help look at the logs to further assist.
I've seen this due to the fact that, by default, SES messages are sent from a shared pool of IP addresses, meaning you and other customers may be originating from the same AWS-owned IP block.
From the error you posted, it sound like that a set of IPs you've been using have been added to a third-party blocklist. The AWS SES team works to keep AWS IPs from being blocked, but it does occasionally happen. A support case can help highlight this to get resolution.
Alternatively, you can chose to use a dedicated pool of IP addresses, potentially avoiding being blocked due to others' activities.
Also encountered this same problem, even when using a managed dedicated IP pool.
I opened a support case using the AWS Console.
Related questions:
https://repost.aws/questions/QUkGceD18WTgu9uv9KYIZ5qQ/aws-ses-standard-dedicated-ip-addresses https://repost.aws/questions/QUjiKIlx5CQdyd4cTnnkwjug/amazon-recently-added-one-dedicated-ip-to-our-ses-but-the-ip-is-already-listed-on-sorbs-duhl
Relevant content
- asked 2 years ago
- asked a year ago
- asked 2 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
I'm a small-time user. Longstanding email list for years of legit subscribers. The first thing I did was put in a ticket to AWS. Totally blew me off and referred me here. And you make a good point. I do not have dedicated IP, so this may have nothing to do with me.
Zero stars for AWS support.