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

Unclear process when email fails #30

Open
morisy opened this issue Feb 28, 2020 · 1 comment
Open

Unclear process when email fails #30

morisy opened this issue Feb 28, 2020 · 1 comment
Assignees

Comments

@morisy
Copy link
Member

morisy commented Feb 28, 2020

Hi,

Noticed a user was getting email errors; tried going in and manually marking it as OK since the user was able to forward emails, but the process seems a bit weird — going to the email page there was no way to reconfirm or otherwise see which email was causing the problem.

I also couldn't see a way to unmark an email as problematic from the backend, but I might be just missing it.

So for this issue, just check in and look at if something seems off with how this email is marked; if everything is working expected, just maybe adding a way to re-verify an email address so that one-off bumps don't leave that error message popping up forever, and maybe also adding some kind of "Email Unreachable" red pill next to bad email addresses.

https://youtu.be/rZYK5rby9Hw

@mitchelljkotler
Copy link
Member

  1. I am adding the email_failed field to the admin backend so staff can manually update this field if needed
  2. If we get a bounced email it just marks it on the account and doesn't actually track which email it was - it should always just be the primary email address (that's the only one we send emails to) - and the only way to clear it is to change your email address (no way to clear temporary hiccups)
    So I think allowing re-verification to clear this makes sense.

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

No branches or pull requests

2 participants