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

Ensure that all internally generated message dispositions have a corresponding bounce classification #294

Open
wez opened this issue Sep 25, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@wez
Copy link
Collaborator

wez commented Sep 25, 2024

Ideally they'd all have an appropriate enhanced status code and match the IANA codes, but otherwise, we should ensure that we have classifications for all of them.

It's worth also thinking about how to ensure that any newly added or changed messages continue to be classified to avoid drifting away in the future.

@wez wez added the enhancement New feature or request label Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant