Open Bug 977562 Opened 10 years ago Updated 2 years ago

Embedded Pictures are not forwarded by filter

Categories

(Thunderbird :: Filters, defect, P5)

Product:
Thunderbird
Component:
Filters
Version:
24 Branch
Platform:
x86_64
Windows 7
Type:
defect

Tracking

(Not tracked)

People

(Reporter: franz, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: dataloss) 

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20140212131424

Steps to reproduce:

1) Create a filter that forwards every incoming Mail to another Mailadress
2) Send an Email with embedded (not attached) pictures to the first mail address.
3) Recieve the Mail at the second mail address.


Actual results:

1) Mail is recieved at Mailbox 1.
2) Filter forwards mail to second email address.
3) Mail is recieved at second Mailbox but the pictures are shown as empty spaces. (not linked / existing pictures)


Expected results:

The pictures should be available at the second mailbox too, just like when you forward an email manually.

email forwarding via filters works in a very reliable fashion in modern thunderbird versions, I recommend closing this issue and letting the OP ( or someone else ) reopen if they have a reproducer for the issue.

Problem still exist on modern version!
I'm trying to forward using message filters on a Thunderbird version 91.5.0 (32-bit); Windows 10 Home 21H1
It forward well the messages, (including format and attachments), but it won't forward embedded images.
It only send the image file names.

This was reproduced by Ping today (on which version of TB?), see bug 1750503, comment 1.

Severity: normal → S2
Flags: needinfo?(remotenonsense)
Priority: -- → P2

This constitutes unexpected dataloss. Should get some attention if possible. Magnus, any hints? Who could work on this?

Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(mkmelin+mozilla)
Keywords: dataloss

(In reply to Thomas D. (:thomas8) from comment #4)

This was reproduced by Ping today (on which version of TB?), see bug 1750503, comment 1.

91 and 97.

Flags: needinfo?(remotenonsense)

xref bug 312025.
Looks like fixing atm would likely be super involved. We could take another look once we don't go through libmime, and filters have been converted to JavaScript. But for now, this bug is out of scope.

Flags: needinfo?(mkmelin+mozilla)
Priority: P2 → P5
Depends on: 1664150

In the interim, is it possible to surface this limitation in the filter UI so users are not caught un-aware ?

You need to log in before you can comment on or make changes to this bug.