invalid email address for a profile

[Pablohn26]

Some datasources (for example mbox) return an anonymized email of the contributor shorting it adding a ..., which makes it an invalid email.

With jira datasource, sometimes we get the email in the form: name dot something at domain dot com:

May happen that we store those invalid/anonymized emails while we have another valid emails from other identities/datasources in the same profile (individual). So we should save as main email of the individual a valid email instead of an invalid/anonymized email address.

[aklapper]

How to define a valid email address? Checking for an @ character?

[sduenas]

How to define a valid email address? Checking for an @ character?

The regex pattern we use for recommendations is :

^(?P<email>[^\s@]+@[^\s@.]+\.[^\s@]+)$

[dipak0000812]

Hi @Pablohn26 , @sduenas, I reviewed the current profile update path and found that profile emails are assigned directly in sortinghat/core/db.py (update_profile(...)) whenever email is present in kwargs, without validation. That seems consistent with the issue description where anonymized or malformed datasource emails can become the profile email. I’m looking into whether the safest fix is to prefer valid emails while preserving backward compatibility.