E-Mail APPLICATION Configuration Service Provider
OMA considers each transport to be an application and requires a corresponding APPLICATION Configuration Service Provider.
Note This Configuration Service Provider is managed over the OMA Client Provisioning (formerly WAP) protocol. For OMA DM, you use the EMAIL2 Configuration Service Provider to create a POP3 or IMAP4 account.
The following list shows the supported EMAIL transports:
- 110, for POP3
- 143, for IMAP
- 25, for SMTP
The following image shows the Configuration Service Provider in tree format as used by OMA Client Provisioning.
.gif)
In the root characteristic, the default security roles are defined. The default security role maps to each subnode unless specific permission is granted to the subnode. The following table shows the default settings
| Permissions | Read/Write |
| Roles allowed to query and update setting | Manager
Operator Operator - TPS |
Characteristics
- APPLICATION
The root node for the APPLICATION object. - APPAUTH
This characteristic is used to specify authentication information - APPADDR
This characteristic is used specify the DM server address - PORT
This characteristic is used in the APPADDR characteristic.
Parameters
APPID
Differentiates application protocols. This parameter is used in the APPLICATION characteristic.The following table shows the port numbers that are used to identify the individual APPLICATION Configuration Service Providers.
- 110, for POP3. port numbers that are used to identify
- 143, for IMAP.
- 25, for SMTP.
You can specify only one folder for each APPLICATION section. The folder should be defined outside of any resource that uses the NAME parameter.
APPIDs must be registered with Open Mobile Alliance (OMA). When you register an APPID, you should also register application-specific parameters that are not defined in the OMA Client Provisioning XML schema.
The following table shows the default settings
Permissions Read/Write Data type String AAUTHNAME
Authentication name. This is a Messaging specific issue. This parameter is used in the following APPIDs:- 110, Required for POP3. Used in the APPAUTH characteristic.
- 143, Required for IMAP. Used in the APPAUTH characteristic.
The following table shows the default settings
Permissions Read/Write Data type String AAUTHSECRET
This parameter is used for the Login password for POP mailbox.The following table shows the default settings.
Permissions Read/Write Data type String ADDR
Specifies the address of receiving POP3 host. If there's no need to specify PORT information then APPLICATION/ADDR can be used instead of APPADDR characteristic.The following table shows the default settings.
Permissions Read/Write Data type String FROM
Specifies the user's E-Mail address.Note This parameter is used only when the APPID is 25.
Format as specified in RFC822. The field name corresponds to FROM field in message header as specified in RFC822. This field can hold Nickname according to RFC 2822 (E.g. "Nickname" <nick.name@domain.com>).
The following table shows the default settings.
Permissions Read/Write Data type E-Mail address NAME
The E-mail setting name shown to the user.The following table shows the default settings.
Permissions Read/Write Data type String PORTNBR
Specifies the port number to connect to. Use 110 or 995 or some non-standard port number.The following table shows the default settings.
Permissions Read/Write Data type String PROVIDER-ID
This parameter is used to Used to bind SMTP and POP3 settings together, to identify an application service access point. It is in the APPLICATION characteristic..The following table shows the default settings.
Permissions Read/Write Data type String TO-NAPID
This parameter specifies the NAPID of the access point. If multiple TO-NAPID parameters are specified, only the first TO-NAPID will be stored.The following table shows the default settings.
Permissions Read/Write Data type String
See Also
APPLICATION Configuration Service Provider
Send Feedback on this topic to the authors