-
Notifications
You must be signed in to change notification settings - Fork 17.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
net/mail: ParseAddress does not allow mixed quoted / unquoted local parts #39591
Comments
Section 3.2.3 suggests that the local part of an address may be a dot-atom or a quoted string, but not a combination of both as your example shows. Do mail clients accept this address? |
There is also section 4.4 describing
does arrive. Note: While section 4 is obsolete, it must be accepted.
|
I read “.” as one literal period character |
Well yeah, so the obs-local-part in
Am I reading the RFC wrong? |
Tbh I’m not sure. What’s your use case? Do you have a need to accept this form of address? |
I've tried to put list of valid email addresses [0] through our email validation and some did not pass. So it seemed reasonable to open a bug report about this. If full RFC 5322 compatibility is not a desired goal, then this can be closed. [0] https://github.com/StoneCypher/testdata-valid-email/blob/master/testdata-valid-email.js |
What version of Go are you using (
go version
)?I'm not sure how to get this information from play.golang.org.
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?I'm not sure how to get this information from play.golang.org.
What did you do?
https://play.golang.org/p/OjrtE1S12lP
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: