CodepageMode Property

Indicates how to convert message content between Internet codepages and Windows codepages. MailBee performs this conversion when the message is decoded from raw data into Message object.

Consider setting this property if "???" instead of international characters appear in messages after decoding.

Another case to set this property is to tell MailBee how to handle Unicode content (UTF7/UTF8) because such content cannot be represented in ordinal 8bit characters.

Options supported:

0 - (default value) Convert to desired codepage (specified in Codepage property value).

Recommended for local use (such as mail clients for Windows). Unicode content (presented in UTF7/UTF8) will be converted to desired Codepage. Unicode characters that do not translate to 8bit characters of desired Codepage will be replaced with "?"
1 - Convert to Windows counterpart of the Internet codepage of the source content.

Recommended for Unicode-enabled server environments (such as international web-based mail clients and mail systems).

UTF7/UTF8 content is not converted to 8bit and no extended characters are lost. To display UTF7/UTF8 content on the web page, set the page's codepage and charset to UTF7/UTF8. The code below sets UTF8 charset in ASP:

Response.CodePage = 65001
Response.CharSet = "utf-8"
2 - UTF7 and UTF8 will be converted to desired codepage specified in Codepage property value while, other Internet codepages will be converted to their Windows counterparts. In other words, option 0 is used for UTF7/UTF8 and option 1 is used for the rest of Internet codepages.

Recommended for server environments where complicated Unicode support is not critical (most web applications and mail systems)
3 - nothing will be converted.

Recommended for displaying HTML contents in its original charset. The original charset of the message can be determined via CharsetOriginal property.
+4 - ignore CodepageMode settings for attachments.

By default, CodepageMode conversions are applied to all parts of the message which have charset set. Sometimes, it's not desired. For instance, a message has attachments with binary data and charset header is set but no charset conversion should take place for this binary data (this typically occurs with .PDF attachments). In this case, add 4 to the CodepageMode value to leave attachment charset intact. This setting can be combined with other CodepageMode values.

Let's imagine that source message uses "iso-2022-kr" charset (Content codepage=50225), and MailBee operates under US Windows system (System codepage=1252).

If CodepageMode=0 (default setting), MailBee decodes the message into default codepage (Codepage=1252 in this example). This allows viewing the message on US Windows system. However, symbols that cannot be represented in US Windows system will be replaced with "?".

If CodepageMode=1, MailBee decodes the message into Codepage=949 (Windows codepage for Korean). This will not allow you to view the message on US Windows system due lack of Korean fonts. However, the decoded text can be transmitted to Korean system where it can be successfully read. So, this mode is fine when machines that decode mail and display it to the user are different, and only one of them supports destination codepage.

If CodepageMode=2, MailBee will act like CodepageMode=1 because the source codepage (50225) is not a Unicode codepage.

If CodepageMode=3, MailBee will retain 50225 codepage for the message data. To display it, you'll need to specify the charset information (for instance, in <META> tag). This works for HTML only because plain-text viewers do not understand charset settings.

Note: This property is useful for decoding messages loaded from disk using ImportFromFile method or directly loaded through RawBody property. To set Codepage/CodepageMode for messages being received from POP3 server use Codepage/CodepageMode properties of POP3 object.

Value Type:	Long

Parameters:	None

Usage example:

Dim Msg
'Using visual basic to create object
Set Msg = CreateObject("MailBee.Message")
'Using ASP to create object
'Set Msg = Server.CreateObject("MailBee.Message")
'In ASP use Response.Write instead of MsgBox

Msg.CodepageMode = 1 ' Always autodetect codepage. Codepage property will be ignored

Msg.ImportFromFile "C:\msg_with_international_symbols.eml"
MsgBox Msg.BodyText