You Are Here:

Community: Wiki

This page was last modified on 20 October 2008, at 17:57.

TSC000016 - E-mail configuration using OMA client provisioning is rejected by the device

From Forum Nokia Wiki


ID TSC000016 Creation date March 16, 2003
Platform S60 2nd Edition Devices
Category Content Subcategory Messaging


Keywords (APIs, classes, methods, functions):

Overview

E-mail configuration using OMA client provisioning is rejected by the device

Description

We have created an e-mail configuration XML file according to the examples in "Series 60 Developer Platform 2.0: OMA Client Provisioning", but did not include the FROM parameter or the SERVICE parameter in the APPLICATION parts.
When the settings reach the device, it only lists the GPRS access point that we have defined but not the POP mailbox settings.  Are the FROM and SERVICE parameters mandatory?

Solution

As is stated in the document "Series 60 Developer Platform 2.0: OMA Client Provisioning," under E-mail Example:
In general, parm values are not checked, but the FROM field must contain a valid e-mail address or the settings will be discarded. In addition, if PROVIDER-ID is defined, it must have the same value in the SMTP and POP3/IMAP settings. Transport Layer Security (TLS) is used if parm SERVICE is found and it contains the value STARTTLS.
In other words; yes, the FROM parameter MUST be given, but SERVICE is optional.

Related Wiki Articles

No related wiki articles found

Rate This

 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fwikiE2eforumE2enokiaE2ecomE2findeE78E2ephpE2fTSC000016E5fE2dE5fE45E2dmailE5fconfigurationE5fusingE5fOMAE5fclientE5fprovisioningE5fisE5frejectedE5fbyE5ftheE5fdeviceX qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZKnowledgeBaseContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZTechnicalSolutionQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqfntypeZWikiContentQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtopicQUqfnTopicZemailQ qfnZtopicQUqfnTopicZmessagingQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZKnowledgeBaseContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZTechnicalSolutionQ qfnZtypeQUqfntypeZWebpageQ qfnZtypeQUqfntypeZWikiContentQ qfnZuserE5ftagQSxmessagingX qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZKnowledgeBaseContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZTechnicalSolutionQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqfntypeZWikiContentQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