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
In section 3.2.1 of the RFC2822, these brackets are described with No special semantics are attached to these tokens. They are simply single characters.
I don't know how the text between brackets should be handled but an error seems inappropriate.
The text was updated successfully, but these errors were encountered:
This library name wasn't future-proof, and as the README says, it is now compatible with RFC 5322. Our implementation is now based on email-addresses and there's an open issue there regarding brackets. The gist is, they're only allowed when the display name is quoted.
Some addresses I met contain text between brackets and this module generates an error. A simple example:
In section 3.2.1 of the RFC2822, these brackets are described with
No special semantics are attached to these tokens. They are simply single characters.
I don't know how the text between brackets should be handled but an error seems inappropriate.
The text was updated successfully, but these errors were encountered: