You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Several participants are unable to or had trouble creating their User Profile's due to their seemingly valid emails not being accepted by SendGrid. The sendGrid UI also shows that emails with no obvious issues were classified as invalid, with all invalid emails having a score of 0. Some participants are able to sign up with failed SendGrid emails.
1/12-1/14 pts had trouble making their UP, 1/15-1/16 emails with no obvious issues were deemed invalid
@jhflorey to implement "trimming" entered email addresses for leading or trailing spaces
Need to check if the PWA MyProfiles page email address edits(for verified pts) also uses the same sendGrid email check. The SMDB does not, and has been used to address pts who are unable to make UP due to invalid emails
One option is to lower the risky scoring threshold to 0 to allow emails with no obvious issues to not be declined. However truly "bad" emails would have to be factored in as they currently fail
Current scoring:
o Invalid
• Domain has valid address syntax = false
• Domain has mx or record = false
Score < 0.45
o Warning
• Suspected disposable email
• Local part is suspected role
• Additional known bounce
• Suspected bounce
Score <0.8
The text was updated successfully, but these errors were encountered:
Several participants are unable to or had trouble creating their User Profile's due to their seemingly valid emails not being accepted by SendGrid. The sendGrid UI also shows that emails with no obvious issues were classified as invalid, with all invalid emails having a score of 0. Some participants are able to sign up with failed SendGrid emails.
Current scoring:
o Invalid
• Domain has valid address syntax = false
• Domain has mx or record = false
Score < 0.45
o Warning
• Suspected disposable email
• Local part is suspected role
• Additional known bounce
• Suspected bounce
Score <0.8
The text was updated successfully, but these errors were encountered: