Not performing sanitization (decapitalization) on email addresses consistently when storing/retrieving email invitations leads to very bad UX in certain cases.
Consider the following scenario in a email invite-only configuration:
An invitation to User@example.com is causing ma1sd to send an invitation mail to the user.
The user tries to register with the email address user@example.com
The user gets the notification: "Your email address cannot be used for registration"
This can be even extended by the following:
The inviting user assumes the error has something to do with the initial invite sent to an address with a captial letter in it and re-invites user@example.com
The user tries to register again with user@example.com and it doesn't work either.
I suppose consistently performing decapitalization
before storing it as a pending invite
when comparing a registration attempt to the value stored in the database
Not performing sanitization (decapitalization) on email addresses consistently when storing/retrieving email invitations leads to very bad UX in certain cases.
Consider the following scenario in a email invite-only configuration:
This can be even extended by the following:
I suppose consistently performing decapitalization
would solve this issue.