<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=208420) </details> <!--IssueSummary end--> ### Problem to solve When an e-mail delivery of a notification fails, it would use useful to the user to indicate that in their settings, perhaps by unverifying their e-mail address. ### Intended users Any/all ### Further details N/A ### Proposal It seems pretty clear without a "journey" being explained, I think. ### Permissions and Security N/A ### Documentation N/A ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning --> ### What does success look like, and how can we measure that? Users to whom e-mail delivery is failing for whatever reason have an indication of such. ### What is the type of buyer? N/A ### Links / references