Like the sender, I am using Microsoft Exchange. All the attachment files are there in the mail message for me just as the author placed them. So, whatever the gateway did to the file, my copy of Microsoft Exchange could undo. I believe that this is just one more way Microsoft is trying to force us all into buying their products. I have a home e-mail account using Eudora, should anyone need copies of the files, e-mail me and I can either MIME or BinHex them to you. Do we need to set some sort of Standard for attachments in this listserve? In would be nice to attach files to posts that everyone could easily decode. Any suggestions? ---------- From: pic microcontroller discussion [SMTP:PICLIST@MITVMA.MIT.EDU] Sent: Monday, September 30, 1996 1:54 PM To: Multiple recipients of list PIC Subject: Re: Help on (16c84..) winmail.dat >> Can you give me a hint how to read the attachment? I may be a stupid >> question, but i can't make anything out of it? > It's not meant to be read. It's some stupid option that is on by > default in Microsoft Exchange (Send text as RTF) Before today, I'd agree completely. MS-Mail does this too. However, this specific WINMAIL.DAT contained all the text parts that Eric Rossello mentioned in his email. Actually, I'm not sure how he got all those files into it. I have taken it apart and have the 6 seperate files he sent. If Eric doesn't repost in a more usable fashion, I can repost them on request. I haven't done so since they are over 1000 lines (~40KB). > that always appends a > base64'ed or uuencoded file called winmail.dat to your email. Technically speaking, the file is added as a binary attachment. The encoding occurs when going through a gateway (Base64 is part of the MIME specification for SMTP transport on the Internet). If you use a MIME-aware user agent, the Base64 encoding is totally transparent and not visible. Lee P.S. No Microsoft products were used in the extraction of the text portions of Eric's WINMAIL.DAT attachment.