How different versions of Outlook and Exchange deal with HTML message body?

Published Nov 17 2004 09:34 AM 1,173 Views

This post provides a brief explanation of how the body of a message (HTML in particular) is handled by the different versions of Outlook (Outlook 97, Outlook 98, Outlook 2000, Outlook XP and Outlook 2003) and Exchange (Exchange 5.5, Exchange 2000, and Exchange 2003). We got a question related to this in one of our earlier postings.

For the Exchange server:

Exchange 5.5 doesn't support HTML messages and can only support clients that use the rich text (stored on the server under PR_RTF_COMPRESSED) representation of the body.

Exchange 2000 can handle both Rich Text and HTML messages and can convert between them when asked by clients.

Exchange 2000 also has a feature that determines the best body of a message and returns the best body when requested by a client.

Exchange 2003 is the same as Exchange 2000 except it has added capability for security filtering of HTML which is primarily used by Outlook Web Access. This feature was to remove potentially dangerous content from HTML, which could create virus or do other harm.

For the Outlook client:

Outlook 97 doesn't support retrieving the body from the server as HTML and will only ask the server for the Rich Text format representation of the body. This means that it will always ask the Exchange server for the Rich text format (PR_RTF_COMPRESSED) of a message and any conversion to a different format (text/HTML) will occur on the client.

Outlook 98 started supporting HTML bodies and it can handle retrieving both the HTML (PR_HTML) and Rich Text (PR_RTF_COMPRESSED) representations of the body. It will ask for the HTML body only if it determines that the server supports it otherwise it will ask for the Rich Text body.

Outlook 2000 behaves same as Outlook 98.

Outlook XP is capable of using the best body feature of the Exchange server. The best body feature can only be used when in online mode and won't work properly for offline mode.

Outlook 2003 supports best body feature in both online and offline modes. The feature is also enabled for cache mode resulting in the same body handling logic for both PST and OST. Other than those, it works the same as Outlook XP.

The converter library (used for doing client/server side conversion between HTML/Plain Text/Rich Text) is different in each Outlook/Exchange version and as such the output can change slightly between Outlook/Exchange versions.

- Je Seog Park

7 Comments
%3CLINGO-SUB%20id%3D%22lingo-sub-609862%22%20slang%3D%22en-US%22%3EHow%20different%20versions%20of%20Outlook%20and%20Exchange%20deal%20with%20HTML%20message%20body%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-609862%22%20slang%3D%22en-US%22%3E%3CP%3E%3C%2FP%3E%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EThis%20post%20provides%20a%20brief%20explanation%20of%20how%20the%20body%20of%20a%20message%20(HTML%20in%20particular)%20is%20handled%20by%20the%20different%20versions%20of%20Outlook%20(Outlook%2097%2C%20Outlook%2098%2C%20Outlook%202000%2C%20Outlook%20XP%20and%20Outlook%202003)%20and%20Exchange%20(Exchange%205.5%2C%20Exchange%202000%2C%20and%20Exchange%202003).%20We%20got%20a%20question%20related%20to%20this%20in%20one%20of%20our%20earlier%20postings.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E%3CEM%3E%3CSTRONG%3EFor%20the%20Exchange%20server%3A%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EExchange%205.5%20doesn't%20support%20HTML%20messages%20and%20can%20only%20support%20clients%20that%20use%20the%20rich%20text%20(stored%20on%20the%20server%20under%20PR_RTF_COMPRESSED)%20representation%20of%20the%20body.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EExchange%202000%20can%20handle%20both%20Rich%20Text%20and%20HTML%20messages%20and%20can%20convert%20between%20them%20when%20asked%20by%20clients.%20%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EExchange%202000%20also%20has%20a%20feature%20that%20determines%20the%20best%20body%20of%20a%20message%20and%20returns%20the%20best%20body%20when%20requested%20by%20a%20client.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EExchange%202003%20is%20the%20same%20as%20Exchange%202000%20except%20it%20has%20added%20capability%20for%20security%20filtering%20of%20HTML%20which%20is%20primarily%20used%20by%20Outlook%20Web%20Access.%20This%20feature%20was%20to%20remove%20potentially%20dangerous%20content%20from%20HTML%2C%20which%20could%20create%20virus%20or%20do%20other%20harm.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E%3CEM%3E%3CSTRONG%3EFor%20the%20Outlook%20client%3A%3C%2FSTRONG%3E%3C%2FEM%3E%20%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EOutlook%2097%20doesn't%20support%20retrieving%20the%20body%20from%20the%20server%20as%20HTML%20and%20will%20only%20ask%20the%20server%20for%20the%20Rich%20Text%20format%20representation%20of%20the%20body.%20This%20means%20that%20it%20will%20always%20ask%20the%20Exchange%20server%20for%20the%20Rich%20text%20format%20(PR_RTF_COMPRESSED)%20of%20a%20message%20and%20any%20conversion%20to%20a%20different%20format%20(text%2FHTML)%20will%20occur%20on%20the%20client.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EOutlook%2098%20started%20supporting%20HTML%20bodies%20and%20it%20can%20handle%20retrieving%20both%20the%20HTML%20(PR_HTML)%20and%20Rich%20Text%20(PR_RTF_COMPRESSED)%20representations%20of%20the%20body.%20It%20will%20ask%20for%20the%20HTML%20body%20only%20if%20it%20determines%20that%20the%20server%20supports%20it%20otherwise%20it%20will%20ask%20for%20the%20Rich%20Text%20body.%20%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EOutlook%202000%20behaves%20same%20as%20Outlook%2098.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EOutlook%20XP%20is%20capable%20of%20using%20the%20best%20body%20feature%20of%20the%20Exchange%20server.%20The%20best%20body%20feature%20can%20only%20be%20used%20when%20in%20online%20mode%20and%20won't%20work%20properly%20for%20offline%20mode.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EOutlook%202003%20supports%20best%20body%20feature%20in%20both%20online%20and%20offline%20modes.%20The%20feature%20is%20also%20enabled%20for%20cache%20mode%20resulting%20in%20the%20same%20body%20handling%20logic%20for%20both%20PST%20and%20OST.%20Other%20than%20those%2C%20it%20works%20the%20same%20as%20Outlook%20XP.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3EThe%20converter%20library%20(used%20for%20doing%20client%2Fserver%20side%20conversion%20between%20HTML%2FPlain%20Text%2FRich%20Text)%20is%20different%20in%20each%20Outlook%2FExchange%20version%20and%20as%20such%20the%20output%20can%20change%20slightly%20between%20Outlook%2FExchange%20versions.%3C%2FFONT%3E%3C%2FP%3E%20%3CP%3E%3CFONT%20face%3D%22Verdana%22%20size%3D%222%22%3E-%20%3CA%20href%3D%22http%3A%2F%2Fblogs.msdn.com%2Fexchange%2Farticles%2F256722.aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EJe%20Seog%20Park%3C%2FA%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-609862%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eall%20posts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Edevelopment%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Version history
Last update:
‎Jul 01 2019 03:01 PM
Updated by: