搜索 | 用户支持

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

详细了解

Problem selecting open-with program when opening attachments in forwarded message

  • 5 个回答
  • 1 人有此问题
  • 6 次查看
  • 最后回复者为 Mark Foley

more options

I am running Thunderbird 52.5.2 (64-bit) on Slackware64 14.2. I have an almost-solved problem. I have a user that likes to forward messages with attachments, but modify the attachment in the forward pane. This saves him from having to first save-to-disk, modify, then re-attach. When right-clicking on an attachment in the forward pane there is an 'Open' option. Clicking on that offers to open the file with some arbitrary application (in this case Foxit Reader, regardless of the file type!). I was able to solve a similar problem some months ago opening normal attachments (in inbox, not forwarding) by clicking on 'Other' in this Open dialog and browsing to the location of the appropriate executable (e.g. LibreOffice). However, it appears that that setting is not applied when opening an attachment in the forward pane. Ok, annoying, but no worries, I just followed the same procedure as before: selected 'Other', browsed to the executable location, selected (in this case) swriter.

Here's the problem -- I can select the right executable, and it will open the attachment appropriately, but the 'Do this for files like this from now on' checkbox is grayed out! I cannot permanently save this setting. This is true on this particular computer. On a different computer that checkbox is NOT grayed out and I can save the setting.

I've looked through the various preferences and cannot find what controls this checkbox. How do I enable it so I can save these program settings?

I am running Thunderbird 52.5.2 (64-bit) on Slackware64 14.2. I have an almost-solved problem. I have a user that likes to forward messages with attachments, but modify the attachment in the forward pane. This saves him from having to first save-to-disk, modify, then re-attach. When right-clicking on an attachment in the forward pane there is an 'Open' option. Clicking on that offers to open the file with some arbitrary application (in this case Foxit Reader, regardless of the file type!). I was able to solve a similar problem some months ago opening normal attachments (in inbox, not forwarding) by clicking on 'Other' in this Open dialog and browsing to the location of the appropriate executable (e.g. LibreOffice). However, it appears that that setting is not applied when opening an attachment in the forward pane. Ok, annoying, but no worries, I just followed the same procedure as before: selected 'Other', browsed to the executable location, selected (in this case) swriter. Here's the problem -- I can select the right executable, and it will open the attachment appropriately, but the 'Do this for files like this from now on' checkbox is grayed out! I cannot permanently save this setting. This is true on this particular computer. On a different computer that checkbox is NOT grayed out and I can save the setting. I've looked through the various preferences and cannot find what controls this checkbox. How do I enable it so I can save these program settings?

所有回复 (5)

more options

The box for 'Do this for files...' is greyed out when the attachment for which you are trying to set the default application is incorrectly encoded. This is caused at the sender's end, but the usual way to correct it at the receiver's end is to receive an attachment sent from an email that encodes the attachment properly. I have often found that sending an attachment to myself from a gmail or hotmail account (through webmail) works, but it may also work if you send yourself an attachment through an account set up in TB. Once you set the default app, i.e. the box is not greyed out, the association is applied even for future, mis-encoded attachments.

more options

Hmmm. I can open these attachments just fine from the message in the inbox. It's when I forward that message and try to open the attachment in the Forward pane that I have a problem. Why would the message be encoded properly when received by Thunderbird, but not encoded properly when Thunderbird forwards?

To test, I sent 3 attachments from Thunderbird on Linux (.docx, .doc and .xlsx), to a Thunderbird recipient on Linux. Again, all attachments open when the message is opened in the inbox. When I forward the message, I get interesting results.

In the Forward pane, when I right-click/open the .docx file nothing happens at all.

When I right-click/open the .doc file it opens in LibreOffice immediately, no "Open as" dialog.

When I right-click/open the .xlsx file, I get the "You have chosen to open" dialog, but the filename is /tmp/nsmail-45.tmp. The "Do this automatically ..." button is grayed out.

So, the .xlsx attachment is somehow stored as a .tmp at this point whereas the .doc file is stored as nsmail-22.doc is able to be opened.

I don't think this is an encoding issue. I think it has to do with how the Forward function deals with editing attachments and how it names the saved temporary files.

Interestingly, the attachments in the first message I tested prior to my OP were sent from mailx, not Thunderbird. I see that ALL the attachments in that message end up with the .tmp file type, even the .doc attachment.

Is this something I can control or is this just the way it is, too bad?

由Mark Foley于修改

more options

This raises that delightful question about peoples' expectations. I wouldn't even try to edit an attachment, because as an attachment it doesn't have a distinct identity. I'd save it, edit it, then re-attach it. That means I have full control over what tools I can choose between to do the editing, and I have a copy of the modified attachment for myself.

If I were able to use Thunderbird to edit the attachment in place, then I would know I am working with a temporary, nay virtual, file. I don't know how well other tools will work with this (particularly if they are file oriented) and I don't expect to have any copy of the revised edition apart from might be stored as an attachment in my Sent folder.

Maybe my approach is coloured by my working in a regulated industry (which industries aren't regulated?) where generally knowing issue numbers and keeping track of versions is rather important; so an ad-hoc edit that has no traceability is just too dangerous.

So, I wouldn't have even tried to do what your user wants to do.

If it's a light-hearted forwarding of a joke where none of that above applies, I'd forward it inline where I can edit it within Thunderbird. But, admittedly, that's good only for a limited range of content type.

由Zenos于修改

more options

Here is a fairly common problem: you receive a message with attachments, and everything works properly as far as opening or saving the attachments, as helper applications are defined for all attachment types in Options/Attachments/Incoming, i.e. no greyed out 'Do this ... from now on'.

Then, you forward the message, expecting that the recipient will also encounter no issues with the attachments. But very often the attachments are not visible to the recipient, for reasons that are not obvious. So, it turns out the safest policy is to always save the attachments from the original message, then attach them to the forwarded message like any other attachment, first deleting the files that appear to be attached when you select Forward.

more options

Zenos: the user is a lawyer and the files in question are being sent back and forth to another party for modification and refinement. In his case he'd rather NOT save the document before modifying because a) it takes time and b) it is preferable to not have traces of in-process, possibly confidential legal documents accidentally laying around on the disk.

Zenos/sfhowes: I understand the reasoning behind saving docs first before attaching -- I've never thought to try what this user is doing. However, the problem here is that this user used Thunderbird on Windows before we switched his workstation to Linux in an effort to move away from Microsoft. The Windows Tbird (52.5.0) has no problem with this and the user got used to doing this procedure routinely, and liked it! On Windows all tempfiles have the proper extention: nsmail-1.xlsx, nsmail-2.docx, etc. On Linux some seem to have the proper extension (nsmail-22.doc), most do not (.xslx -> /tmp/nsmail-45.tmp).

As a programmer, I am well aware that users can make use of my programs in unintended way. However, when I upgrade or rewrite the application, I need to consider these novel and ultimately depended upon uses in the new version or else I'm in for an earful of pain.

Unless one of you knows of a way to make the temp files have the same file type as the original file, I suppose there is no solution to this. In that case I'll make a bug report, although I imagine this would not be a high priority. Still, consistent functionality, intended or not, should be maintained among platforms. Otherwise, it will be increasingly difficult to convince users to change from Windows; something NOT in the interest of Mozilla.