Explaining Exchange Message formats
Exchange Server 2003 can use different Messages Formats on an e-mail domain base. By default Exchange Server 2003 uses only one default setting for delivering all messages. The default settings are suitable for many small and medium sized customers but in large messaging environments or for interoperability with non Microsoft Exchange messaging systems, it is often necessary to implement different settings for different e-mail domains. Before we start explaining the Exchange settings here are some theories and basics about Message formats.
There are two well known Message formats:
There is also TNEF which is used primarily for attachments in Outlook and Exchange.
UUENCODE is a program that allows the sending of binary Data via e-mail which allows only the sending of ASCII (American Standard Code for Information Interchange) code. The UU stands for Unix to Unix, however nowadays it is more normally called user-to-user; and encode for message encoding. The principle is like the Base64 encoding scheme. Three bytes of the binary file (24 bit) would be divided into four of 6 bytes and these 6 byte values would be associated with printable ASCII code. The first UUENCODE Implementations use ASCII code from 32 to 95.
MIME (Multipurpose Internet Mail Extensions) is a coding standard that defines the structure of E-Mails and other Internet messages. MIME is also used for declaration of content from other Internet protocols like HTTP, Desktop environments like KDE, Gnome or Mac OS X Aqua. The standard is defined in RFC 2045.
With MIME it is possible to exchange information about the type of messages (the content type) between the sender and the recipient of the message. MIME also defines the art of coding (Content-Transfer-Encoding).
These are different coding methods defined for the transportation of non ASCII characters in plain text documents and non text documents like Images, Voice and Video for transportation through text based delivery systems like e-mail or the Usenet.
The non text elements will be encoded from the sender of the message and will be decoded by the message recipient. Coding of non ASCII characters is often based on “quoted printable” coding, binary data typically using Base64-coding.
There is an extension of this Standard called S/MIME (Secure Multipurpose Internet Mail Extensions) that allows the signing and encryption of messages. There are other e-mail encryption solutions like PGP/MIME (RFC 2015 and 3156).
TNEF / WINMAIL.DAT
TNEF is short for Transport Neutral Encapsulation Format and is a proprietary file format used by Microsoft in Microsoft Outlook and Exchange Server to define a file format for attachments in e-mail messages. Attachments in this format often contain files called winmail.dat or win.dat.
This proprietary format allows Outlook users to use some advanced features but when Outlook users exchange messages with programs other than Outlook the message can get unreadable or contains the file called winmail.dat. There are third party tools that allow one to open the winmail.dat.
Internet Message Formats
There is one setting in Exchange Server 2003 that you can use to associcate specific file extensions to MIME content type.
MIME content types are usually used by browsers and e-mail clients. For example, the MIME content type application/x-msexcel is associated with the .xls file extension and refers to an Excel spreadsheet. Therefore, if a document were to display this MIME content type to a browser such as Internet Explorer, or an e-mail client such as Outlook Express, Microsoft Excel could be automatically started to view the document.
Figure 1: MIME Content types
Description of Messaging formats
A plain text message is the most accepted form of messaging format. All e-mail message readers can display text messages in plain text format.
Rich Text Format (RTF)
Exchange 2003 uses a different format of RTF messaging for messages that are delivered between Microsoft Outlook users. However, RTF is only readable by Outlook.
HTML mail is a recent implementation that makes it possible to display rich content in a message. When you use the HTML mail format, the message is sent as an HTML page, complete with tags to change the appearance of the text. The recipient's e-mail client program then formats and displays the HTML.
Plain text and HTML
Exchange 2003 can send messages to external domains as both plain text and HTML. This format appears correctly on both types of client. However, the messages become two times as large and processing takes longer. You may be able to view both the plain text and the HTML in the replies to the message.
MIME and uuencode
MIME and user-to-user encoding (uuencode) are two different methods of sending binary attachments with messages. Early e-mail client programs used uuencode as the default message format. However, most current e-mail client programs support MIME.
Message text word wrapping
Although this format is not strictly an e-mail messaging format, some earlier versions of e-mail messaging clients require that a line break is placed after the seventy-sixth or seventy-seventh character. If you do not perform this procedure, those clients can only view the first 76 characters of each line. As a result, large portions of the message may not appear.
Figure 2: Message Format
There is one default setting for Message formats for all outgoing e-mails. You can choose between MIME and UUENcode format.
If your non-Exchange users work with Microsoft Office Outlook in an IMAP4 configuration, select Provide message body as plain text. If the mail clients of your non-Exchange users do not support MAPI but support HTML-formatted messages, select the Provide message body as HTML option or the Both option to provide the message body both as plain text and as HTML (attention: significantly larger e-mails are the result).
MIME types only apply to MAPI clients, such as Outlook 2003, when they are sending e-mail to, or receiving e-mail from, non-MAPI Internet clients, such as Outlook Express.
There are some more settings that you can choose when sending messages as RTF format as you can see in the following figure.
Figure 3: Advanced settings
Exchange rich-text format
Under Exchange rich-text format, select Always use if the messaging clients of the e-mail recipient support MAPI (such as Microsoft Outlook in an IMAP4 configuration). If recipients work with non-MAPI clients, select Never use. The default, Determined by individual user settings, allows the sender of the e-mail to decide whether to send Exchange rich-text information.
Message text word wrap
Under Message text word wrap, Never use is selected by default. If the messaging clients of the recipient impose a maximum number of characters per line in SMTP messages, select Use at column and specify the number of characters per line in the corresponding text box.
Using individual message format settings for special domains
If you must use different Message formats for some special e-mail domains that use different mail systems or mail clients it is possible to create additional e-mail domains. For every additional e-mail domain you can specify individual Message Format settings.
I hope you now understand Exchange Message formats, message conversion and e-mail delivery to non Outlook clients a little better.