Closed Bug 2001632 Opened 6 days ago Closed 1 day ago

getFull() fails to fully parse message

Categories

(Thunderbird :: Add-Ons: Extensions API, defect)

Thunderbird 145
defect

Tracking

(Not tracked)

RESOLVED FIXED
147 Branch

People

(Reporter: jan.kiszka, Assigned: john)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:140.0) Gecko/20100101 Firefox/140.0

Steps to reproduce:

While trying to parse the attached message via the messages API and getFull ( as used by https://github.com/jan-kiszka/copypatch), some internal error seems to occur, and the retrieved result lacks the body and likely more fields.

The attached mesage was received via an IMAP inbox, but the error persists when reading it via an NNTP server.

Component: Untriaged → Add-Ons: Extensions API
Summary: getFull fails to fully parse message → getFull() fails to fully parse message

Hm, the part has a contentId and is therefore treated as an attachment. Unexpected.

Assignee: nobody → john
Status: UNCONFIRMED → NEW
Ever confirmed: true

Usually the presence of a content-id header indicates that a part is an inline element
referenced from elsewhere in the message as a related part. The current implementation
however treats those parts as attachments, which should only happen if the part has a
name.

Attachment #9528691 - Attachment description: Bug 2001632 - Treat text parts without a name but with a content-id as inline, not as attachments. r=#thunderbird-reviewers. → Bug 2001632 - Treat parts with a content-id as attachments only if they also have a name. r=#thunderbird-reviewers.
Target Milestone: --- → 147 Branch

Pushed by sking@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/f300c69d2825
Treat parts with a content-id as attachments only if they also have a name. r=mkmelin

Status: NEW → RESOLVED
Closed: 1 day ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: