Skip to content
This repository has been archived by the owner on Aug 22, 2019. It is now read-only.

Verify additional email sending to primary account #1167

Open
mattdigitalme opened this issue Apr 23, 2018 · 3 comments
Open

Verify additional email sending to primary account #1167

mattdigitalme opened this issue Apr 23, 2018 · 3 comments

Comments

@mattdigitalme
Copy link
Contributor

@auralon We've had a couple of reports in where the below is happening:

When I try to verify an associated Email address, I receive the code in the
main address mailbox, not in the associated email address that I am trying
to verify. As a result neither address gets verified.

Essentially, adding in a secondary email is causing the verify link to be sent to the primary address and not the newly added email. Can you take a look

M

@auralon
Copy link
Contributor

auralon commented Apr 24, 2018

Hmmm, this is odd. Have you managed to recreate this behaviour @mattdigitalme? It's been quite thoroughly tested, so I'm wondering how this behaviour could be triggered from a user perspective. We'll need to schedule in some time to investigate this issue.

@mattdigitalme
Copy link
Contributor Author

@auralon John (DME) and I have run through it and can recreate the issue - when we used Johns flow he has merged gmail accounts and I wondered if this could be the issue however this new case (addressed above) uses a gmail and and outlook account in separate mailboxes.

@strandloper
Copy link

I can confirm this is still a problem. With primary (gmail.com) address verified; on attempting to verify secondary address (company account hosted on Office 365) the email is sent to the primary address. Whether entering the code in the email or just closing the verification pop-up, the primary account is now also no longer verified. If you do enter the code, an error message flashes indicating the code is invalid.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants