- Newest
- Most votes
- Most comments
Hi Chris.
Per the Amazon SES Account-level suppression list considerations this shouldn't have happened:
If you attempt to send a message to an address that's on your account-level suppression list, SES accepts the message, but doesn't send it.
At the same time, please confirm you are using account-level suppression list and not global suppression list. This is because in the same document it states:
If an address is on the global suppression list, but not on your account level suppression list (which means you want to send to it), and you do send to it, SES will still attempt delivery; however, if it bounces, it still counts toward the bounce rate for your account and toward your daily sending quota.
Now, it may be an issue of having all the backend updated. Can you tell me how much time has passed between adding the email address to the suppression list and email being sent?
Without knowing how you are sending your emails, you should avoid sending emails deliberately to email addresses in your suppression list. If you are coding your own system to deliver the emails, try to read the list of email addresses in the suppression list and use this information to prevent sending them emails.
I hope this helps.
Hi Jose.
Today, I received the third complaint from the same customer. I don't know what's going on with him. He is just marking our transactional emails as spam. Don't know why he is doing this. His email address is clearly on the account level suppression list since June 29, 2023.
I have never had any problems since using SES. I will check if I can add the email addresses to my email system. But I am angry that SES does not filter the addresses on the suppression list.
I can send you the message ID, if you can do something.
Thanks Chris
Relevant content
- Accepted Answerasked 5 months ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 5 months ago
- AWS OFFICIALUpdated 2 years ago
Hello Chris. I think the best option right now is to open a support case with AWS Support. They would have the tools to investigate why this is happening. With that said, something that comes to mind is, is this email address defined in the suppression list defined with the same casing as in the system sending the email? I don't remember exactly if this has any effect but please check that. Also, per my previous answer:
I hope this helps.