- 最新
- 最多得票
- 最多評論
Can you check your account level suppression list? It will tell you why its suppressed (bounce, complaint, etc)
From the CLI
aws sesv2 list-suppressed-destinations
You can also view in the SES Console
If an address is on the suppression list for your account, but you know that the address shouldn't be on the list, you can remove it by using DeleteSuppressedDestination operation in the SES API v2.
Hi, what is the bounce sub-type you see? https://docs.aws.amazon.com/ses/latest/dg/notification-contents.html
Here are the difference bounce types and bounce sub types with a description of what it means. There are 4 subTypes for 'Permanent' bounce type. Does this leave you a clue on what happened with your email, which was bouncing?
This is not due to the account-level suppression list. Rather, this is because of the global-level suppression list. More info on that can be found here: https://docs.aws.amazon.com/ses/latest/dg/sending-email-global-suppression-list.html
Basically what happened is that the first time the email was sent to that email address, it wasn't on an account-level suppression list so SES tried sending it to the recipient MTA. The recipient MTA responded with a hard bounce so SES placed that email address on the global-level suppression list. Email addresses fall off the global suppression list over time (at most, 14 days) and then you'll be able to retry sending to that email address (but only do so if you are 100& confident that a hard bounce will not occur again!). Alternatively, you can contact AWS Support to get that email address removed from the global-level suppression list manually if you do not want to wait 14 days.
相關內容
- 已提問 6 個月前
- AWS 官方已更新 1 年前
- AWS 官方已更新 2 年前
Hi Matt, Thank you for your reply. We removed the email addresses from account level suppression list several times, but they keep get into list again and again. notification type is bounce and bounce type is permanent. As I said they are valid email addresses. in the report we see that "Amazon SES has suppressed sending to this address because it has a recent history of bouncing as an invalid address". we are quite confused.