>What am I doing wrong? Is there a way to make sure the url hangs together >in transit? I'll be curious to see how the above url looks when this post >comes back to me.
You got some help already, and I'm hopping in a little late, but I'll toss in my advice too. 1. Like Martin said, make sure you put the correct 3 letter extension on the files. If you don't, Windows will surely choke (and in fact, many other OS's will, simple because without the extension, the web server may not know what kind of file it is, and it may try to send it as text instead of binary). 2. Put the URL in angle brackets. < and > should be at the start and finish of the URL. ie: <http://members.cox.net/billmac22/Bill%20with%2054%20pound%20white%20sea%20 bass> The brackets will tell a URL parser where the start and end of the URL is. White space is ignored in URLs, so the line breaks will be either stripped out, or ignored by the web browser. This should restore the ability to click the URL in an email (for clients that support that) despite being broken across multiple lines. And then of course, Martin's other two points stand, although aren't as important (but good advice and will help remove possible problems). Don't use spaces, and stick with all lowercase. Many unix servers are case sensitive, so "Bill_with_fish" is a different file then "bill_with_fish". Neither of these points are a huge deal if you are using URLs, but both will make it much harder for a person to manually type the URL in the event they can't click it in the email. So as a good rule of thumb, don't use spaces and don't mix case. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
