搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Inserting image in signature is blocked -- no way to allow to include the image

  • 2 个回答
  • 1 人有此问题
  • 1 次查看
  • 最后回复者为 jlinkels

more options

Thunderbird version 102.5.0 (64-bit) Debian 11 (Bullseye) KDE Plasma 5.20.5

I am trying to insert a HTML signature to my new messages. The HTML file contains a link to the signature file.

When I try to compose the message I get this message: "Thunderbird has blocked a file from loading into this message. Unblocking the file will include it in your sent message." There is a button "Preferences". When I click it, the message says: Unblock file:///home/xxx/yyy/zzz/artwork/email_sign_20160719.png

When I click Unblock, nothing happens.

I have tried to compose manually a new email and insert this image. Menu -> Insert -> Image -> Chose file. Chose the same file.

Same error message and no result when allowing / unblocking this image.

In Settings -> Privacy -> Mail Content -> Allow remote content in messages is checked. There is no exception blocking local file content.

I have added an exception, allowing everything starting with file:/// . No result.

In config editor I have mailnews.message_display.disable_remote_image set to false.

I am out of solutions. This is far beyond a simple method to allow me to attach an image in a signature.

Thunderbird version 102.5.0 (64-bit) Debian 11 (Bullseye) KDE Plasma 5.20.5 I am trying to insert a HTML signature to my new messages. The HTML file contains a link to the signature file. When I try to compose the message I get this message: "Thunderbird has blocked a file from loading into this message. Unblocking the file will include it in your sent message." There is a button "Preferences". When I click it, the message says: Unblock file:///home/xxx/yyy/zzz/artwork/email_sign_20160719.png When I click Unblock, nothing happens. I have tried to compose manually a new email and insert this image. Menu -> Insert -> Image -> Chose file. Chose the same file. Same error message and no result when allowing / unblocking this image. In Settings -> Privacy -> Mail Content -> Allow remote content in messages is checked. There is no exception blocking local file content. I have added an exception, allowing everything starting with file:/// . No result. In config editor I have '''mailnews.message_display.disable_remote_image''' set to false. I am out of solutions. This is far beyond a simple method to allow me to attach an image in a signature.

被采纳的解决方案

Found a solution. Somehow. Not happy about it.

Steps: Create a new empty email Insert the desired image and text Save the mail as HTML

When this HTML file is inserted as a signature, no warnings are issued.

Difference is that the HTML does not contain a pointer to a file in HTML. Like "src=file:///this.png" But instead the file contains the complete BASE64 encoded image.

The significant disadvantage is that if the image file changes, the signature must be completely recomposed and saved as HTML. Instead of simply changing the image file name of image file contents.

IMHO this ought not to be complicated like this. If I can compose HTML, file pointers should be allowed. It is normal HTML syntax. When I allow files to be included or attached, this should be allowed.

定位到答案原位置 👍 1

所有回复 (2)

more options

Some correction. When I do this action:

Menu -> Insert -> Image -> Choose file. Chose the same file.

The image is inserted. The reason Thunderbird still complains is that the option "insert HTML file as signature" is still enabled.

That should not preclude to insert an image manually anyway. But still it did.

After removing the option insert HTML file as signature I could manually insert an image.

more options

选择的解决方案

Found a solution. Somehow. Not happy about it.

Steps: Create a new empty email Insert the desired image and text Save the mail as HTML

When this HTML file is inserted as a signature, no warnings are issued.

Difference is that the HTML does not contain a pointer to a file in HTML. Like "src=file:///this.png" But instead the file contains the complete BASE64 encoded image.

The significant disadvantage is that if the image file changes, the signature must be completely recomposed and saved as HTML. Instead of simply changing the image file name of image file contents.

IMHO this ought not to be complicated like this. If I can compose HTML, file pointers should be allowed. It is normal HTML syntax. When I allow files to be included or attached, this should be allowed.