Accept whitespace in RFC2047 encoded-text productions #1190
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
gahr
added
bug:confirmed
flatcap
approved these changes
May 7, 2018
ghost
removed
the
|
Maybe we could log a warning to raise awareness for this? I know it's a long shot but if Neomutt accepts non-standard headers while encouraging people to report the issue to the sender's client's maintainer as an RFC violation, we might eventually be able to drop this again. 😉 |
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.
Let's be more liberal and accept RFC2047 encoded-test productions that include white space. This is explicitly forbidden by RFC2047, but Mutt has been accepting them since (almost) forever, so let's not break existing clients.
#1189