Messaging Server Supported Standards

Skip to end of metadata
Go to start of metadata

This documentation applies to Communications Suite 7 at the time of its release. The most up-to-date documentation is available at the Communications Suite Documentation Home.

Supported Standards

This appendix lists national, international, industry and de-facto standards related to electronic messaging and for which support is claimed by Messaging Server. Most of these are Internet standards, published by the RFC Editor and approved by the Internet Engineering Task Force (IETF). Standards for documents from other sources are noted.

Messaging

The following documents are relevant to national and international standards for messaging (these tables are generated automatically, so please add a note to this page rather than editing them directly if you find an error).

Software compliant with older IETF RFCs is usually compatible with newer RFCs unless the protocol version changes. Where the table mentions a newer version in parentheses and that version is not listed in a separate row, we have not made a complete assessment of compatibility but are probably compatible with the new version unless otherwise stated. Newer versions of IETF specifications often drop features that were optional, rarely used or problematic. If we implemented features of note that are present only in the older specification, the older specification is listed on a separate row in addition to the parenthetical mention.

Features with status "Experimental" or "Work in Progress" may be changed incompatibly in a future version until the specification has settled. Features with status "De Facto" may not interoperate with all software as interpretations of the de facto standard may vary.

Protocols

Reference Status Feature and Information
RFC 3501 Proposed standard IMAP (port 143) (Usage: Server Client) (Older specs: RFC2060) March 2003
RFC 2180 Informational IMAP4 Multi-Accessed Mailbox Practice (port 143) (Usage: Server Client) July 1997
RFC 2061 Informational IMAP4 Compatibility with IMAP2bis (port 143) (Usage: Server Client) (Older specs: RFC1730) December 1996
RFC 2062 Informational Internet Message Access Protocol - Obsolete Syntax (port 143) (Usage: Server Client) December 1996
RFC 2683 Informational IMAP4 Implementation Recommendations (port 143) (Usage: Server Client) September 1999
 RFC 1730 Proposed standard IMAP4 (Usage: Server) (Newer specs: RFC2060 RFC2061) December 1994
 RFC 3501 section 7.2.1 Proposed standard IMAP4rev1 (Usage: Server Client) (Older specs: RFC2060) March 2003
 RFC 3501 section 6.2.1 Proposed standard IMAP STARTTLS (Usage: Server Off-by-default) (Older specs: RFC2060) March 2003
 RFC 2246 Proposed standard TLS 1.0 as used by IMAP STARTTLS (Usage: Server Off-by-default) (Newer specs: RFC4346) January 1999
 RFC 3501 section 6.2.3 Proposed standard IMAP LOGINDISABLED Caveat: Proxies presently don't support this correctly when communicating with backend (5077412). (Usage: Server Off-by-default) (Older specs: RFC2060) March 2003
 RFC 2222 Proposed standard AUTHENTICATE (SASL) Caveat: SASLprep, added by RFC 4422, is not implemented. (Usage: Server Client) (Newer specs: RFC4422 RFC4752) October 1997
 RFC 3501 section 6.2.2 Proposed standard AUTHENTICATE (SASL) Caveat: SASLprep, added by RFC 4422, is not implemented. (Usage: Server Client) (Older specs: RFC2060) March 2003
 RFC 2595 section 6 Proposed standard IMAP AUTH=PLAIN Caveat: SASLprep, added by RFC 4616, is not implemented. (Usage: Server Client) June 1999
 RFC 2222 section 7.4 Proposed standard IMAP AUTH=EXTERNAL (Usage: Server Off-by-default) (Newer specs: RFC4422 RFC4752) October 1997
 RFC 2245 Proposed standard IMAP AUTH=ANONYMOUS (Usage: Server Off-by-default) (Newer specs: RFC4505) November 1997
 RFC 2195 Proposed standard IMAP AUTH=CRAM-MD5 (Usage: Server Off-by-default) (Older specs: RFC2095) September 1997
 RFC 2831 Proposed standard IMAP AUTH=DIGEST-MD5 Caveat: Deprecated feature, will be removed in future version. (Usage: Server Off-by-default) May 2000
 RFC 2086 Proposed standard IMAP ACL Caveat: Support for the 'p' right only works for user 'anyone' presently. (Usage: Server) (Newer specs: RFC4314) January 1997
 RFC 2087 Proposed standard IMAP QUOTA (Usage: Server) January 1997
 RFC 2088 Proposed standard IMAP LITERAL+ (Usage: Server) January 1997
 RFC 2342 Proposed standard IMAP NAMESPACE (Usage: Server) May 1998
 RFC 2359 Proposed standard IMAP UIDPLUS (Usage: Server) (Newer specs: RFC4315) June 1998
 RFC 3348 Informational IMAP CHILDREN (Usage: Server) July 2002
 RFC 3516 Proposed standard IMAP BINARY (Usage: Server) April 2003
 RFC 3691 Proposed standard IMAP UNSELECT Added in release: 6.3 (Usage: Server) February 2004
 RFC 2177 Proposed standard IMAP IDLE Added in release: 6.3 (Usage: Server Off-by-default) June 1997
 RFC 4959 Proposed standard IMAP SASL-IR Added in release: 7.0 (Usage: Server) September 2007
 RFC 4469 Proposed standard IMAP CATINATE Added in release: 7.0 (Usage: Server) April 2006
 RFC 4731 Proposed standard IMAP ESEARCH Added in release: 7.0 (Usage: Server) November 2006
 RFC 4551 Proposed standard IMAP CONDSTORE Added in release: 7.0 (Usage: Server) June 2006
 RFC 4467 Proposed standard IMAP URLAUTH Added in release: 7.0 (Usage: Server Client) May 2006
 RFC 5162 Proposed standard IMAP QRESYNC Added in release: 7.0 (Usage: Server) March 2008
 RFC 5032 Proposed standard IMAP WITHIN Added in release: 7.0 (Usage: Server) September 2007
 RFC 2221 Proposed standard IMAP Login Referrals Details: Used to detect user in transit via rehostuser utility. Added in release: 7.0 (Usage: Server Client) October 1997
 RFC 5257 Experimental IMAP ANNOTATE Added in release: 7.0 (Usage: Server) June 2008
 RFC 5267 Proposed standard IMAP CONTEXT Added in release: 7.0 (Usage: Server) July 2008
 RFC 5256 Proposed standard IMAP THREAD Added in release: 7.0 (Usage: Server) June 2008
 RFC 5256 Proposed standard IMAP SORT Added in release: 6.3 (Usage: Server Client) June 2008
 RFC 5255 Proposed standard IMAP LANGUAGE (Usage: Server Client) June 2008
 draft-daboo-imap-annotatemore-08.txt Work in Progress, subject to change IMAP X-ANNOTATEMORE Details: Implemented pre-standard different from final version. Added in release: 6.3 (Usage: Server)
