Back to: Bugs/Defect Tracker
Description:
The "Advanced Fields > Email" component rejects unusual valid email addresses (false negative) and accepts unusual invalid email addresses (false positive). Source (I don't know if this implementation was meant to be compliant with RFC5322 .)
*The above screenshot was taken from: https://submit.digital.gov.bc.ca/app/form/preview?f=3527a6ba-62b9-47a3-ba1c-f33b687d9d2b&d=2a4faad4-342f-4cd5-808b-e4a5baf4acde on Aug 17, 2023.
(Chrome browser: Version 116.0.5845.97 (Official Build) (32-bit), Windows 10.)
*The above screenshot was taken from: https://submit.digital.gov.bc.ca/app/form/preview?f=3527a6ba-62b9-47a3-ba1c-f33b687d9d2b&d=2a4faad4-342f-4cd5-808b-e4a5baf4acde on Aug 17, 2023.
(Chrome browser: Version 116.0.5845.97 (Official Build) (32-bit), Windows 10.)
As I understand it Email addresses can include certain special characters, but the rules for their usage are specific.
For the email address
just”not”right@example.com, it’s invalid because it uses quotes (") directly in the local part (before the @ symbol) without surrounding the entire local part in quotes.However, for the email address
"email"@example.com, it’s valid because the entire local part is surrounded by quotes. This is a special rule that allows certain special characters to be used when they are enclosed in quotes.
So, while quotes are generally not allowed directly in the local part of an email address, they can be used to enclose the entire local part, allowing for certain special characters.
However: the “Advanced Fields > Email” component accepts just”not”right@example.com
Source: https://submit.digital.gov.bc.ca/app/form/submit?f=04d899e8-6669-4a3d-89a6-448b0a3e5a72