Can someone create a notification to be used for telling users to fix their malformed email addresses?
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Open | None | T150335 Notify users with malformed mail address to correct via Echo notifications | |||
Open | None | T125653 Create new types of notifications | |||
Open | None | T150337 Create Echo notification for users with malformed addresses |
Event Timeline
Just checked how the email address change is handled now:
(1) An email is sent to the old email address to inform a user about changes in the email address.
(2) When a user adds email address in Special:ChangeEmail, the validation for the email address is checks for limited number of options:
e.g. typing 11111 and clicking 'Change email'
Please include '@'in the email address. [user email] is missing an '@'.
But 11@111 or '2345'@1 are considered valid email addresses.
It might be worth to improve the validation of email addresses https://tools.ietf.org/html/rfc1035#section-2.3.1 and https://tools.ietf.org/html/rfc5322#section-3.4.
I'd definitely concur that it needs improving. There's all sorts of junk in the user_email field. Missing TLD etc. Which may be fine on a local domain, where it's internal email etc... But not in the case of Wikipedia et al
Probably should file a seperate task for that. Would you like to, or should I? (Might be worth a quick search beforehand, as we will likely have some tickets for it at least already)
This still has some use (see also parent task) for poking people to go fix it. I would agree improving validation first before notifying people to change/fix their emails would certainly be prudent. But this can be done before hand as appropriate :)
- I agree that improving email address validation deserves a separate task, so please file it.
- I also agree that since a user receives an email about email address changes, it makes sense to have an option for sending a notification.
- Improving validation and creating a new notification about malformed addresses (or maybe more generally about email address changes) may not depend on each other. Even without improving validation, sending a user a notification about changes will improve chances for correcting not-valid email addresses (assuming that users enter email addresses in good faith).
What do you mean by malformed email addresses? Are these actually malformed per RFC whatever or just invalid? During SULF I ran a script to de-confirm all emails that were malformed, does it need running again?
I assume the scope of this task is only about WMF sites? (Would welcome a clarification like "on WMF sites" in the task summary.)
11@111 or "2345"@1 (no TLD) are perfectly valid email addresses in local domains.
I did already say that ;)
The easy answer is it should be allowable if the server can resolve the domain. But on Wikipedia, we have a lot without TLD's, which will never work....
For gmail alone from testwiki:
| gmaIl.com | | gmai.com | | gmail | | gmail.Com | | gmail.c | | gmail.cim | | gmail.co | | gmail.co.in | | gmail.com | | gmail.com | | gmail.com.au | | gmail.comselimabner | | gmail.con | | gmail.it | | gmail.ru | | gmailcom | | gmaio.com | | gmal | | gmal.com | | gmaul.com | | gmil.com |
I think resending the email for the changed email address and confirming if the email could be set can be a better validation ?