1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE reference

    11   PUBLIC "-//OASIS//DTD DITA Reference//EN" "reference.dtd">

    12 <reference id="GUID-931F2B0C-0F7D-5819-83AF-8EC2C8988538" xml:lang="en"><title>Email

    13 Settings</title><shortdesc>The Email collection provides IMAP MTM, POP3 MTM and SMTP MTM components

    14 to support the IMAP4, POP3 and SMTP email protocols respectively. These components

    15 provide APIs to modify configuration settings of an email MTM. </shortdesc><prolog><metadata><keywords/></metadata></prolog><refbody>

    16 <section><p>The configuration settings are broadly classified as below: </p> <ul>

    17 <li id="GUID-C614F440-92D2-576C-BFFD-4C4CDBFEA092"><p> <b>Service settings:</b> Allows

    18 the messaging client to modify the settings parameters and save them. </p> </li>

    19 <li id="GUID-76F48B41-6C6A-5FDE-8A87-47C8B4F25D1B"><p> <b>Internet Access

    20 Provider (IAP) preferences setting:</b> Allows the messaging client to modify

    21 the IAP preferences and save them. </p> </li>

    22 <li id="GUID-D6247431-770B-549E-9B5C-9EE31820C3BF"><p> <b>SNAP preferences:</b> Allows

    23 the messaging client to set a SNAP identifier to use for internet access. </p> </li>

    24 </ul> </section>

    25 <section><title>Service settings</title> <p>These settings can be modified

    26 by the functions provided by the Email MTM component. Applicable settings

    27 for protocols are marked. </p> <table id="GUID-C85C1446-3106-59F4-9C02-06D7827327F6">

    28 <tgroup cols="5"><colspec colname="col0"/><colspec colname="col1"/><colspec colname="col2"/><colspec colname="col3"/><colspec colname="col4"/>

    29 <thead>

    30 <row>

    31 <entry>Setting</entry>

    32 <entry>Description</entry>

    33 <entry>SMTP</entry>

    34 <entry>POP3</entry>

    35 <entry>IMAP4</entry>

    36 </row>

    37 </thead>

    38 <tbody>

    39 <row>

    40 <entry><p>Acknowledge receipts </p> </entry>

    41 <entry><p>If the sender of an email message has requested a receipt notification,

    42 the messaging client can check this setting and compose a receipt notification

    43 message. </p> </entry>

    44 <entry><p>-</p> </entry>

    45 <entry><p>Supported </p> </entry>

    46 <entry><p>Supported </p> </entry>

    47 </row>

    48 <row>

    49 <entry><p>Bearer Mobility </p> </entry>

    50 <entry><p>If enabled, indicates that the email service shall attempt a bearer

    51 migration when a preferred carrier becomes available (upgrade), or when the

    52 carrier over which an existing connection has been made becomes unavailable

    53 (downgrade). </p> <p>The following is the default migration: </p> <ul>

    54 <li id="GUID-C185CE8D-4825-5288-9A86-E8AA2DED9FEF"><p> <b>upgrade:</b> allow

    55 any outstanding operation to complete, then attempt to switch to the new bearer. </p> </li>

    56 <li id="GUID-4F8B5FF0-147D-5CC2-A10F-5717ACA1409D"><p> <b>downgrade:</b> immediately

    57 close connected sockets, then attempt to switch to the new bearer. Any operations

    58 in progress at the time of the migration is resumed when connection has been

    59 made through the new carrier. </p> </li>

    60 </ul> <p>The default policy is plug-in replaceable, allowing migration notices

    61 to be ignored or modifying the handling of outstanding operations, which may

    62 be suspended and resumed following the migration. </p> <p>Note that Bearer

    63 Mobility can only be performed when the account connection preferences specify

    64 a SNAP, see <xref href="GUID-AD6587AD-A5B2-5369-9217-D752A37490C4.dita">Bearer

    65 Mobility</xref>. </p> </entry>

    66 <entry><p>Supported </p> </entry>

    67 <entry><p>Supported </p> </entry>

    68 <entry><p>Supported </p> </entry>

    69 </row>

    70 <row>

    71 <entry><p>Body encoding </p> </entry>

    72 <entry><p>Specifies the encoding used when sending an email message. </p> </entry>

    73 <entry><p>Supported </p> </entry>

    74 <entry><p>-</p> </entry>

    75 <entry><p>-</p> </entry>

    76 </row>

    77 <row>

    78 <entry><p>Default character set </p> </entry>

    79 <entry><p>Sets the character set of the out-bound email message. </p> </entry>

    80 <entry><p>Supported </p> </entry>

    81 <entry><p>- </p> </entry>

    82 <entry><p>- </p> </entry>

    83 </row>

    84 <row>

    85 <entry><p>Disable IMAP Folder Tree Synchronisation </p> </entry>

    86 <entry><p>Specifies whether the remote folder tree shall be synchronised as

    87 part of account synchronisation operations. The default setting is <codeph>EFalse</codeph>,

    88 which means that the folder tree synchronisation shall be performed. </p> </entry>

    89 <entry><p>- </p> </entry>

    90 <entry><p>- </p> </entry>

    91 <entry><p>Supported </p> </entry>

    92 </row>

    93 <row>

    94 <entry><p>Disconnected user mode </p> </entry>

    95 <entry><p>If enabled, allows the messaging client to fetch, move, and delete

    96 mailbox messages while not connected by queuing offline operations. </p> <p>The

    97 queued offline operations are automatically processed the next time the messaging

    98 client connects, just before login and Inbox synchronisation. For the IMAP4

    99 protocol, messages are not marked as invisible when disconnected if this setting

   100 is enabled. </p> </entry>

   101 <entry><p>- </p> </entry>

   102 <entry><p>Supported </p> </entry>

   103 <entry><p>Supported </p> </entry>

   104 </row>

   105 <row>

   106 <entry><p>Email address </p> </entry>

   107 <entry><p>The email address of the subscriber. </p> </entry>

   108 <entry><p>Supported </p> </entry>

   109 <entry><p>- </p> </entry>

   110 <entry><p>- </p> </entry>

   111 </row>

   112 <row>

   113 <entry><p>Email alias </p> </entry>

   114 <entry><p>The name of the subscriber as they want it to appear in the header

   115 of the email messages they send. </p> </entry>

   116 <entry><p>Supported </p> </entry>

   117 <entry><p>- </p> </entry>

   118 <entry><p>- </p> </entry>

   119 </row>

   120 <row>

   121 <entry><p>Folder path </p> </entry>

   122 <entry><p>The path to the IMAP4 mailbox on the server if the subscriber’s

   123 primary mailbox is not the Inbox. </p> <p> <b>Note:</b> Most messaging clients

   124 need not have to set this. Refer to RFC 3501, Section 5.1 Mailbox naming for

   125 more information. </p> </entry>

   126 <entry><p>- </p> </entry>

   127 <entry><p>- </p> </entry>

   128 <entry><p>Supported </p> </entry>

   129 </row>

   130 <row>

   131 <entry><p>Get Mail Options </p> </entry>

   132 <entry><p>Specifies how new messages must be fetched when synchronising. The

   133 available options are: </p> <ul>

   134 <li id="GUID-F28822E7-6AC0-515E-B53F-C7C65CDF665B"><p>Headers only </p> </li>

   135 <li id="GUID-7DBDC59C-9E5D-5965-B133-A44A211AD6F1"><p>Body text only (applicable

   136 to IMAP4 only) </p> </li>

   137 <li id="GUID-B8820C8C-AA0D-5A86-A5E8-837F22887BB9"><p>Attachments only (applicable

   138 to IMAP4 only) </p> </li>

   139 <li id="GUID-57F98841-57F7-5180-8D6A-C00934875F94"><p>Entire message </p> </li>

   140 </ul> </entry>

   141 <entry><p>- </p> </entry>

   142 <entry><p>Supported </p> </entry>

   143 <entry><p>Supported </p> </entry>

   144 </row>

   145 <row>

   146 <entry><p>IMAP IDLE </p> </entry>

   147 <entry><p>Specifies whether the IMAP IDLE command must be used as defined

   148 in RFC2177. </p> <p>The default setting is <codeph>ETrue</codeph> which means

   149 that the IMAP IDLE command is used, if the server supports it. </p> </entry>

   150 <entry><p>- </p> </entry>

   151 <entry><p>- </p> </entry>

   152 <entry><p>Supported </p> </entry>

   153 </row>

   154 <row>

   155 <entry><p>IMAP IDLE timeout </p> </entry>

   156 <entry><p>Specifies the IMAP IDLE timeout in seconds. The default setting

   157 is 1740 seconds (29 minutes). </p> </entry>

   158 <entry><p>- </p> </entry>

   159 <entry><p>- </p> </entry>

   160 <entry><p>Supported </p> </entry>

   161 </row>

   162 <row>

   163 <entry><p>IMAP Synchronisation Download Rules </p> </entry>

   164 <entry><p>Specifies which message parts to automatically download when synchronising

   165 the contents of an IMAP email account. See <xref href="GUID-75B1B1DF-4EC2-59BC-8BE0-A8AD681798C5.dita">IMAP

   166 Account Settings</xref> for more information. </p> </entry>

   167 <entry><p>- </p> </entry>

   168 <entry><p>- </p> </entry>

   169 <entry><p>Supported </p> </entry>

   170 </row>

   171 <row>

   172 <entry><p>IMAP Transport Buffer Sizes </p> </entry>

   173 <entry><p>Allows a client to configure transport buffer sizes of IMAP accounts

   174 according to bearer type for fetching of large message parts. </p> <p>It is

   175 possible to specify: </p> <ul>

   176 <li id="GUID-8083E140-B97C-50FE-8582-92D5BAE8A390"><p>maximum fetch size (default

   177 is 20480 octets) </p> </li>

   178 <li id="GUID-170DDB00-B16E-5BCC-A4EC-98E6201C88F9"><p>maximum outstanding

   179 fetch requests (default is 2 outstanding requests) </p> </li>

   180 </ul> <p>Note that this is a global setting that affects all IMAP accounts. </p> </entry>

   181 <entry><p>- </p> </entry>

   182 <entry><p>- </p> </entry>

   183 <entry><p>Supported </p> </entry>

   184 </row>

   185 <row>

   186 <entry><p>Inbox refresh rate </p> </entry>

   187 <entry><p>Specifies whether to periodically poll the email server for new

   188 messages, and if so, how frequently. </p> </entry>

   189 <entry><p>- </p> </entry>

   190 <entry><p>- </p> </entry>

   191 <entry><p>Supported </p> </entry>

   192 </row>

   193 <row>

   194 <entry><p>Inbox synchronisation limit </p> </entry>

   195 <entry><p>Sets the limit (if any) for the number message headers stored in

   196 the Inbox of the local device when synchronising. </p> <p>Older message headers

   197 are deleted to make space for newer message headers. Messages that have had

   198 body text or attachments downloaded will not be deleted and are not considered

   199 part of the Inbox count limit. Can also be used to disable Inbox synchronisation

   200 after a connection. </p> </entry>

   201 <entry><p>- </p> </entry>

   202 <entry><p>Supported </p> </entry>

   203 <entry><p>Supported </p> </entry>

   204 </row>

   205 <row>

   206 <entry><p>Include signature </p> </entry>

   207 <entry><p>If the subscriber has a signature, it is append the body text of

   208 out-bound email messages. </p> </entry>

   209 <entry><p>Supported </p> </entry>

   210 <entry><p>- </p> </entry>

   211 <entry><p>- </p> </entry>

   212 </row>

   213 <row>

   214 <entry><p>Include VCard </p> </entry>

   215 <entry><p>If the subscriber has a VCard, the VCard is attached to out-bound

   216 email messages. </p> </entry>

   217 <entry><p>Supported </p> </entry>

   218 <entry><p>- </p> </entry>

   219 <entry><p>- </p> </entry>

   220 </row>

   221 <row>

   222 <entry><p>Login name </p> </entry>

   223 <entry><p>The subscriber’s login name. </p> </entry>

   224 <entry><p>Supported </p> </entry>

   225 <entry><p>Supported </p> </entry>

   226 <entry><p>Supported </p> </entry>

   227 </row>

   228 <row>

   229 <entry><p>Login password </p> </entry>

   230 <entry><p>The subscriber’s login password. </p> </entry>

   231 <entry><p>Supported </p> </entry>

   232 <entry><p>Supported </p> </entry>

   233 <entry><p>Supported </p> </entry>

   234 </row>

   235 <row>

   236 <entry><p>Mailbox synchronisation limit </p> </entry>

   237 <entry><p>Sets the limit (if any) for the number of messages headers stored

   238 in non-Inbox folders on the local device when synchronising. </p> <p>Older

   239 message headers are deleted to make space for newer message headers. Messages

   240 that have had body text or attachments downloaded will not be deleted and

   241 are not considered part of the non-Inbox count limit. Can also be used to

   242 disable folder synchronisation. </p> </entry>

   243 <entry><p>- </p> </entry>

   244 <entry><p>- </p> </entry>

   245 <entry><p>Supported </p> </entry>

   246 </row>

   247 <row>

   248 <entry><p>Maximum email size </p> </entry>

   249 <entry><p>Allows the messaging client to specify a maximum size (if any) in

   250 KB that are downloaded. If the email is larger than the maximum size, none

   251 of its body text or attachments are downloaded. </p> </entry>

   252 <entry><p>- </p> </entry>

   253 <entry><p>Supported </p> </entry>

   254 <entry><p>Supported </p> </entry>

   255 </row>

   256 <row>

   257 <entry><p>Path separator </p> </entry>

   258 <entry><p>Allows the messaging client to specify the character used to separate

   259 hierarchical mailbox names on the IMAP4 server. Refer to RFC 3501 section

   260 5.1.1 for more information. </p> </entry>

   261 <entry><p>- </p> </entry>

   262 <entry><p>- </p> </entry>

   263 <entry><p>Supported </p> </entry>

   264 </row>

   265 <row>

   266 <entry><p>Reply-to address </p> </entry>

   267 <entry><p>The email address that the subscriber wishes any replies to their

   268 email messages to be sent to. However, it is possible to override this on

   269 a per message basis when composing the message. </p> </entry>

   270 <entry><p>Supported </p> </entry>

   271 <entry><p>- </p> </entry>

   272 <entry><p>- </p> </entry>

   273 </row>

   274 <row>

   275 <entry><p>Request receipt </p> </entry>

   276 <entry><p>If enabled, sent messages indicates to the receiving messaging client

   277 that they want a receipt notification message (for example, a read notification)

   278 sent back to the email address specified in the receipt address setting. It

   279 is entirely up to the receiving messaging client whether it complies with

   280 this request. </p> </entry>

   281 <entry><p>Supported </p> </entry>

   282 <entry><p>- </p> </entry>

   283 <entry><p>- </p> </entry>

   284 </row>

   285 <row>

   286 <entry><p>Receipt address </p> </entry>

   287 <entry><p>The email address that message receipt notifications is sent to

   288 if request receipts has been enabled. </p> </entry>

   289 <entry><p>Supported </p> </entry>

   290 <entry><p>- </p> </entry>

   291 <entry><p>- </p> </entry>

   292 </row>

   293 <row>

   294 <entry><p>Secure sockets </p> </entry>

   295 <entry><p>If enabled, a secure TLS connection is negotiated over an un-secure

   296 socket on the specified server port according to RFC 2595 and 3207 specifications. </p> </entry>

   297 <entry><p>Supported </p> </entry>

   298 <entry><p>Supported </p> </entry>

   299 <entry><p>Supported </p> </entry>

   300 </row>

   301 <row>

   302 <entry><p>Send copy to self </p> </entry>

   303 <entry><p>Specifies how copies of messages must be send to the sender. The

   304 available options are: </p> <ul>

   305 <li id="GUID-28276A85-A423-5C85-B8DC-E5590877496D"><p>Do not send a copy </p> </li>

   306 <li id="GUID-E56F00B8-49C4-51F0-8223-06C0F2AB8D50"><p>Send a copy by including

   307 the sender’s email address in the To recipients of the email to be sent </p> </li>

   308 <li id="GUID-CA713DF3-97F0-54F1-84F7-F608FF1F4F1A"><p>Send a copy by including

   309 the sender’s email address in the Cc recipients of the email to be sent </p> </li>

   310 <li id="GUID-E28B8830-E87F-5351-9581-4C1BB2B26A9D"><p>Send a copy by including

   311 the sender’s email address in the Bcc recipients of the email to be sent </p> </li>

   312 </ul> </entry>

   313 <entry><p>Supported </p> </entry>

   314 <entry><p>- </p> </entry>

   315 <entry><p>- </p> </entry>

   316 </row>

   317 <row>

   318 <entry><p>Send message options </p> </entry>

   319 <entry><p>Specifies how the message is sent. The available options are: </p> <ul>

   320 <li id="GUID-0DFFAD00-E8D0-5A7A-BAE7-9B288468EBDA"><p>Send messages next time

   321 the subscriber connects to their mailbox </p> </li>

   322 <li id="GUID-1A1F2366-F8F4-5563-9963-FCDC070A94FA"><p>Send messages immediately </p> </li>

   323 <li id="GUID-8EDFB259-896C-5709-9BC4-6B432F352F3A"><p>Send messages when messaging

   324 client requests </p> </li>

   325 </ul> </entry>

   326 <entry><p>Supported </p> </entry>

   327 <entry><p>- </p> </entry>

   328 <entry><p>- </p> </entry>

   329 </row>

   330 <row>

   331 <entry><p>Server address </p> </entry>

   332 <entry><p>The hostname or IP address of the SMTP, IMAP4, or POP3 server. </p> </entry>

   333 <entry><p>Supported </p> </entry>

   334 <entry><p>Supported </p> </entry>

   335 <entry><p>Supported </p> </entry>

   336 </row>

   337 <row>

   338 <entry><p>Server port </p> </entry>

   339 <entry><p>The TCP port of the SMTP, IMAP4, or POP3 server. </p> </entry>

   340 <entry><p>Supported </p> </entry>

   341 <entry><p>Supported </p> </entry>

   342 <entry><p>Supported </p> </entry>

   343 </row>

   344 <row>

   345 <entry><p>Size Limiting of emails </p> </entry>

   346 <entry><p>If body text size limit is specified, then downloads the body text

   347 of a email partially and downloads the attachments only if their size is less

   348 than or equal to the specified attachment size limit. </p> </entry>

   349 <entry><p>- </p> </entry>

   350 <entry><p>- </p> </entry>

   351 <entry><p>Supported </p> </entry>

   352 </row>

   353 <row>

   354 <entry><p>SMTP Account Override </p> </entry>

   355 <entry><p>Allows the client to associate “SMTP Mobility Accounts” with an

   356 SMTP account, to use when connected through specified internet access points. </p> <p>When

   357 attempting to send an email using SMTP, the IAP that the connection to the

   358 SMTP server is using is checked. If a SMTP mobility account is specified for

   359 that IAP, then the settings for that SMTP mobility account is used to send

   360 the email. If no SMTP mobility account is specified for that IAP, then the

   361 settings from the SMTP account is used. </p> <p>Only settings relating to

   362 the sending of emails are overridden – emails are constructed according to

   363 the over-ridden SMTP account settings. </p> </entry>

   364 <entry><p>Supported </p> </entry>

   365 <entry><p>- </p> </entry>

   366 <entry><p>- </p> </entry>

   367 </row>

   368 <row>

   369 <entry><p>SSL wrapper </p> </entry>

   370 <entry><p>If enabled, a secure TLS connection is established on the specified

   371 server port. </p> </entry>

   372 <entry><p>Supported </p> </entry>

   373 <entry><p>Supported </p> </entry>

   374 <entry><p>Supported </p> </entry>

   375 </row>

   376 <row>

   377 <entry><p>TLS/SSL Domain </p> </entry>

   378 <entry><p>Specifies the domain to use for certificate validation when establishing

   379 a secure TLS connection. </p> </entry>

   380 <entry><p>Supported </p> </entry>

   381 <entry><p>Supported </p> </entry>

   382 <entry><p>Supported </p> </entry>

   383 </row>

   384 <row>

   385 <entry><p>Update flags </p> </entry>

   386 <entry><p>If enabled, the seen flag is updated on the IMAP4 mailbox for messages

   387 that have been read. This indicates to email applications on other devices

   388 accessing the same mailbox that the message has already been read. </p> <p>Likewise,

   389 if an email application on another device marks messages as read on the server,

   390 then the messaging client indicates that the message has already been read. </p> </entry>

   391 <entry><p>- </p> </entry>

   392 <entry><p>- </p> </entry>

   393 <entry><p>Supported </p> </entry>

   394 </row>

   395 <row>

   396 <entry><p>Use APOP authentication </p> </entry>

   397 <entry><p>Specifies whether to use APOP authentication to login to the POP3

   398 mailbox. </p> </entry>

   399 <entry><p>- </p> </entry>

   400 <entry><p>Supported </p> </entry>

   401 <entry><p>- </p> </entry>

   402 </row>

   403 <row>

   404 <entry><p>Use SMTP authentication </p> </entry>

   405 <entry><p>Specifies whether to use SMTP AUTHentication to login to the SMTP

   406 server. </p> </entry>

   407 <entry><p>Supported </p> </entry>

   408 <entry><p>- </p> </entry>

   409 <entry><p>- </p> </entry>

   410 </row>

   411 </tbody>

   412 </tgroup>

   413 </table> <p><b>SNAP Preferences</b> </p> <p>A allow Service Network Access

   414 Point (SNAP) is a collection of access points (AP) that are used especially

   415 for bearer mobility to identify a service network with a service to be accessed

   416 on the network. That is, it is a collection of IAP that specify the same network

   417 and the same service on that network. SNAP uses the underlying Networking

   418 framework to select the best AP defined in the SNAP preference list to use

   419 to establish the connection. </p> <p>The <xref href="GUID-9CAB9BE5-7233-3A01-A906-756177CF4460.dita"><apiname>CImIAPPreferences</apiname></xref> class

   420 encapsulates preferences about IAPs for an email service. This class allows

   421 a single SNAP to be specified as an alternative to a list of preferred IAPs.

   422 A SNAP defines its own list of IAPs in preference order, and is reusable by

   423 multiple clients that requires network connections. </p> <p>To allow SNAP

   424 IDs to be defined, retrieved, and deleted when a network connection is made,

   425 the following functions are provided by the <xref href="GUID-9CAB9BE5-7233-3A01-A906-756177CF4460.dita"><apiname>CImIAPPreferences</apiname></xref> class: </p> <ul>

   426 <li id="GUID-89871675-D443-5343-8D3E-8E5C1A86AC99"><p> <xref href="GUID-F4D57A3E-BC3E-3DEA-B969-B656C5FD3B68.dita"><apiname>SNAPDefined()</apiname></xref>  </p> </li>

   427 <li id="GUID-2F171496-91D5-530E-9809-10FBFDCA4A38"><p> <xref href="GUID-C0AF460A-8DC8-3115-9AEC-A63FF4DB2067.dita"><apiname>SNAPPreference()</apiname></xref>  </p> </li>

   428 <li id="GUID-AD0FC483-1646-5496-B2AD-6B643D1DBFE8"><p> <xref href="GUID-EBF66578-1CF1-3737-B78A-3A8D06A9CD16.dita"><apiname>SetSNAPL()</apiname></xref>  </p> </li>

   429 <li id="GUID-05777751-5244-5778-824C-E3D8834D4CA1"><p> <xref href="GUID-B15A0120-1D4D-33B9-AC8F-2F94AF7B1EFD.dita"><apiname>RemoveSNAPL()</apiname></xref>  </p> </li>

   430 </ul> <p><b>SMTP account override settings</b> </p> <p>The SMTP account override

   431 functionality allows the messaging client to associate <b>SMTP mobility accounts</b> with

   432 an SMTP account to use when connected through the specified Internet access

   433 points. </p> <p>A SMTP mobility account allows different send settings to

   434 be used by SMTP accounts depending on what access point is being used by the

   435 SMTP connection. When a connection is made for a SMTP account, its associated

   436 list of SMTP mobility accounts is examined to check, if any access point is

   437 linked to the bearer type that is used for the connection. If any access point

   438 is found, then the settings for the SMTP mobility account are used for the

   439 connection and subsequent email sending in preference to the settings for

   440 the SMTP account. </p> <p>To override the SMTP mobility account settings,

   441 the following class are provided. These classes describe the settings that

   442 are overridden when connecting to the mobility account through an IAP associated

   443 with the mobility account. </p> <ul>

   444 <li id="GUID-37CE33BF-27F2-5C61-93D4-E339F9AE2F03"><p> <xref href="GUID-72BF08A4-2724-3F42-A685-F97F68133B69.dita"><apiname>TSmtpMobilityAccount</apiname></xref>  </p> </li>

   445 <li id="GUID-54F87DB8-07F3-511C-A986-EFDEFA41BA6E"><p> <xref href="GUID-AA86050B-00E4-3EEC-9E41-32C1A4493D30.dita"><apiname>CImSmtpMobilitySettings</apiname></xref>  </p> </li>

   446 </ul> <p><b>TLS or SSL domain name for certificate validation</b> </p> <p>To

   447 enhance certification security checks, the <xref href="GUID-3EDD3DFA-AE8A-3941-960A-8BD2733E74C3.dita"><apiname>CImBaseEmailSettings</apiname></xref> class

   448 is enhanced to allow the Transport Layer Security (TLS) or Secure Sockets

   449 Layer (SSL) server domain name to be specified when creating email accounts.

   450 The following functions are added to the <xref href="GUID-3EDD3DFA-AE8A-3941-960A-8BD2733E74C3.dita"><apiname>CImBaseEmailSettings</apiname></xref> class: </p> <ul>

   451 <li id="GUID-120DA036-4153-552C-B712-8B593753EA8C"><p> <xref href="GUID-86633B7D-5AB8-3BBD-BB54-4697211AC86E.dita"><apiname>SetTlsSslDomainL()</apiname></xref>  </p> </li>

   452 <li id="GUID-DA875B46-D163-5397-A0D9-36D8732E872E"><p> <xref href="GUID-46A0BD1F-833E-3D55-B2C3-329770808AD2.dita"><apiname>TlsSslDomain()</apiname></xref>  </p> </li>

   453 </ul> </section>

   454 <section><title>IAP preferences setting</title> <table id="GUID-CDE2AF8B-FCE2-5DA1-83FD-9D09A131CE30">

   455 <tgroup cols="2"><colspec colname="col0"/><colspec colname="col1"/>

   456 <thead>

   457 <row>

   458 <entry>Tittle </entry>

   459 <entry>Description</entry>

   460 </row>

   461 </thead>

   462 <tbody>

   463 <row>

   464 <entry><p>IAP Number </p> </entry>

   465 <entry><p>The IAP identifier as specified in the CommDb record for the IAP. </p> </entry>

   466 </row>

   467 <row>

   468 <entry><p>Dialogue Preference </p> </entry>

   469 <entry><p>The dialog preference determines whether a user must be prompted

   470 with a dialog when connecting to the IAP. </p> <p>The available options are: </p> <ul>

   471 <li id="GUID-78F25ED9-DB36-5854-892B-DE27F0BC8CA3"><p>Prompt </p> </li>

   472 <li id="GUID-DDF46C83-0F5F-52F1-9D50-5EF315D156B7"><p>Warn </p> </li>

   473 <li id="GUID-967332AA-71AE-58D3-A4BC-69BEE8057843"><p>Do not prompt </p> </li>

   474 <li id="GUID-CBC5B2FB-221B-5B00-8D78-8281635827B9"><p>Prompt if wrong mode </p> </li>

   475 </ul> </entry>

   476 </row>

   477 </tbody>

   478 </tgroup>

   479 </table> </section>

   480 <example><title>Email settings example</title> <ul>

   481 <li id="GUID-78EAF21A-8941-583E-861F-BADE2394A3B4"><p><xref href="GUID-D73AD200-BE4D-50BF-BCF9-14627DE530B7.dita">IMAP4

   482 Example: An Email manager using IMAP4 and SMTP</xref>  </p> </li>

   483 <li id="GUID-742F921B-CBD7-538F-8EB2-D823AC45E3E4"><p><xref href="GUID-BB35DBCC-FE56-547F-BADA-9EF854691ADC.dita">POP3

   484 Example: An Email manager using POP3 and SMTP</xref>  </p> </li>

   485 </ul> </example>

   486 </refbody><related-links>

   487 <link href="GUID-AD6587AD-A5B2-5369-9217-D752A37490C4.dita"><linktext>Bearer  

   488               Mobility</linktext></link>

   489 <link href="GUID-179099DA-1CD9-5912-B41B-363C132C7A86.dita"><linktext>Processing

   490 Email in Chunks</linktext></link>

   491 <link href="GUID-4384066E-158A-5F63-A823-7793DAE680BF.dita"><linktext>Email</linktext>

   492 </link>

   493 </related-links></reference>