- Newest
- Most votes
- Most comments
Soft bounces are temporary, they can be resolved by attempting to re-deliver the mail after a delay. An example might be a full mailbox, the user may empty the mailbox and then the bounce will go away. (https://aws.amazon.com/premiumsupport/knowledge-center/ses-understand-soft-bounces/)
Hard bounces are permanent and should be suppressed, they should not be re-attempted.
Assuming the "missed bounces" are soft, it should be fine. I don't believe soft bounces can be included in suppression lists automatically today.
Thanks Chris. Is the "send feedback" option on the "suppression list" page the best way for me to request that soft bounces be optionally included?
If I am using a webhook to report bounces to a 3rd party client (IE https://docs.mautic.org/en/channels/emails/bounce-management#amazon-webhook), soft bounces won't be recorded there either?
Also, I think I verified that the issue is not simply soft bounces being excluded. Here's some examples of emails that should be hard bounces that are not getting included:
jsjsjs@icooud.com
example@ufl.edi
(should be .edu).
UPDATE: I confirmed that when using a webhook, SES will send all the "extra" bounces there. So example@ufl.edi
gets blocked by my 3rd party app, but doesn't get registered on SES's suppression list. Same for soft bounces.
Basically, SES reports soft bounces & domain errors via email notifications and webhooks, but only logs hard bounces on their suppression list.
Relevant content
- asked 2 months ago
- asked 2 years ago
- asked 4 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago