Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Inline image missing when replying to email

  • 2 respostas
  • 2 têm este problema
  • 1 visualização
  • Última resposta por 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?

Solução escolhida

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.

Ler esta resposta no contexto 👍 2

Todas as respostas (2)

more options

Solução escolhida

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.