IDENTIFYING INFORMATION
#######################
APPID: 143
APPID type: IANA.
Owner: Nokia.
Contact: smart.messaging@nokia.com
Registration version: 2.
Registration timestamp: 2003-12-19.
Application description: EMail IMAP4 settings.
Application reference: IMAP4 is defined in RFC2060.

WELL-KNOWN PARAMETERS
#####################
Characteristic/name: APPLICATION/APPID.	
Status: Required.
Occurs: 1/1.
Default value: None.
Used values: 143.
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 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 receiving IMAP4 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: 143.
Used values: 143 or 993 or some non-standard port number.
Interpretation: 
	Port number to connect to.
-------
Characteristic/name: PORT/SERVICE.
Status: Required.
Occurs: 0/1. 
Default value: 143.
Used values: STARTTLS, 143, 993.
Interpretation: 
	Indicates the used protocol, which is either secure or 
	unsecure. If the value is STARTTLS then Secure IMAP over TLS 
	should be used as specified in RFC2595. Value 143 indicates
	unsecure IMAP connection to port specified in PORTNBR. 993 
	means that secure connection is made to port specified in 
	PORTNBR.
-------
Characteristic/name: APPAUTH/AAUTHTYPE.
Status: Required.
Occurs: 0/1.
Default value: LOGIN.
Used values: 
	CRAM-MD5, DIGEST-MD5, GSSAPI, KERBEROS_V4, LOGIN, PLAIN, SKEY.
Interpretation: 
	Specifies the used authentication mechanism.
-------
Characteristic/name: APPAUTH/AAUTHNAME.
Status: Optional.
Occurs: 0/1.
Default value: None.
Used values: N/A.
Interpretation: Login name for IMAP mailbox.
-------
Characteristic/name: APPAUTH/AAUTHSECRET.
Status: Optional.
Occurs: 0/1.
Default value: None.
Used values: N/A.
Interpretation: Login password for IMAP mailbox.
-------

APPLICATION-SPECIFIC PARAMETERS
###############################
Characteristic/name: APPLICATION/MTR
Status: Optional.
Occurs: 0/1. 
Default value: None.
Used values: Any Number
Interpretation: 
	Specifies how many E-Mails to retrieve at a time.
-------

Characteristic/name: APPLICATION/RM
Status: Optional.
Occurs: 0/1. 
Default value: None.
Used values: "LATEST" or "LATEST-UNREAD"
Interpretation: 
	Specifies the method how E-Mails are retrieve.
-------

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/GSSAPI.
Status: Optional.
Interpretation: 
	Indicates that GSSAPI authentication mechanism should 
	be used as defined in RFC1508.	

Characteristic/name/parameter: APPAUTH/AAUTHTYPE/KERBEROS_V4.
Status: Optional.
Interpretation: 
	Indicates that Kerberos version 4 authentication mechanism
	should be used as defined in RFC1731.

Characteristic/name/parameter: APPAUTH/AAUTHTYPE/LOGIN.
Status: Required.
Interpretation: 
	Indicates that the LOGIN authentication mechanism should 
	be used as defined in RFC2060.

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: APPAUTH/AAUTHTYPE/SKEY.
Status: Optional.
Interpretation: 
	Indicates that SKEY authentication mechanism should be 
	used. See the RFC 2289 and RFC 2444.

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="143"/>
  <parm name="PROVIDER-ID" value="MyMail"/>
  <parm name="TO-NAPID" value="IAP1"/>
  <characteristic type="APPADDR">
    <parm name="ADDR" value="imap.mail.com"/>
    <characteristic type="PORT">
      <parm name="PORTNBR" value="143"/>
      <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>
</characteristic>

<characteristic type="APPLICATION">	
  <parm name="APPID" value="143"/>
  <parm name="TO-NAPID" value="IAP1"/>
  <parm name="ADDR" value="imap.mail.com"/>
</characteristic>

###END###