Bug 1628441 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I haven't looked at the full mailbox files you attached yet, but the sample email seems to have some problems. It claims it is multipart but I only see one part. Also, it says it is quoted-printable and it looks like just all plain text. Maybe this is OK, don't know for sure.

Anyhow, I found a workaround for the sample file. Set ```mail.inline_attachments.text``` to true in config editor. This causes the sample email to appear.  This pref was added as part of the 68 release to avoid showing huge plain text attachments inline. Apparently tb is seeing your file as just a text attachment.

Also, FWIW, removing the line 
```
Content-Disposition: quoted-printable
```
from the file causes the message to be seen without changing the pref. 
Possibly other tb coding changes in the MIME code in version 68 are affecting this.
I haven't looked at the full mailbox files you attached yet, but the sample email seems to have some problems. It claims it is multipart but I only see one part. Also, it says it is quoted-printable and it looks like just all plain text. Maybe this is OK, don't know for sure.

Anyhow, I found a workaround for the sample file. Set ```mail.inline_attachments.text``` to true in config editor. This causes the sample email to appear.  This pref was added as part of the 68 release to avoid showing huge plain text attachments inline. Apparently tb is seeing your file as just a text attachment.

Also, FWIW, removing the line 
```
Content-Disposition: quoted-printable
```
from the file causes the message to be seen without changing the pref. 
Possibly other tb coding changes in the MIME code in version 68 are affecting this.

Edit: I imported the mbox and msf file to local folder and see the problem on all the emails I looked at: displays blank.  Setting mail.inline_attachements.text to true fixes the problem.
I haven't looked at the full mailbox files you attached yet, but the sample email seems to have some problems. It claims it is multipart but I only see one part. Also, it says it is quoted-printable and it looks like just all plain text. Maybe this is OK, don't know for sure.

Anyhow, I found a workaround for the sample file. Set ```mail.inline_attachments.text``` to true in config editor. This causes the sample email to appear.  This pref was added as part of the 68 release to avoid showing huge plain text attachments inline. Apparently tb is seeing your file as just a text attachment.

Also, FWIW, removing the line 
```
Content-Disposition: quoted-printable
```
from the file causes the message to be seen without changing the pref. 
Possibly other tb coding changes in the MIME code in version 68 are affecting this.

Edit: I imported the mbox and msf file to local folder and see the problem on all the emails I looked at: displays blank.  Setting mail.inline_attachements.text to true fixes the problem.
Note also that for every email in the reporter's mailbox (total 7679) I see a paperclip icon indicating each has an attachment. However, the message displays, with default setting, empty with no attachment link visible along the bottom. I've noticed the paperclip icon before and there would be no linked attachment, not just on the reporter's mailbox.

Back to Bug 1628441 Comment 6