We are still not able to reproduce the error but we are working on it.
We made a change at 12.00 pm UTC today, Monday 31st of July. If you have not tried after that timestamp already, please give it another go.
If that fails again,
1 - Do you get that error with any email or just the new one?
2 - Also, do you have any chance to try to log in from a different IP address, by using a VPN for example?
Thank you for your patience.