thunderbird / thunderbird/thunderbird-android
Outlook attachments can't be viewed
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Checklist
- I have used the search function to see if someone else has already submitted the same bug report.
- I will describe the problem with as much detail as possible.
App
Thunderbird for Android
App version
14.0b2
Where did you get the app from?
F-Droid
Android version
Android 16 QPR2 Beta 3.1
Device model
Pixel 9
Steps to reproduce
Receive an E-Mail sent by Outlook (with uncertain settings) that contains forwarded emails (probably forwarded as a file instead of just embedded into the email).
Expected behavior
The attachments should be properly displayed, as e.g. Thunderbird for Linux 140.4.0 esr is able to.
Actual behavior
The TB app only shows "noname.eml" with a size of 0 B. Though tapping on the attachment and opening it e.g. in GMail (or downloading it) does show the contents of the eml file, but not the attachments contained inside them.
The TB app shows two noname.eml files as attachments, while desktop TB shows two eml files and all 4 attached PDF files. Also in desktop TB, above the forwarded emails, TB displays a "ForwardedMessage.eml"
Logs
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 reproducing the issue with the linked k9mail-logs.txt and an Outlook message containing forwarded emails. Compare the Android attachment display with the stated Thunderbird for Linux behavior; done means the nested forwarded message and its PDF attachments are displayed rather than empty noname.eml entries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100