The previous responses are to the point.
But this is a pain in the neck. Mail is supposed to be a productivity tool,
so let's not fall into the mindset trap inhabited by the Redmond, WA crowd.
It certainly is a pain in the neck and the problem is caused entirely by the Redmond, WA crowd.
Let's read text copied from the link I provided that you seem to have missed or ignored.
Pronounced tee-neff, and short for Transport Neutral Encapsulation Format, a proprietary format used by the Microsoft Exchange and Outlook e-mail clients when sending messages formatted as Rich Text Format (RTF).
When Microsoft Exchange thinks that it is sending a message to another Microsoft e-mail client, it extracts all the formatting information and encodes it in a special TNEF block. It then sends the message in two parts - the text message with the formatting removed and the formatting instructions in the TNEF block. On the receiving side, a Microsoft e-mail client processes the TNEF block and re-formats the message.
Unfortunately, most non-Microsoft e-mail clients cannot decipher TNEF blocks. Consequently, when you receive a TNEF-encoded message with a non-Microsoft e-mail client, the TNEF part appears as a long sequence of hexadecimal digits, either in the message itself or as an attached file (usually named WINMAIL.DAT).
How do you propose Apple upgrade Mail to handle what is a proprietary/closed format used by Microslop which is a problem for all non-Microsoft e-mail clients?
The
real solution is for Microslop to use open standards and this wouldn't be a problem.