RFC 1939 Standard POP3 (port 110) (Usage: Server Client) (Older specs: RFC1725) May 1996
RFC 1957 Informational Some Observations on Implementations of the Post Office Protocol (POP3) (port 110) (Usage: Server Client) June 1996
 RFC 1939 section 7 Standard POP TOP (Usage: Server) (Older specs: RFC1725) May 1996
 RFC 1939 page 12 Standard POP UIDL (Usage: Server Client) (Older specs: RFC1725) May 1996
 RFC 1939 page 13 Standard POP USER / PASS (Usage: Server Client) (Older specs: RFC1725) May 1996
 RFC 1939 page 15 Standard APOP (Usage: Server Off-by-default) (Older specs: RFC1725) May 1996
 RFC 2449 section 6.3 Proposed standard POP SASL (Usage: Server Client) November 1998
 RFC 2449 Proposed standard POP CAPA Caveat: We don't implement EXPIRE or LOGIN-DELAY. (Usage: Server) November 1998
 RFC 2449 section 6.6 Proposed standard POP PIPELINING (Usage: Server) November 1998
 RFC 2449 section 6.4 Proposed standard POP RESP-CODES (Usage: Server) November 1998
 RFC 2449 section 6.9 Proposed standard POP IMPLEMENTATION (Usage: Server) November 1998
 RFC 2595 section 4 Proposed standard POP STLS (Usage: Server Off-by-default) June 1999
 RFC 2246 Proposed standard TLS 1.0 as used by POP STLS (Usage: Server Off-by-default) (Newer specs: RFC4346) January 1999
 RFC 3206 Proposed standard POP AUTH-RESP-CODES (Usage: Server) February 2002
