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
Maybe it is a bug, or this is expected behavior, but éàé@local.dev seems to be a valid email (with strict_mode off, default behavior)
The problem is when you want to send an email with this address, there is an Exception raised by swiftmailer because this email is not RFC822 compliant .
Shouldn't we use the the filter_var('éàé@local.dev', FILTER_VALIDATE_EMAIL) which follows RFC 822 instead of a regex here ?
The text was updated successfully, but these errors were encountered:
That's the expected behaviour. If you need to catch more invalid e-mail addresses, you need use the strict option. filter_var() was used in the past, but it had other issues. If you want to read more about this, you can take a look at these issues (there are probably more about this topic): #18162, #18560, #19385 and #20309
In #1581 you can read more about the discussion that led to the introduction of the strict option and dropping the use of filter_var() (see PR this features was introduced with is #9140).
Since there is no bug in the component I am closing here. Thank you for understanding.
Maybe it is a bug, or this is expected behavior, but
éàé@local.dev
seems to be a valid email (with strict_mode off, default behavior)The problem is when you want to send an email with this address, there is an Exception raised by swiftmailer because this email is not RFC822 compliant .
Shouldn't we use the the
filter_var('éàé@local.dev', FILTER_VALIDATE_EMAIL)
which follows RFC 822 instead of a regex here ?The text was updated successfully, but these errors were encountered: