Replace RFC-822 address-list parser with RFC-5322 #278
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
seriyps
force-pushed
the
rfc5322-address-list
branch
from
4274355 to
b47ab2c
Compare
|
Great work! |
mworrell
pushed a commit
that referenced
this pull request
Sep 21, 2021
mworrell
pushed a commit
that referenced
this pull request
Sep 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A more modern and robust parser for address specifiers like this (may appear in To / From / CC etc):
https://datatracker.ietf.org/doc/html/rfc5322#section-3.4
login@domainName <login@domain>Name Surname <login@domain>Name <login1@domain1>, Name2 <login2@domain2>group name:login@domain,Name <login2@domain2>;Also different versions of escaping of name / login / domain.
It's much more unicode-friendly also.