Have MAPIMessage try the codepage properties to get the ascii encoding, before falling back to the existing logic around content type parsing