On Wednesday, October 22, 2003, 6:27:42 PM, Daniel wrote in message: mid:[EMAIL PROTECTED] DR> It is possible that the Apple Mailer doesn't support UUEncode. MIME DR> seems to be quite common amongst e-mail clients.
Hi Daniel, As I said I sent it again as MIME rather than UUEncode and it still arrived scrambled. My correspondent sent me this reply about it today - you'll see he has figured out what was happening, but what I'd like to know is why? I certainly did not compress the file - it left here as plain text and came back to me as plain text when I mailed it to my other account, but this is what he says: "The bad news is that when I looked at this second attached file, it was all gibberish just like the first. The good news is that I am a little bit of a techie myself. Looking at the gibberish, it struck me odd that there were no blank spaces or repeated characters or any words standing out. It did not look like a word processing file. I began to wonder whether the file had been compressed. So, I ran a little experiment. I replaced the extension ".txt" with ".zip". Then, I asked my computer to decompress the file. Voila'! It became a readable text file of the will of Elizabeth Docwra. So, the file you sent was really a compressed file and should have had the extension ".zip" instead of ".txt" at the end of the title." Any thoughts as to why/where this may be happening? My correspondent uses comcast.net as his ISP - could it be something they are doing to the attachment - perhaps as an anti-virus measure? I can't see it being my ISP (Freenetname) or the one I mailed myself would have been treated the same way. -- Cheers, Anne Flying high with The Bat! v2.00.6 on Windows 98 4.10 Build 2222 Visit The Bat! Users' Unofficial Help Forum http://the-bat-forums.donzeigler.com ________________________________________________ Current version is 2.01.3 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
