On 8/25/04 10:57 AM, Allen Watson deftly typed out: >> I have one or two more questions that I forgot to ask first time around. Do >> both/either of these methods create an RFC-822 MIME encoded attachment if my >> prefs are set to "Encode for any computer"? Or do I have to select "Encode >> for Windows (Base 64/MIME) encoding in each individual email window? > > "Encode for any computer" uses Apple-Double. If you want the Base 64/MIME > encoding you need to select it. But, to be honest, I don't really know if > that is the same as the RFC-822 MIME or not.
The answers to Dan's two questions are, respectively, yes and no. RFC822 is the standard defining the format of email messages. Messages exported from Entourage by drag-n-dropping are RFC822 compatible files. Apple-Double is an RFC-specified method of using MIME (Base64) encoding to preserve Macintosh specific information. In very basic terms, using it to attach a file on the Macintosh creates two MIME-encoded attachments, one for the data fork and one for the resource fork (Type and creator codes are not part of the resource fork and do not count in this discussion). If a file has no resource fork, then only one MIME attachment is created. Messages exported by Entourage don't have a resource fork. So, to summarize...drag-n-dropping messages and attaching them with "Encode for any computer" as your default, will produce your requested results (notice I said "requested" rather than expected :-). -Remo Del Bello -- "We are like tenant farmers chopping down the fence around our house for fuel when we should be using nature's inexhaustible sources of energy - sun, wind and tide. I'd put my money on the sun and solar energy. What a source of power! I hope we don't have to wait until oil and coal run out before we tackle that." - Thomas Alva Edison (1847-1931) -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