RFC 2821 Proposed standard SMTP Specification (port 25) (Usage: Server Client) (Older specs: RFC0821 RFC0974 RFC1869 STD0010) (Newer specs: RFC5321) April 2001
RFC 821 Standard SMTP Legacy Specification (port 25) (Usage: Server Client) (Older specs: RFC0788) (Newer specs: RFC2821) August 1982
RFC 920 Unknown Domain requirements (port 25) (Usage: Server Client) October 1984
RFC 974 Historic SMTP Mail Routing and DNS (port 25) (Usage: Server Client) (Newer specs: RFC2821) January 1986
RFC 1123 section 5 Standard SMTP Host Requirements (port 25) (Usage: Server Client) October 1989
RFC 2505 Best current practice Anti-Spam Recommendations for SMTP MTAs (port 25) (Usage: Server Client) February 1999
RFC 3848 Proposed standard ESMTP and LMTP Transmission Types Registration (port 25) (Usage: Server Client) July 2004
RFC 1428 Informational Transition of Internet Mail from Just-Send-8 to 8bit-SMTP/MIME (port 25) (Usage: Server Client) February 1993
 RFC 1652 Draft standard SMTP 8BITMIME (Usage: Server Client) (Older specs: RFC1426) July 1994
 RFC 2920 Standard SMTP PIPELINING (Usage: Server Client) (Older specs: RFC2197) September 2000
 RFC 3030 Proposed standard SMTP CHUNKING Caveat: Spec also contains BINARYMIME which has not been implemented. Added in release: 6.3 (Usage: Server Client) (Older specs: RFC1830) December 2000
 RFC 3461 Draft standard SMTP DSN (Usage: Server Client) (Older specs: RFC1891) January 2003
 RFC 2034 Proposed standard SMTP ENHANCEDSTATUSCODES (Usage: Server Client) October 1996
 RFC 3463 Draft standard Enhanced Mail System Status Codes (Usage: Server Client) (Older specs: RFC1893) January 2003
 RFC 2821 section 4.1.1.7 Proposed standard SMTP EXPN (Usage: Server) (Older specs: RFC0821 RFC0974 RFC1869 STD0010) (Newer specs: RFC5321) April 2001
 RFC 2821 section 4.1.1.8 Proposed standard SMTP HELP (Usage: Server) (Older specs: RFC0821 RFC0974 RFC1869 STD0010) (Newer specs: RFC5321) April 2001
 RFC 821 section 3.4 Standard SMTP SAML (Usage: Server Off-by-default) (Older specs: RFC0788) (Newer specs: RFC2821) August 1982
 RFC 821 section 3.4 Standard SMTP SEND (Usage: Server Off-by-default) (Older specs: RFC0788) (Newer specs: RFC2821) August 1982
 RFC 821 section 3.4 Standard SMTP SOML (Usage: Server Off-by-default) (Older specs: RFC0788) (Newer specs: RFC2821) August 1982
 RFC 821 section 3.8 Standard SMTP TURN (Usage: Server Off-by-default) (Older specs: RFC0788) (Newer specs: RFC2821) August 1982
 RFC 3207 Proposed standard SMTP STARTTLS (Usage: Server Client Off-by-default) (Older specs: RFC2487) February 2002
 RFC 2246 Proposed standard TLS 1.0 as used by SMTP STARTTLS (Usage: Server Client Off-by-default) (Newer specs: RFC4346) January 1999
 RFC 2554 Proposed standard SMTP AUTH Caveat: SASLprep, added by RFC 4422, is not implemented. Support for AUTH= mail parameter is server-only. (Usage: Server Client Off-by-default) (Newer specs: RFC4954) March 1999
 RFC 2222 Proposed standard SMTP AUTH Caveat: SASLprep, added by RFC 4422, is not implemented. Support for AUTH= mail parameter is server-only. (Usage: Server Client Off-by-default) (Newer specs: RFC4422 RFC4752) October 1997
 RFC 1985 Proposed standard SMTP ETRN (Usage: Server) August 1996
 RFC 1870 Standard SMTP SIZE (Usage: Server) (Older specs: RFC1653) November 1995
 RFC 3865 Proposed standard SMTP NO-SOLICITING (Usage: Server Off-by-default) September 2004
 SMTP AUTH=LOGIN Widely Used or De Facto SMTP AUTH=LOGIN Details: Undocumented pre-standard subset of AUTH PLAIN, needed by many clients. (Usage: Server Off-by-default)
