File links doesn't works in e-mails
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
People
(Reporter: zoyi81, Unassigned)
Details
(Keywords: testcase-wanted)
Attachments
(1 file)
|
46.93 KB,
image/jpeg
|
Details |
Comment 2•16 years ago
|
||
Comment 4•16 years ago
|
||
Comment 6•16 years ago
|
||
Comment 10•14 years ago
|
||
Comment 11•14 years ago
|
||
| Reporter | ||
Comment 12•14 years ago
|
||
| Reporter | ||
Comment 13•14 years ago
|
||
Updated•14 years ago
|
Comment 14•13 years ago
|
||
Comment 15•13 years ago
|
||
Comment 16•13 years ago
|
||
Comment 17•7 years ago
|
||
Is comment 0 + 1 a sufficient testcase? And should it even work?
Comment 18•7 years ago
|
||
I think a local file reference can work IFF both the sender and the receiver shares the SAME remote file system from their PCs, for example.
So let assume the sender and the receiver are in the SAME office and both of them use a shared file system (assuming CIFS/SAMBA for windows users, or NFS and others including CIFS/SAMBA share under linux, say.).
In such a setting, the file link can and should work.
We often share the link to Google drive and other shared file service URIs in short messages, etc.
HOWEVER, I noticed in the comment 0, the URI in question looks to be in the form in the main text body,
file:////mail/attachment/filepathname
but it is shown as file:////attach/... in the link status bar.
The poster asked: "In the status bar i see bore slashes. file:\mail\attach...in link status bar can see: file:///attach/.. Why happened this. "
Indeed why.
I am not sure if the "file:///attach/..." shown as the real link which it seems that the mail server the poster uses
replaced in place of the attachment is correct URI or not for the poster's environment.
It seems more likely to be the e-mail server issue than TB itself.
Either the server at the time had an incorrect configuration that replaced the URL in an incorrect way, OR
the server produces new MIME constructs for attachment that either triggered the error in TB's mime handling OR actually the earlier MIME construct got accepted incorrectly by TB.
In either way, I think this is "WORKSFORME".
This is because
- the replacement of attachment with a link to a copy of the attachment under a directory
accessible by the e-mail server (and presumably is accessible by the clients in an office setting)
is done by e-mail server if I understand this correctly, - the report is 7-8 years old, and
- I can use firefox to access the file c:/temp/t.lst by putting file:///c:/temp/t.lst in a mail myself.
So I have no question as to if a proper CIFS/SAMBA URI in the mail text allows us to access a shared file on a remote
server in a shared environment. (They may look like file://IP-address-or-host-name/.... and the details depend on the share protocol.)
TIA
PS: I had a local virtualbox linux image trashed by an operator mistake, so to speak,
when the root partition was enlarged to allow additional kernel image to be bootable. It would take a day or two before I can access my local TB source tree... Oops.
Why I think so?
I mean I can certainly send a message that contains the following myself,
and instructs firefox to open it for me (under Windows).
file:///c:/temp/t.lst
And firefox dutifully opened it for me when I clicked on the instruction.
In the case of the original poster, unless mail/attachment is in the default server and is accessible under default drive (presumably C: under windows? I am not sure what happens here under linux.), the file is not accessible after all.
But I suspect that this mail/attachment is a directory accessible by the e-mail server.
E-mail server strips an attachment and stores it under mail/attachment directory on a file system that could be accessed remotely by the client, and puts in the link to this attachment file instead.
So my guess is that it is an issue of the particular office setting.
file:
Updated•3 years ago
|
Comment 19•3 years ago
|
||
I just send a message to myself with a file link. The link is from the system I'm using to read the e-mail. I can't open the link.
The error console:
Security Error: Content at mailbox:///...../Inbox?number=9999 may not load or link to file:///...../foo.txt.
The file and the mailbox are on the same file system. The file isn't in the Thunderbird profile. Owned by user running Thunderbird.
Using Ubuntu.
Description
•