-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
70 "Your Riot Validation Token" emails received for new account #2447
Comments
Reported fixed by Matthew at about 0000 GMT:
Matthew is emailing those affected. I've not received an email but perhaps my provider (1and1 via Gmail) is blocking the domain. |
Everyone affected should have received an apologetic email at 00:20 GMT. This looks to be due to matrix-org/synapse#1160 having accidentally made its way onto the production matrix.org homeserver and interacting badly with riot.im/app, which tight-looped on registration. |
ftr the root cause of this was matrix-org/matrix-react-sdk#510 (exposed by the server API refinement) |
5d9546f introduced a change to synapse behaviour, in that failures in the interactive-auth process would return the flows and params data as well as an error code (as specced in matrix-org/matrix-spec-proposals#397). That change exposed a bug in Riot which would make it request a new validation token (and send a new email) each time it got a 401 with a `flows` parameter (see element-hq/element-web#2447 and the fix at matrix-org/matrix-react-sdk#510). To preserve compatibility with broken versions of Riot, grandfather in the old behaviour for the email validation stage.
I later received the follow-up email and notification mails seem to be working too. |
I created a new riot.im account and quickly received 70 emails with "Your Riot Validation Token" in the subject. They all seem to contain the same message:
I confirmed the address within the first 10-20 messages but they kept coming for a bit. They might still be coming and my email provider has just banned the sender.
The text was updated successfully, but these errors were encountered: