Mapping OMA WAP XML to Email2 Configuration Service Provider (POP3)
The following table shows OMA WAP Configuration Service Provider parm names.
Characteristic | Parm name | Values | Description | EMAIL2 Configuration Service Provider |
---|---|---|---|---|
APPLICATION | APPID | 110 | n/a | SERVICETYPE |
APPLICATION | PROVIDER-ID | N/A | Used to bind SMTP and POP3 (or IMAP) settings together. | Used by Configuration Service Provider but not stored. |
APPLICATION | NAME | N/A | Email setting name shown to the user. | SERVICENAME |
APPLICATION | TO-NAPID | NAPID of access point | The network access point used. | Stored and used to determine network connection |
APPADDR | ADDR | N/A | Specifies the address of the receiving POP3 host. If there is no need to specify PORT information then APPLICATION/ADDR can be used instead of APPADDR characteristic. | INSERVER |
APPADDR | ADDRTYPE | IPV6 | Defines the type of the value in the ADDR parameter. | Not required. |
PORT | PORTNBR | 110 is the default port.
995 or a non-standard port number |
Port number to connect to. | INPORTNBR
(new parm name) |
PORT | SERVICE | 110 default,
STARTTLS, 995 |
Indicates the protocol used. It is either Secure or Unsecure. If the value is STARTTLS then Secure POP over TLS should be used, as specified in RFC2595.
Value 110 indicates an Unsecure POP connection to the port specified in PORTNBR. 995 indicates that a Secure connection is made to the port specified in PORTNBR. |
Not required. |
APPAUTH | AAUTHTYPE | LOGIN, default.
APOP, CRAM-MD5, DIGEST-MD5, GSSAPI, KERBEROS_V4, PLAIN, SKEY |
Specifies the authentication mechanism used. | Not required. |
APPAUTH | AAUTHNAME | N/A | Login name for POP mailbox | AUTHNAME |
APPAUTH | AAUTHSECRET | N/A | Login password for POP mailbox | AUTHSECRET |
New and Unsupported OMA WAP Configuration Service Provider Parm Names
The following table shows the new and unsupported OMA WAP Configuration Service Provider parm names.
Parm name | Description |
---|---|
APPID | APPID maps to SERVICENAME and is used to identify whether the XML blob is configuring POP3, IMAP or SMTP settings. The mapping is not direct. The mapping is as follows:
|
PROVIDER-ID | Used by the Configuration Service Provider but not stored.
This parm name is only used at provisioning time by the Configuration Service Provider to link SMTP to POP and IMAP XML. PROVIDER-ID is an arbitrary unique ID, not a GUID, which is only used to bind POP3 and IMAP to SMTP settings together in a single account. It is used specifically in cases where an OMA WAP XML blob is used to create multiple email accounts. |
TO-NAPID | Stored and used to determine which network connection to use.
TO-NAPID uses a text value from the Operator to identify the network connection name to be used by the provisioned account. The Operator friendly name for the connection is mapped to an actual Connection Manager GUID. For Email provisioning, identify and bind the account to a network connection GUID as follows:
|
ADDRTYPE | Not supported. Not required.
Used to specify whether an address is IPV6 or IPV4. Windows Mobile Version 5.0 supports IPV6 address formats so no address format designation is necessary. |
PORTNBR | Maps to a new parm name to specify a port number
Maps to new INPORTNBR, that is a new parm name for setting the port number of an account. |
SERVICE | Not supported. Not required.
The following three values are supported for determining the type of secure connection to use when connecting to a POP3 server:
Messaging is not required to use this setting because it queries the server with multiple attempts to establish an SSL connection. |
AAUTHTYPE | Not supported. Not required.
Messaging queries the server to find out what authentication method is supported and has an internal prioritization for which to use. There is no way at the transport level to require the use of a certain authentication method. |
See Also
APPLICATION Configuration Service Provider | APPLICATION E-Mail Configuration Service Provider for POP3 Example | Email2 Configuration Service Provider Mapping to OMA DM E-mail XML
Send Feedback on this topic to the authors