RFC 2476 Proposed standard Message Submission Details: Superset of SMTP adding AUTH by default. (port 587) (Usage: Server Client) (Newer specs: RFC4409) December 1998
 RFC 2554 Proposed standard Submission AUTH Caveat: SASLprep, added by RFC 4422, is not implemented. Support for AUTH= mail parameter is server-only. (Usage: Server Client) (Newer specs: RFC4954) March 1999
 RFC 2222 Proposed standard Submission AUTH Caveat: SASLprep, added by RFC 4422, is not implemented. Support for AUTH= mail parameter is server-only. (Usage: Server Client) (Newer specs: RFC4422 RFC4752) October 1997
 RFC 2595 section 6 Proposed standard Submission AUTH PLAIN Caveat: SASLprep, added by RFC 4616, is not implemented. (Usage: Server Client) June 1999
 RFC 2222 section 7.4 Proposed standard Submission AUTH=EXTERNAL (Usage: Server Client Off-by-default) (Newer specs: RFC4422 RFC4752) October 1997
 Submission AUTH=LOGIN Widely Used or De Facto Submission AUTH=LOGIN Details: Undocumented, subset of AUTH PLAIN functionality. (Usage: Server Client)
 RFC 4468 Proposed standard Submission BURL Added in release: 7.0 (Usage: Server) May 2006
 RFC 4865 Proposed standard Submission Future Release Added in release: 7.0 (Usage: Server) May 2007
RFC 2251 Proposed standard LDAPv3 (port 389) (Usage: Client) (Newer specs: RFC4510 RFC4511 RFC4513 RFC4512) December 1997
RFC 1034 Standard Domain names - concepts and facilities (port 53) (Usage: Client) (Older specs: RFC0973 RFC0882 RFC0883) November 1987
RFC 1035 Standard Domain names - implementation and specification (port 53) (Usage: Client) (Older specs: RFC0973 RFC0882 RFC0883) November 1987
 RFC 1035 section 3.4.1 Standard DNS A (Usage: Client) (Older specs: RFC0973 RFC0882 RFC0883) November 1987
 RFC 3596 Draft standard DNS AAAA Details: Partial support (Usage: Client) (Older specs: RFC3152 RFC1886) October 2003
 RFC 1035 section 3.3.1 Standard DNS CNAME (Usage: Client) (Older specs: RFC0973 RFC0882 RFC0883) November 1987
 RFC 1035 section 3.3.9 Standard DNS MX (Usage: Client) (Older specs: RFC0973 RFC0882 RFC0883) November 1987
 RFC 934 Unknown DNS MX (Usage: Client) January 1985
 RFC 1035 section 3.3.12 Standard DNS PTR (Usage: Client) (Older specs: RFC0973 RFC0882 RFC0883) November 1987
 RFC 1035 section 3.3.14 Standard DNS TXT Details: For RBL and SPF. (Usage: Client) (Older specs: RFC0973 RFC0882 RFC0883) November 1987
RFC 3507 Informational ICAP Details: For Norton AV. (port 1344) (Usage: Client Off-by-default) April 2003
RFC 1928 Proposed standard SOCKS 5 (port 1080) (Usage: Client Off-by-default) March 1996
RFC 2788 Proposed standard SNMP Network Services MIB Details: Provided via NetSNMP. (port 161) (Usage: Server Off-by-default) (Older specs: RFC2248) March 2000
RFC 2789 Proposed standard SNMP Mail MIB Details: Provided via NetSNMP. (port 161) (Usage: Server Off-by-default) (Older specs: RFC2249 RFC1566) March 2000
RFC 2033 Informational LMTP Caveat: The addressing model is non-standard in order to avoid the need for the LMTP server to perform address lookups in LDAP. Third-party use of this is not supported and will not work as expected. (port 225) (Usage: Server Client Off-by-default) October 1996

Data and File Formats, Schema

