1 Answer
- Newest
- Most votes
- Most comments
0
The only other suppression list would be the global suppression list [1] although given that it succeeds when disabling your account suppression list sure seems the domain is on the account level list. Would be worth attempting to remove the destinations [2] in question from your account suppression list to see if that succeeds or fails.
[1] https://docs.aws.amazon.com/ses/latest/dg/sending-email-global-suppression-list.html [2] https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list.html#sending-email-suppression-list-manual-delete
answered 2 years ago
Relevant content
- asked 2 months ago
- asked a year ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Thanks for your answer. It was a rather silly issue. I did'nt realize that 'aws sesv2 list-sppressed-destinations' command does not list all the destination in a single invocation. It returns a 'NextToken' in json output, if there are more to be listed. Caller is then required to invoke command again with the token passed in --next-token arguement. Wish there was an option though to dump the entire list in single shot, for convinience in scripts etc.
Ah thats fair, yh some commands will handle the pagination or are supposed to but seems like its not supported on all commands