X
Appuyez ici pour vous rendre sur la version mobile du site.

Forum d’assistance

Why do image links in my HTML signature get turned into inline images?

Publié

I have written a program to create HTML signature files for email programs at my workplace.

The signature file uses URLs to images hosted on a server. This appears to work fine, but I've noticed that when I send an email from Icedove (Thunderbird rebadged for Debian), the image links automatically get turned into attachments. These are then visible as base64-encoded MIME blocks in the email source.

I cannot find any option for altering this behaviour anywhere in the application, even in the Config Editor.

Can anybody advise me how to change this behaviour? Thanks in advance.

I am running Icedove v.17 for Debian 64 bit.

I have written a program to create HTML signature files for email programs at my workplace. The signature file uses URLs to images hosted on a server. This appears to work fine, but I've noticed that when I send an email from Icedove (Thunderbird rebadged for Debian), the image links automatically get turned into attachments. These are then visible as base64-encoded MIME blocks in the email source. I cannot find any option for altering this behaviour anywhere in the application, even in the Config Editor. Can anybody advise me how to change this behaviour? Thanks in advance. I am running Icedove v.17 for Debian 64 bit.

Solution choisie

By default Thunderbird attaches all images, even if the <img> element points to a remote resource. Most e-mail clients block remote content these days unless the user authorizes it (see this thread for an in-depth discussion) due to potential privacy/tracking issues. Thus, the image your are adding as a remote resource may not display the first time the recipient opens the message.

If you want to change your code respectively anyway, have a look at this article. You'll have to add an attribute <img moz-do-not-send="true"> to the element which will Tell Thunderbird to not download the image from the server and embedding it into the message on sending.

Lire cette réponse dans son contexte 4

Détails additionnels sur le système

Application

  • Agent utilisateur : Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20140205 Firefox/24.0 Iceweasel/24.3.0

Plus d’informations

rsx11m 21 solutions 125 réponses

Solution choisie

By default Thunderbird attaches all images, even if the <img> element points to a remote resource. Most e-mail clients block remote content these days unless the user authorizes it (see this thread for an in-depth discussion) due to potential privacy/tracking issues. Thus, the image your are adding as a remote resource may not display the first time the recipient opens the message.

If you want to change your code respectively anyway, have a look at this article. You'll have to add an attribute <img moz-do-not-send="true"> to the element which will Tell Thunderbird to not download the image from the server and embedding it into the message on sending.

By default Thunderbird attaches all images, even if the &lt;img&gt; element points to a remote resource. Most e-mail clients block remote content these days unless the user authorizes it (see [https://support.mozilla.org/en-US/questions/991448 this thread] for an in-depth discussion) due to potential privacy/tracking issues. Thus, the image your are adding as a remote resource may not display the first time the recipient opens the message. If you want to change your code respectively anyway, have a look at [http://kb.mozillazine.org/Creating_complex_mails_with_inline_images#Remote_images this article]. You'll have to add an attribute &lt;img '''moz-do-not-send="true"'''&gt; to the element which will Tell Thunderbird to ''not'' download the image from the server and embedding it into the message on sending.