Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Emailing 'file:' URLs to both PC and Mac users Network
I have figured out how to send email hyperlink files to both Windows and Macs users at work. These files comes off a linux file server; the Windows users are using 2003 Exchange servers, and we have various Mac users. The hyperlink file in the email that you send to Mac users is different than the hyperlink file that you would send to a Windows users. In the end, however, both Windows and Mac users are able to click on a hyperlink to open a file off the server.

DISCLAIMER: Even though this works for me, it doesn't necessary mean that it will work for you. Success depends on the file server, Exchange server, ports and privileges, syntax, etc. This hint provides clues on how to set up hyperlinked file such that you may be able to send them to both Macs and Windows users via email. You will probably have to experiment a little (or a lot) to get this to work for you.

Here are the details of how I was able to get this to work. First, make sure that your email is formatted in plain text; it doesn't work for me with my email formatted in HTML. The format is as follows:

To send to Mac users: First, make sure that the server is mounted, and then use the following format:
file://localhost/Volumes/name_of_Volume/path_to_name_of_file
If the filename and/or path contains spaces, replace them with %20:
file://localhost/Volumes/name_of_Volume/path%20to%20name%20of%20file
To send to Windows users: Since their server drives are automatically automounted, you can skip that step for them. Use the following link format:
file://domain_name/path_to_name_of_file
And again, if the filename and/or path contains spaces, replace them with %20:
file://domain_name/Documents/path%20to%20name%20of%20file
Whenever I send a link to a file now, I include both formats so the end user can click on the appropriate hyperlink. Using my Mac at work has just gotten a little easier.
    •    
  • Currently 1.00 / 5
  • 1
  • 2
  • 3
  • 4
  • 5
  (3 votes cast)
 
[16,651 views]  

Emailing 'file:' URLs to both PC and Mac users | 7 comments | Create New Account
Click here to return to the 'Emailing 'file:' URLs to both PC and Mac users' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Emailing 'file:' URLs to both PC and Mac users
Authored by: sylvainlemire on Aug 25, '05 12:34:35PM

This is what I do on a Mac OSX only network:

Select the enclosing folder of the file you want to send. Drag the folder on a Firefox window (dosn't work with Safari). You will be presented with a kind of directory of all the files in this folder. Control-click or right-click on the specific file and copy its link. Paste that link into your email and it should open the correct file for anybody on OSX that have the specific server already mounted.



[ Reply to This | # ]
Emailing 'file:' URLs to both PC and Mac users
Authored by: adrianm on Aug 25, '05 02:08:47PM
On the Mac, you can also have a URL like this:

smb://servername/share/path/to/file.txt
Basically, the same as the Windows one but with smb: instead of file:.

The volume will mount and the file open in the Finder, which is closer to what a Windoze machine would do.

Also, to send such a link (eg hello.txt on the desktop) to a Windoze user for a file on your mac, ensure Windows Sharing is on, then send a URL like:


smb://macname/username/Desktop/hello.txt


[ Reply to This | # ]
Emailing 'file:' URLs to both PC and Mac users
Authored by: Fillman on Aug 25, '05 07:37:14PM

Thanks for a really useful explanation. Anyone know how to solve this problem in reverse?

In our Windows Server 2003 / Internet Explorer company intranet we have clickable links to important shared files. When I click on the link in Safari or Firefox, nothing happens. If I mount the server/share point I can manually navigate to the file and open it.

Anyone know of a fix or plug-in to either browser that will let me open the file by clicking instead? I've searched here and Apple Discussions but can't find any previous solution.



[ Reply to This | # ]
Yeah, I wish OS X could do this!
Authored by: germ on Aug 25, '05 11:39:56PM
Emailing 'file:' URLs to both PC and Mac users
Authored by: roncross@cox.net on Aug 28, '05 04:09:34AM

It sounds like they are sending it to you in a way that doesn't facilitate you clicking on it and automatically opening the file. I would start with the source code in the browser and see how the hyperlink is put together.

Is it ftp:, href=3D, file:, etc... From there you will have to convert the string into a string that your mac will recognize. Once you can do this, you can then proceed to create a script that will allow you to open a file either when you copy the link or run a script that will recognize the format and automatically open it for you.

The problem you have is that you don't have control over how people send you these links. Experimenting a little or a lot can solve this for you.

After some thought, I am not sure if I can blame Apple. From what I understand now, there appears to be no clear standard when it comes to networking between Linux, Mac, and Windows systems in terms of hyperlink file format.

thx
RLC

---
rlc



[ Reply to This | # ]
Doesn't work for me
Authored by: germ on Aug 25, '05 11:35:56PM

I have found that Windows does not like the %20 instead of a space.



[ Reply to This | # ]
Doesn't work for me
Authored by: roncross@cox.net on Aug 28, '05 03:53:47AM

Experiment a little. What Windows system are you working with? Where are the files located? What Mac are you using? Are you attaching files, urls, etc...? Does forward / work instead of backwards \. Success depends on a lot of factors. You will have to experiment a little to achieve success.

Other people have posted other techniques. Try those technique and see if they help you. The point is that it is possible to get this to work for you with a little or lot of effort.

If %20 doesn't work, then try wrapping the phrase with quotes. Also make sure that you are using plain text. HTML didn't work for me.

thx
RLC

---
rlc



[ Reply to This | # ]