Remo Del Bello at [EMAIL PROTECTED] wrote: > 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.
Sorry to belabor the topic, but I'm still unclear about this, so let me try approaching it a different way. My ISP has its own spam filters, but of course, some spam manages to get through it from time to time. According to my ISP, their filters become more "intelligent" if I forward the spam emails to a "missed spam" address as RFC-822 MIME encoded attachments. The ISP instructions say it MUST be in this format. They give instructions for doing this in Outlook Express 5 and 6, and Netscape Messenger, but not Entourage. How can I do this in Entourage 10.1.4? TIA, Dan Dixon -- 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/>