Reference Status Feature and Information
RFC 822 Standard Legacy Internet Message Format (Usage: Generate Accept Process) (Older specs: RFC0733) (Newer specs: RFC2822) August 1982
RFC 2822 Proposed standard Internet Message Format (Usage: Generate Accept Process) (Older specs: RFC0822) (Newer specs: RFC5322) April 2001
RFC 2045 Draft standard Multi-purpose Internet Mail Extensions (MIME) (Usage: Generate Accept Process) (Older specs: RFC1521 RFC1522 RFC1590) November 1996
RFC 2046 Draft standard Multi-purpose Internet Mail Extensions (MIME) (Usage: Generate Accept Process) (Older specs: RFC1521 RFC1522 RFC1590) November 1996
RFC 2049 Draft standard Multi-purpose Internet Mail Extensions (MIME) (Usage: Generate Accept Process) (Older specs: RFC1521 RFC1522 RFC1590) November 1996
RFC 2047 Draft standard MIME International Headers (Usage: Generate Accept Process Normalize) (Older specs: RFC1521 RFC1522 RFC1590) November 1996
RFC 2231 Proposed standard MIME International Parameters (Usage: Accept Process) (Older specs: RFC2184) November 1997
RFC 2183 Proposed standard MIME Content-Disposition (Usage: Generate Accept Process) (Older specs: RFC1806) August 1997
RFC 1864 Draft standard Content-MD5 (Usage: Process Validate) (Older specs: RFC1544) October 1995
RFC 3458 Proposed standard Message Context for Internet Mail Details: For per-context quotas. Added in release: 6.3 (Usage: Generate Accept) January 2003
RFC 1740 Proposed standard Macintosh MIME Format (Usage: MTA Translate Off-by-default) December 1994
RFC 1741 Informational Macintosh Binhex Encoding (Usage: MTA Translate Off-by-default) December 1994
RFC 2045 section 6.7 Draft standard MIME base-64 and quoted-printable encodings (Usage: Generate Accept Process MTA Translate Validate Normalize) (Older specs: RFC1521 RFC1522 RFC1590) November 1996
RFC 1847 Proposed standard MIME multipart/signed (Usage: Process) October 1995
RFC 2480 Proposed standard Gateways and MIME Security Multiparts (Usage: Process) January 1999
RFC 3280 Proposed standard X.509 Certificate Profile Details: Generated by certutil, msgcert. Accepted by SSL/TLS. (Usage: Generate Accept Off-by-default) (Older specs: RFC2459) (Newer specs: RFC5280) April 2002
RFC 3462 Draft standard MIME multipart/report (Usage: Generate Process) (Older specs: RFC1892) January 2003
 RFC 3464 Draft standard Delivery Status Notifications (DSN) (Usage: Generate Process) (Older specs: RFC1894) January 2003
 RFC 3798 Draft standard Message Disposition Notifications (MDN) (Usage: Generate Process Off-by-default) (Older specs: RFC2298) May 2004
RFC 2442 Informational Batch SMTP (Usage: Generate Accept Off-by-default) November 1998
RFC 5228 Proposed standard Sieve (Mail Filtering Language) (Usage: Accept) (Older specs: RFC3028) January 2008
 RFC 5173 Proposed standard Sieve body Details: Includes some storage and complexity limits. Added in release: 7u3 (Usage: Accept Off-by-default) April 2008
 RFC 3894 Proposed standard Sieve :copy parameter (Usage: Accept) October 2004
 RFC 5293 Proposed standard Sieve Editheader Added in release: 6.3 (Usage: Accept) August 2008
 RFC 5228 Proposed standard Sieve Encoded-character extension Added in release: 7.0 (Usage: Accept) (Older specs: RFC3028) January 2008
 draft-freed-sieve-notary-05.txt Work in Progress, subject to change Sieve envelope-dsn, redirect-dsn Added in release: 7.0u2 (Usage: Accept)
 RFC 5183 Proposed standard Sieve Environment Added in release: 7.0u1 (Usage: Accept) May 2008
 draft-melnikov-sieve-external-lists-01.txt Work in Progress, subject to change Messaging Server Support for Externally Stored Lists Sieve Extension Details: Likely subject to incompatible change in a future version. Caveat: Implementation includes additional features not in the current specification. Added in release: 7.0u1 (Usage: Accept Off-by-default)
 RFC 5463 Proposed standard Sieve ihave Added in release: 7.0 (Usage: Accept) March 2009
 RFC 5232 Proposed standard Sieve imap4flags Added in release: 6.3p1 (Usage: Accept) January 2008
 draft-ietf-sieve-mime-loop-08.txt Work in Progress, subject to change Sieve MIME extension Caveat: Only mime extension implemented, other extensions in spec not implemented Added in release: 7.0u2 (Usage: Accept)
 RFC 5435 Proposed standard Sieve Notifications Added in release: 6.2 (Usage: Accept) January 2009
 RFC 5436 Proposed standard Sieve Notification Mechanism: mailto Added in release: 6.2 (Usage: Accept) January 2009
 RFC 5231 Proposed standard Sieve Relational Tests (Usage: Accept) (Older specs: RFC3431) January 2008
 RFC 3598 Proposed standard Sieve Subaddress (Usage: Accept) (Newer specs: RFC5233) September 2003
 RFC 5235 Proposed standard Sieve Spamtest / Virustest (Usage: Accept) (Older specs: RFC3685) January 2008
 RFC 5230 Proposed standard Sieve vacation (Usage: Accept) January 2008
 RFC 5229 Proposed standard Sieve variables Added in release: 6.3 (Usage: Accept) January 2008
