>I only ever use BASE 64 (MIME). The only time this will cause you a problem is if you send a mac dual fork file to another mac user. Such as an application, or any document file that uses the resource fork (disk images, some text files with style information, and who knows what else).
In those cases, the resource fork will be lost when encoded with Base64, and the file will be damaged and unusable. Two ways to avoid this, and still keep compatability. 1: Compress dual fork files with Stuffit (or a Mac friendly Zip program) before encoding them. 2: Use AppleDouble encoding. AppleDouble encoding is Base64 passed on both forks of the file, and then both resulting encoded files are attached to the email. If the recipient supports AppleDouble, then the file will be reassembled or the resource fork portion ignored and thrown out (on a PC). If they don't support AppleDouble, it will appear as two Base64 attachments, and PC users can just ignore the resource fork one (the one that starts with a % in the name). The only time AppleDouble should be a problem is if you have a really dumb PC user AND their email client doesn't support AppleDouble (Outlook Express does to the best of my knowledge), AND because they are so dumb, they can't grasp ignoring the % named file. OR, you are sending to an AOL user. AOL only seems to support Base64 encoding. AppleDouble IIRC, will make it thru, but they screw up the name of the file, so it comes thru as "%UnknownFile", although if you drop that file on something that knows how to decode AppleDouble (Stuffit, WinZip), it restores the file just fine. But AOL people aren't known for their ability to use outside software, so straight Base64 is probably best when sending to them. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
