How to change filelink style in outgoing email?
I use filelink feature of Thunderbird a lot for attaching big files. However, when ever I use filelinks Thunderbird puts a big html block with link to the attachment as seen in this screenshot: http://imgur.com/XexKeLK . Initialy, it looks good and fancy but very soon it becomes very distracting, annoying and confusing to recipient. Few times people also confuse it with advertisement! Also, while using filelink, thunderbird would attach a file of 0 bytes with names like "Part1.2". So my question is:
1. Is there any way to simplify the html block generated by filelink feature? Just a plain link with may be file size is good enough, atleast for me. I have tried editing the source HTML of outgoing email myself but it is not a solution as it has to be done for each and every email.
2. Can Thunderbird not attach 0 byte files while using filelink? It is also a source of confusion to recipient.
Thanks
Modified by mozillawebid
الحل المُختار
As suggested by christ1, switching to plain text email resolves Issue 1 and it seems to work with all filelink providers.
Issue 2 is not resolved by above workaround. However, I will still mark this question as resolved as first issue was the most annoying to me. Thanks.
Read this answer in context 👍 2All Replies (5)
This is how attachments look for me using Filelink in connection with Dropbox. I'm composing in plain text.
I've linked 2 files to this email:
- image1.jpg (2.4 MB) hosted on Dropbox: <url>
- image2.jpg (2.6 MB) hosted on Dropbox: <url>
You may try this add-on to install Dropbox as a Filelink provider.
https://addons.mozilla.org/en-US/thunderbird/addon/dropbox-for-filelink/
Switching to plain text email resolves Issue 1. It works for all providers, not just dropbox.
Any idea about issue 2 in my question?
Try Dropbox as provider for Filelink.
No. Dropbox as provider did not resolve issue 2. See attached screenshots.
Modified by mozillawebid
الحل المُختار
As suggested by christ1, switching to plain text email resolves Issue 1 and it seems to work with all filelink providers.
Issue 2 is not resolved by above workaround. However, I will still mark this question as resolved as first issue was the most annoying to me. Thanks.