fix: parse emails as plaintext#26
Merged
Merged
Conversation
no major email clients do this, but it's good to have just in case
noahpistilli
reviewed
May 5, 2026
noahpistilli
left a comment
noahpistilli
left a comment
Member
There was a problem hiding this comment.
Add a workflow to run the test, otherwise LGTM
Member
Author
|
We already have a workflow for this, merging. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR adds proper handling for HTML emails. Multipart messages now default to non-HTML text (as all major email clients send HTML messages as multiparts with both HTML and plaintext), while having a proper fallback to strip HTML tags when only HTML is available.
This also adds a basic unit test to ensure we are parsing content properly from multipart emails.