RFC 952 section 1 Unknown Domain Name Syntax (Usage: Accept Validate) (Older specs: RFC0810) October 1985
RFC 1123 section 2.1 Standard Domain Name Syntax (Usage: Accept Validate) October 1989
RFC 2251 Proposed standard namingContexts of root DSE Details: Used by comm_dssetup.pl with Directory Server 6 to determine naming contexts so customer can select one to use for user/group tree. Added in release: 6.3 (Usage: Accept) (Newer specs: RFC4510 RFC4511 RFC4513 RFC4512) December 1997
RFC 2849 Proposed standard LDAP Data Interchange Format (LDIF) (Usage: Generate) June 2000
RFC 2254 Proposed standard LDAP Search Filter String Format (Usage: Generate Accept Validate) (Older specs: RFC1960) (Newer specs: RFC4510 RFC4515) December 1997
RFC 2253 Proposed standard LDAP Distinguished Name String Format (Usage: Generate MTA Translate Normalize) (Older specs: RFC1779) (Newer specs: RFC4510 RFC4514) December 1997
RFC 2255 Proposed standard LDAP URL Format (Usage: Accept Validate) (Older specs: RFC1959) (Newer specs: RFC4510 RFC4516) December 1997
RFC 3280 Proposed standard PKIX Details: Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile Caveat: As implemented by Mozilla NSS library, believed to be complete. Some new features in RFC 5280 not implemented. (Usage: Generate Accept Validate) (Older specs: RFC2459) (Newer specs: RFC5280) April 2002
ITU-T Rec. X.680, ITU-T Rec. X.690. Other National/International ASN.1 Caveat: Only the LDAP, PKIX and SNMP subsets are implemented. (Usage: Generate Accept Validate)
RFC 1738 section 3.10 Proposed standard File URL Format (Usage: Accept) (Newer specs: RFC4248 RFC4266) December 1994
RFC 3339 Proposed standard Internet Date / Time Timestamps Details: Also ISO 8601. Used in a few places that don't require mail-specific timestamp format. (Usage: Generate) July 2002
Unix /var/mail mailbox file format Widely Used or De Facto Unix /var/mail mailbox file format Details: Traditional 'From ' Unix mailbox format (multiple messages per file). Used by MTA native channel and migration tool. (Usage: Generate MTA Translate)

Charsets

