Images in E-Mail not displayed
Categories
(Thunderbird :: Message Reader UI, defect)
Tracking
(Not tracked)
People
(Reporter: teves, Unassigned)
Details
Attachments
(1 file)
|
35.56 KB,
message/rfc822
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/113.0
Steps to reproduce:
We use a marketing tool called Mautic to send Newsletters to our clients. The mails coming from this tool are working on every platform I tested, but are not shown correctly in Thunderbird.
Actual results:
The problem is that none of the images contained in these emails are shown, and also there is no message that 'external contents are blocked'.
I have appended an example email file for you to reproduce the behaviour.
Developer tools say 'Image could not be loaded' when hovering over an <img> Tag in the HTML source.
The console says: Error while calling actor 'domnode's method 'getImageData' CanvasRenderingContext2D.drawImage: Passed-in image is "broken"
But when I copy one of the image links into a browser, the image will be displayed without problem.
Expected results:
All images should simply display, or at least I should get the opportunity to load objects blocked for security reasons.
|
||
Comment 1•2 years ago
|
||
I do get the blocked remote content notification, and if I enable the images, they are not blocked. But they are not displayed.
In the dev tools network tab I see SEC_ERROR_UNKNOWN_ISSUER.
You can see the same issue from the command line with cURL.
curl 'https://mautic.fuago.io/media/images/ox_guard_laptop.jpg' -H 'User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/116.0 Thunderbird/116.0a1' -H 'Accept: image/avif,image/webp,*/*' -H 'Accept-Language: en-US,en;q=0.5' -H 'Accept-Encoding: gzip, deflate, br' -H 'Connection: keep-alive' -H 'Sec-Fetch-Dest: image' -H 'Sec-Fetch-Mode: no-cors' -H 'Sec-Fetch-Site: cross-site'
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: https://curl.se/docs/sslcerts.html
So something wrong with the cert of that server.
Hi,
you were right indeed, so you can close this issue now.
One of our intermediate certificates was not the right one. The nasty thing was that although it was the wrong certificate, it was from the correct issuer. Apparently for this reason, no problems were displayed in any browser, even some sophisticated SSL test suites did not report any errors.
So thank you very much for your help and sorry for putting the blame on you guys. ;-)
Kind regards,
Tom
Description
•