Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Inline image missing when replying to email

  • 2 trả lời
  • 2 gặp vấn đề này
  • 22 lượt xem
  • Trả lời mới nhất được viết bởi rolandriddell

more options

I've noticed that when I reply to emails that contain inline images that were inserted in the original email using an iOS device (e.g. iPhone), they are not shown in the reply email. All is see is a border line around where the image should be. This only seems to occur if the image was inserted & sent from an iOS device as this doesn't happen with any other emails that have inline images.

I had a look at the html of the message and this is what I see where the image should be: <fieldset class="mimeAttachmentHeader"></fieldset>

I'm interested to know if anyone else has noticed this. I'm I missing something obvious here?

I've noticed that when I reply to emails that contain inline images that were inserted in the original email using an iOS device (e.g. iPhone), they are not shown in the reply email. All is see is a border line around where the image should be. This only seems to occur if the image was inserted & sent from an iOS device as this doesn't happen with any other emails that have inline images. I had a look at the html of the message and this is what I see where the image should be: <fieldset class="mimeAttachmentHeader"></fieldset> I'm interested to know if anyone else has noticed this. I'm I missing something obvious here?

Giải pháp được chọn

My understanding is that ios mis encodes mime types and Thunderbird displays them but will not forward the poorly encoded images. Using forward as attachment should work.

Đọc câu trả lời này trong ngữ cảnh 👍 2

Tất cả các câu trả lời (2)

more options

Giải pháp được chọn

My understanding is that ios mis encodes mime types and Thunderbird displays them but will not forward the poorly encoded images. Using forward as attachment should work.