Mapping OMA WAP XML to Email2 Configuration Service Provider (SMTP)
The SMTP schema for OMA Client Provisioning XML has many shared parm names with the POP and IMAP settings. The RT-ADDR parm is the only non-standard parm name that requires special description.
The following table shows the mapping of OMA WAP XML to Email2 Configuration Service Provider for SMTP. Standard mappings are shown as BOLD values in the table's Email2 Configuration Service Provider column.
| Characteristic | Parm name | Values | Description | E-mail2 Configuration Service Provider |
|---|---|---|---|---|
| APPLICATION | APPID | 25 | n/a | SERVICETYPE |
| APPLICATION | PROVIDER-ID | N/A | Used to bind SMTP, POP3 and IMAP4 settings together. | Used by the 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 | Used network access point. | Stored and used to determine the network connection. This is the same value for POP and IMAP, but it is stored as a unique value for SMTP. |
| APPADDR | ADDR | N/A | Specifies the address of the sending host. If there is no need to specify PORT information then APPLICATION/ADDR can be used instead. | OUTSERVER |
| APPADDR | ADDRTYPE | IPV6 | Defines the type of the value in ADDR parameter. | Not required. |
| PORT | PORTNBR | 110, default.
25 |
25 or a non-standard port number | OUTPORTNBR
(new) |
| PORT | SERVICE | 110, default.
Other values are:STARTTLS, 25 |
Indicates the protocol used. It is either secure or unsecure. If the value is STARTTLS then Secure SMTP over TLS should be used as specified in RFC2595. Value 25 indicates an Unsecure SMTP connection to the port specified in PORTNBR. | Not required. |
| APPAUTH | AAUTHTYPE | LOGIN, default.
Other values are: CRAM-MD5, DIGEST-MD5, PLAIN |
Specifies the authentication mechanism used. If it is omitted, no authentication is used. For more information see the RFC 2554 for SMTP Service Extension for Authentication. | Not required. |
| APPAUTH | AAUTHNAME | N/A | SMTP Login name. | OUTAUTHNAME |
| APPAUTH | AAUTHSECRET | N/A | SMTP login password. | OUTAUTHSECRET |
| APPLICATION | FROM | E-Mail address | Specifies your E-Mail address. Format as specified in RFC822. The field name corresponds to the FROM field in the message header as specified in RFC822. This field can hold Nickname according to RFC 2822. For example, "Nickname" <nick.name@domain.com>. | REPLYADDR |
| APPLICATION | RT-ADDR | E-Mail address | Specifies a Reply To E-Mail address. Format as specified in RFC822. The field name corresponds to the REPLY-TO field in the message header as specified in RFC822. | REPLYTOADDR
(new) |
The following table shows the non-standard parm name RT-ADDR.
| Parm name | Description |
|---|---|
| RT-ADDR | Create a new parm name REPLYTOADDR to support the RT-ADDR address. This is the address sent as the Reply-To value in the header of an email.
Windows Mobile Version 5.0 supports configuring this parm by using XML but not in the Application UI. This feature includes the transport support for Reply-To when set on a messaging store as a per-account value. |
See Also
Email2 Configuration Service Provider Mapping to OMA DM E-mail XML
Send Feedback on this topic to the authors