IDENTIFYING INFORMATION
#######################
APPID: 25.
APPID type: IANA.
Owner: OMA DM Working Group.
Contact: OMA DM Working Group <OMA-DM@MAIL.OPENMOBILEALLIANCE.ORG>.
Registration version: 1.
Registration timestamp: 2003-09-19.
Application description: EMail SMTP settings.  
Application reference: See RFC 2821 for SMTP definition. 

WELL-KNOWN PARAMETERS
#####################
Characteristic/name: APPLICATION/APPID.
Status: Required.
Occurs: 1/1.
Default value: None.
Used values: 25.
Interpretation: N/A.
-------
Characteristic/name: APPLICATION/PROVIDER-ID.
Status: Required.
Occurs: 0/1.
Default value: None.
Used values: N/A
Interpretation: Used to bind SMTP and POP3/IMAP4 settings together.
-------
Characteristic/name: APPLICATION/NAME.
Status: Optional.
Occurs: 0/1.
Default value: None.
Used values: N/A.
Interpretation: Email setting name shown to the user.
-------
Characteristic/name: APPLICATION/TO-NAPID.
Status: Required.
Occurs: 0/1. 
Default value: None.
Used values: NAPID of access point.
Interpretation: Used network access point.
-------
Characteristic/name: APPADDR/ADDR.
Status: Required.
Occurs: 1/1. 
Default value: None.
Used values: N/A.
Interpretation: 
	Specifies the address of sending host. If there's no need 
	to specify PORT information then APPLICATION/ADDR can be used
	instead of APPADDR characteristic.
-------
Characteristic/name: APPADDR/ADDRTYPE.
Status: Required.
Occurs: 0/1. 
Default value: None.
Used values: IPV6.
Interpretation: Defines the type of the value in ADDR parameter.
-------
Characteristic/name: PORT/PORTNBR.
Status: Required.
Occurs: 1/1. 
Default value: 25.
Used values: 25 or some non-standard port number
Interpretation: SMTP port number.
-------
Characteristic/name: PORT/SERVICE.
Status: Required.
Occurs: 0/1. 
Default value: 25.
Used values: STARTTLS, 25.
Interpretation: 
	Indicates the used protocol, which 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
	unsecure SMTP connection to port specified in PORTNBR.
-------
Characteristic/name: APPAUTH/AAUTHTYPE.
Status: Required.
Occurs: 0/1.
Default value: None.
Used values: CRAM-MD5, DIGEST-MD5, LOGIN, PLAIN.
Interpretation: 
	Specifies the used authentication mechanism. If omitted 
	no authentication is used. See the RFC 2554 for SMTP Service
	Extension for Authentication.
-------
Characteristic/name: APPAUTH/AAUTHNAME.
Status: Optional.
Occurs: 0/1.
Default value: None.
Used values: N/A.
Interpretation: SMTP Login name.
-------
Characteristic/name: APPAUTH/AAUTHSECRET.
Status: Optional.
Occurs: 0/1.
Default value: None.
Used values: N/A.
Interpretation: SMTP login password.
-------

APPLICATION-SPECIFIC PARAMETERS
###############################
Characteristic/name: APPLICATION/FROM
Status: Required.
Occurs: 1/1. 
Default value: None.
Used values: E-Mail address. 
Interpretation: 
	Specifies own E-Mail address. Format as specified in RFC822.
	The field name corressponds 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>).
-------
Characteristic/name: APPLICATION/RT-ADDR
Status: Optional.
Occurs: 0/1. 
Default value: None.
Used values: E-Mail address. 
Interpretation: 
	Specifies an reply to E-Mail address. Format as specified in RFC822.
	The field name corressponds to REPLY-TO field in message header 
	as specified in RFC822.
-------

PARAMETER VALUES
################
Characteristic/name/parameter: APPAUTH/AAUTHTYPE/CRAM-MD5.
Status: Optional.
Interpretation: 
	Indicates that Challenge-Response Authentication 
	Mechanism should be used as defined in RFC2195.

Characteristic/name/parameter: APPAUTH/AAUTHTYPE/DIGEST-MD5.
Status: Optional.
Interpretation: 
	Indicates that HTTP Digest Access Authentication 
	should be used as defined in RFC2831.

Characteristic/name/parameter: APPAUTH/AAUTHTYPE/LOGIN.
Status: Optional.
Interpretation: 
	Indicates that the LOGIN authentication mechanism should
	be used as implemented in Microsoft Exchange.

Characteristic/name/parameter: APPAUTH/AAUTHTYPE/PLAIN.
Status: Optional.
Interpretation: 
	Indicates that the PLAIN authentication mechanism should 
	be used as defined in RFC2595.

Characteristic/name/parameter: PORT/SERVICE/STARTTLS.
Status: Optional.
Interpretation: 
	Indicates that secure connection should be negotiated
	as specified in RFC2487.

EXAMPLE
#######
<characteristic type="APPLICATION">
  <parm name="APPID" value="25"/>
  <parm name="PROVIDER-ID" value="MyMail"/>
  <parm name="TO-NAPID" value="IAP1"/>
  <parm name="FROM" value="first.second@mymail.com"/>
  <characteristic type="APPADDR">
    <parm name="ADDR" value="smtp.mail.com"/>
    <characteristic type="PORT">
      <parm name="PORTNBR" value="25"/>
      <parm name="SERVICE" value="STARTTLS"/>
    </characteristic>
  </characteristic>
  <characteristic type="APPAUTH">
    <parm name="AAUTHTYPE" value="CRAM-MD5"/>
    <parm name="AAUTHNAME" value="username"/>
    <parm name="AAUTHSECRET" value="password"/>
  </characteristic>
  <parm name="RT-ADDR" value="first.second@mymail.com"/>
</characteristic>

<characteristic type="APPLICATION">
  <parm name="APPID" value="25"/>
  <parm name="FROM" value="first.second@mymail.com"/>
  <parm name="ADDR" value="smtp.mail.com"/> 
</characteristic>

###END###