Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ecosystem platform] Add information pertaining to bounceType #12155

Closed
data-sync-user opened this issue Mar 14, 2022 · 0 comments · Fixed by #12877
Closed

[ecosystem platform] Add information pertaining to bounceType #12155

data-sync-user opened this issue Mar 14, 2022 · 0 comments · Fixed by #12877

Comments

@data-sync-user
Copy link
Collaborator

data-sync-user commented Mar 14, 2022

In the Email Bounces section within Admin Panel, there is a bounce type field. It would be helpful to add any details and/or definitions of what the different bounceTypes mean, what can/can't be done and/or should/shouldn't be done (e.g., see attachment - what does Permanent mean? Is there something I should tell the user?). This should be included within the Admin Panel docs on the Ecosystem Platform and there should be a link to the section in the Triage Owner Duties docs as well.

For reference, bounceType, bounceSubType, and descriptions can be found here: https://docs.aws.amazon.com/ses/latest/dg/notification-contents.html#bounce-types

Also note -

if a bounce type is suppressed, clearing it isn’t going to help and will hurt deliverability score if we keep trying to send it.

If a user’s email address is globally suppressed, we are not able to clear it from the list as Amazon SES owns this list. The email address should drop off of the list in 14 days.

There are also per-account suppression lists which we can clear, either through their panel or their support system - though we are not sure if we’ve ever done one of these.

Once their email address is cleared off the Amazon suppression list(s), the email address will still be blocked within our database. We will have wait the 14 days, then unblock in our database and have them retry.

!Screen Shot 2022-03-14 at 4.03.16 PM.png|width=535,height=456!

┆Issue is synchronized with this Jira Task
┆Attachments: Screen Shot 2022-03-14 at 4.03.16 PM.png

xlisachan added a commit that referenced this issue May 13, 2022
Because:

* it would provide more information when clearing email bounces

This commit:

* adds descriptions for bounce type/subtype based on Amazon SES

Closes #12155
xlisachan added a commit that referenced this issue May 13, 2022
Because:

* it would provide more information when clearing email bounces

This commit:

* adds descriptions for bounce type/subtype based on Amazon SES

Closes #12155
xlisachan added a commit that referenced this issue May 13, 2022
Because:

* it would provide more information when clearing email bounces

This commit:

* adds descriptions for bounce type/subtype based on Amazon SES

Closes #12155
xlisachan added a commit that referenced this issue May 13, 2022
Because:

* it would provide more information when clearing email bounces

This commit:

* adds descriptions for bounce type/subtype based on Amazon SES

Closes #12155
xlisachan added a commit that referenced this issue May 14, 2022
Because:

* it would provide more information when clearing email bounces

This commit:

* adds descriptions for bounce type/subtype based on Amazon SES

Closes #12155
xlisachan added a commit that referenced this issue May 16, 2022
Because:

* it would provide more information when clearing email bounces

This commit:

* adds descriptions for bounce type/subtype based on Amazon SES

Closes #12155
xlisachan added a commit that referenced this issue May 17, 2022
Because:

* it would provide more information when clearing email bounces

This commit:

* adds descriptions for bounce type/subtype based on Amazon SES

Closes #12155
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant