Encode e-mail subject to support non-ASCII chars #888
Merged
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
Pull Request Test Coverage Report for Build 579415284
💛 - Coveralls |
|
Would you be so kind as to add tests for this? |
paskal
reviewed
Feb 18, 2021
paskal
approved these changes
Feb 18, 2021
umputun
pushed a commit
to go-pkgz/email
that referenced
this pull request
Apr 28, 2022
Originally done in umputun/remark42#888 by @VeselovAlex.
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.
Add base64-encoding to email
Subject:header value to allow non-ASCII characters, according to RFC2047. Current implementation produces invalid messages when e.g. page title contains Cyrillic letters.