Closed Bug 1872677 Opened 10 months ago Closed 7 months ago

Emails from Tech Republic do not render header info correctly

Categories

(Thunderbird :: General, defect, P1)

Thunderbird 122

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1880867

People

(Reporter: d.mcdivitt, Unassigned)

References

(Depends on 1 open bug)

Details

Attachments

(4 files)

TB version 122.0b1 (64-bit)
Picture shown is my message list. Notice two lines have uninterpretable characters for subject and correspondents. I saw this the first time on 12/31/2023 for an email by the same sender. Today is 01/02/2024 and the same happened again. I looked at the email with K-9 on my phone and did not see an issue so forwarded the email as an attachment from my phone hoping to encapsulate the entire wad. Upon receiving the forwarded email, that also did not render subject and correspondents properly.

This is the email forwarded as an attachment from K-9. The received email or outer package had the same rendering problem but the attachment came through properly, which I saved and edited to remove identifying info.

If I double-click the eml file and open with TB it renders properly. If I drag the original email that does not render properly, to the desktop and save as an eml file, then double-click to open with TB, it does render properly.

Version: unspecified → Thunderbird 122

I put the version at the top of the original post. Did not see where to put it in the new bug page.

I am receiving more emails that do not render headers properly. I updated to 122.0b1 last week. That's when the issue started. I don't remember the previous version I had. It was 121 something. I don't have the time right now to download and try the last few versions.

Severity: -- → S2
Priority: -- → P1
See Also: → 1872849

I was getting this problem, the headers not rendering properly and having uninterpretable characters, from two senders. It was reliably happening from those two senders. The last time I saw the issue occur was Jan 5th 2024. The problem was reported when I had 122.0b1. I recently upgraded to 122.0b2 and not having seen the problem for a few days I wanted to see if a code change resolved the problem. I downloaded and reinstalled 122.0b1, restored my email to last night's backup, and pulled current email again from the server. New emails from those senders rendered properly with 122.0b1.

If I go back and look at emails from when I reported this issue they still do not render properly. Because new emails from those senders do render properly when pulled freshly from the server, and because I'm using 122.0b1 which I was using when I originally reported the problem, the problem may be in the data and not code. Possibly the server was corrupting the emails. I can restore my email back to when the problem originally occurred and pull email from there to present, since I leave email on the server for ninety days, but see no need to make the problem happen again if it isn't happening currently.

The problem does seem to be gone. In instances like these in my support and development work I let the problem go, documenting specifics in case it begins happening again. I will post a new bug comment if I ever see the problem again.

I'm resurrecting this issue. Today I upgraded to 123.0b1 (64-bit) and saw the issue happen again for several emails. The issue is exactly as described previously in the bug report and the same pictures apply. But I'm adding an additional picture of what happened in the standalone message window for at least one message. It may be a separate bug but that can be sorted out. To make sure you see the correct picture it is uploaded Jan 28th and has "To protect your privacy, Thunderbird Beta has blocked remote content in this message" displayed thirty times in yellow.

This issue was gone. I installed 123.0b1 (64-bit) and it was back. To isolate what specific version has the bug I downloaded the last five beta versions. For each version I restored my email folder and pulled today's email again. My email stays on the server ninety days. For 122.0b1 thru 122.0b4 there was no issue. Version 123.0b1 has the issue.

I will stay with 122.0b4 for the time being.

Wayne, has anything been done on this? I want to resume with most recent beta version. Thanks

Flags: needinfo?(wayne.mery)

The multiple-notification bug (comment 7) has been fixed.

See Also: → 1880867

(In reply to David McDivitt from comment #8)

Wayne, has anything been done on this? I want to resume with most recent beta version. Thanks

It's all related to the class of issues in bug 1872849

Depends on: 1872849

Unfortunately I don't have any insight.
Does thsi still reproduce with a newer version?

Flags: needinfo?(wayne.mery) → needinfo?(david)

@wsmwk (Wayne) Can you tie this to bug 1880867 . I think it's the same issue.

Flags: needinfo?(david)
Status: NEW → RESOLVED
Closed: 7 months ago
Depends on: 1880867
Duplicate of bug: 1880867
Resolution: --- → DUPLICATE
See Also: 1880867
Depends on: 1890230
No longer depends on: 1880867
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: