thunderbird / thunderbird/thunderbird-android
Don't treat parts with unknown Content-Transfer-Encoding as candidates for viewable parts
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
From RFC 2045:
Any entity with an unrecognized Content-Transfer-Encoding must be treated as if it has a Content-Type of "application/octet-stream", regardless of what the Content-Type header field actually says.
Currently we treat parts with a content type of text/plain or text/html as viewable regardless of whether or not Content-Transfer-Encoding contains an unknown value.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the MIME-part viewability logic that currently accepts text/plain and text/html parts, and read RFC 2045's rule for unrecognized Content-Transfer-Encoding values. Add a regression test for an unknown encoding and verify that the part is no longer treated as viewable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100