On 8/26/04 11:23 AM, Remo Del Bello deftly typed out: >> Just to clarify, then, if I need to forward an email as an RFC-822 MIME >> encoded attachment, I can either 1) drag-n-drop it, then attach it, then >> send it; or 2) use Barry Wainwright's "Send Messages as Attachments v1.0.0" >> script. In either method, having my attachment prefs set to "Encode for any >> computer" will still create the needed RFC-822 MIME encoded attachment. >> >> Is all the above correct? > > Yes, that is correct. A third option is to drag the message from the message > list into an open new outgoing message window. This is just like option 1 > above, but it skips the intermediary file on the Desktop.
After sounding so sure, I decided to actually look at the source of the message. Apparently, Entourage is smart enough to recognize the attached message as an RFC822-format file and attaches the raw source with the Content-Type message/rfc822 and no encoding. This is the case with E2004's "Forward as attachment", drag-n-drop or even renaming the exported message to .txt and attaching (Entourage picks up on the type and creator code that it is a message). It doesn't matter what encoding you specify, because the attached message doesn't get encoded. The only way for you to get the attached message to be encoded (if that is *really* a requirement) is to save to the Desktop, replace the .eml file extension to something else (i.e. .txt) and wiping out at least the type code. I do this by cp'ing the file in Terminal to a new name, renaming and wiping out type & creator codes in one step. -Remo Del Bello -- "Okay...that was a little strange. When you were in that coma, did you feel your brain being damaged?" - Dr. Nick Riviera on The Simpsons -- 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/>
