Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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

  • 1 reply
  • 3 have this problem
  • 6 views
  • Last reply by rsx11m

more options

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.

Chosen solution

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.

Read this answer in context 👍 4

All Replies (1)

more options

Chosen Solution

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.