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
According to RFC 5322, given a string like "kev@inburke.comkev@inburke.com", the first "kev@inburke.com" can only be parsed as a display-name. An unquoted display-name can only contain what RFC 5322 calls "atoms", which can be alphanumeric characters or various special characters, but the list of special characters does not include '@'. So I think that is not a valid address specification, and mail.ParseAddress is correct to reject it.
Similarly ':' is not permitted so I think your second string is also correctly rejected.
I expect that
mail.ParseAddress("kev@inburke.com <kev@inburke.com>")
will parse toIt's weird, granted, but I am guessing that the RFC for email parsing allows email-like things to be present in the Name field?
Noticed when using maintner to parse Gerrit emails. I also found this one:
(actual person's name withheld) which choked on the second Author: call.
It seems like it would be good to have a tool to validate the commit name/email before merge.
The text was updated successfully, but these errors were encountered: