I am working on a migration from Exchange 2003 to Exchange 2007. One of the existing remote domains has US-ASCII set as the MIME character set. This option has disappeared in Exchange 2007 and I cannot appear to find what this now translates to. The only thing I can find as a possible match (by eliminating the obvious) is Western European (Windows). Can anyone point me in the direction of how the Exchange 2003 character set choices map to those available in Exchange 2007 and Exchange 2010 Thanks

On Mon, 26 Jul 2010 14:43:01 +0000, RicochetOnline wrote: >I am working on a migration from Exchange 2003 to Exchange 2007. One of the existing remote domains has US-ASCII set as the MIME character set. This option has disappeared in Exchange 2007 and I cannot appear to find what this now translates to. The only thing I can find as a possible match (by eliminating the obvious) is Western European (Windows). Sticking with the ISO character sets is probably a better fit for the world outside Windows. --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

I would agree with you as a general rule of thumb but as I don't know the specific requirement to why this particular domain is set to US-ASCII (and finding out is a painful, if achievable process) I would like to understand if there is a direct replacement for this setting or if it has just been given a different identity and if so which is it. Thanks

On Tue, 27 Jul 2010 16:02:59 +0000, RicochetOnline wrote: > > >I would agree with you as a general rule of thumb but as I don't know the specific requirement to why this particular domain is set to US-ASCII (and finding out is a painful, if achievable process) I would like to understand if there is a direct replacement for this setting or if it has just been given a different identity and if so which is it. I guess the first quetion I'd ask is whether or not the application (or user, or whatever) is sending message that are MIME encoded. If they are they probably already include the character set in the MIME header. In any case, the US-ASCII (ANSI_X3.4-1968) character set only defined the 1st 128 characters (0x00 - 0x7f) of the possible 256 character encodings in an 8-bit storage unit. The LATIN1 (ISO_1859-1:1987) character set keeps the same definitions for the 1st 128 characters and adds definitions for the remaining 128 (0x80 - 0xff). If your messages use only 7-bit encoding there's no difference in the character representations between the two character sets. If it used 8-bit characters I guess you could say that it was a ____-shoot as to the way the 0x80 - 0xff characters were represented in the message. ref: http://tools.ietf.org/html/rfc1345 --- Rich Matheisen MCSE+I, Exchange MVP --- Rich Matheisen MCSE+I, Exchange MVP

“Eight-bit standards such as ISO/IEC 8859 and Mac OS Roman developed as true extensions of ASCII, leaving the original character-mapping intact, but adding additional character definitions after the first 128 (i.e., 7-bit) characters. This enabled representation of characters used in a broader range of languages. Still, ISO-8859-1 (Latin 1), its variant Windows-1252 (often mislabeled as ISO-8859-1), and the original 7-bit ASCII remain the most common character encodings in use today” ---------Refer to <ASCII> “The most-used characters (those in ASCII, the seven-bit code points) are common to all sets—even most proprietary ones—failure to correctly identify a character set often suffers no adverse consequences if the user is typing in English” ---------Refer to <Extended ASCII> Most supported character sets I saw are including the ASCII characters Supported Character Sets for Remote Domain ConfigurationJames Luo TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx) If you have any feedback on our support, please contact tngfb@microsoft.com