Reference Status Feature and Information
ANSI X3.4-1986 Other National/International US-ASCII Details: ANSI X3.4-1986 (Usage: Accept MTA Translate Validate IMAP Search)
RFC 3629 Standard UTF-8 Details: Unicode Transformation Format 8-bit. (Usage: Accept MTA Translate Validate Normalize IMAP Search) (Older specs: RFC2279) November 2003
ISO 8859 (1-10,14,15) National/International ISO 8859 (1-10,14,15) Details: ISO 8859 family of 8-bit charsets. Several languages with proper US-ASCII subset. (Usage: MTA Translate IMAP Search)
ISO 8859 11 National/International ISO 8859 11 Details: ISO 8859 8-bit Thai with ASCII subset. Added in release: 7u3 (Usage: IMAP Search)
CNS 11643-1986, GB 2312-1980 Other National/International GB-2312 Details: Simplified Chinese, also CNS 11643-1986. (Usage: MTA Translate IMAP Search)
RFC 1842 Informational HZ-GB-2312 Details: Simplified Chinese. No MTA support. (Usage: IMAP Search) August 1995
Big5   Big5 Details: Traditional Chinese (Usage: MTA Translate IMAP Search)
GB-18030 National/International GB-18030 Details: Extended Simplified Chinese with Unicode subset. (Usage: MTA Translate)
ISO/IEC 2022-1986 Other National/International ISO-2022 Details: ISO standard technique for code-switching; very complex so everything uses a subset. Caveat: We only implement a subset of full 2022 as needed by language-specific charsets and other MTA functions. (Usage: MTA Translate IMAP Search)
RFC 1468 Informational ISO-2022-JP Details: Japanese, based on ISO 2022, JIS X 0201-1976, JIS X 0208-1990 (Usage: MTA Translate IMAP Search) June 1993
RFC 1554 Informational ISO-2022-JP-2 Details: Japanese, with additional language support, not widely used. (Usage: MTA Translate IMAP Search) December 1993
JIS X 0201-1976, JIS X 0208-1990 with EUC encoding Other National/International EUC-JP Details: Japanese. (Usage: MTA Translate IMAP Search)
RFC 1557 Informational ISO-2022-KR Details: Korean KSC 5601-1987 with ISO 2022 encoding (Usage: MTA Translate IMAP Search) December 1993
RFC 1557 Informational EUC-KR Details: Korean KSC 5601-1987 with EUC encoding (Usage: MTA Translate IMAP Search) December 1993
RFC 1489 Informational KOI8-R Details: Russian 8-bit with US-ASCII subset. (Usage: MTA Translate IMAP Search) July 1993
Windows-1250 Vendor Non-standard, subject to change Windows-1250 Details: Windows variant of ISO-8859-2 (Eastern/Central Latin) with extensions. IMAP SEARCH support new in 7u3 (Usage: MTA Translate IMAP Search)
Windows-1251 Vendor Non-standard, subject to change Windows-1251 Details: Windows variant of KOI8-R (Russian) with extensions. IMAP SEARCH support new in 7u3 (Usage: MTA Translate IMAP Search)
Windows-1252 Vendor Non-standard, subject to change Windows-1252 Details: Windows variant of ISO-8859-1 (Latin) with extensions. (Usage: MTA Translate IMAP Search)
Windows-1253 Vendor Non-standard, subject to change Windows-1253 Details: Windows incompatible variant of ISO-8859-7 (Greek) with extensions. IMAP SEARCH support new in 7u3 (Usage: MTA Translate IMAP Search)
Windows-1254 Vendor Non-standard, subject to change Windows-1254 Details: Windows variant of ISO-8859-9 (Turkish) with extensions. IMAP SEARCH support new in 7u3 (Usage: MTA Translate IMAP Search)
Windows-1255 Vendor Non-standard, subject to change Windows-1255 Details: Windows incompatible variant of ISO-8859-8 (Hebrew) with extensions. IMAP SEARCH support new in 7u3 (Usage: MTA Translate IMAP Search)
Windows-1256 Vendor Non-standard, subject to change Windows-1256 Details: Windows incompatible variant of ISO-8859-6 (Arabic) with extensions. (Usage: MTA Translate IMAP Search)
Windows-1257 Vendor Non-standard, subject to change Windows-1257 Details: Windows incompatible variant of ISO-8859-13 (Baltic) with extensions. IMAP SEARCH support new in 7u3 (Usage: MTA Translate IMAP Search)
Windows-1258 Vendor Non-standard, subject to change Windows-1258 Details: Windows Vietnamese 8-bit. IMAP SEARCH support new in 7u3 (Usage: MTA Translate IMAP Search)
RFC 2152 Informational UTF-7 Details: Use not recommended, doesn't interoperate well. (Usage: MTA Translate IMAP Search) (Older specs: RFC1642) May 1997
RFC 3501 section 5.1.3 Proposed standard IMAP Modified UTF-7 (Usage: Accept MTA Translate Validate) (Older specs: RFC2060) March 2003

Library files

Reference Status Feature and Information
RFC 1345 Informational charnames.txt Details: Defines the mnemonic character names (based on RFC 1345) used in charsets.txt (Usage: Accept) June 1992
RFC 1345 Informational charsets.txt Details: Character set definitions based on RFC 1345 (Usage: Accept) June 1992
ISO 3166 country codes Other National/International countries.txt Details: List of ISO 3166 country codes (Usage: Accept)
RFC 3066 Best current practice languages.txt Details: List of language codes (Usage: Accept) (Older specs: RFC1766) (Newer specs: RFC4646 RFC4647) January 2001
Labels:
messagingserver messagingserver Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.