This document provides a sample configuration on how to use IMAP4 to
access voice messages in Cisco Unity when you use Microsoft Exchange
Note: Certain Exchange Server 2007 managed code services do not start after
you install this update Rollup. This is true if the services cannot access this
Microsoft Web site,
or it takes too long to do it.
Refer to article number 944752,
managed code services do not start after you install an update rollup for
, in order to view the article in the Microsoft Knowledge
Base for more information about how to resolve or work around this
Ensure that you meet these requirements before you attempt this
This document is not restricted to specific software and hardware
Refer to the
Technical Tips Conventions for more information on document
In this section, you are presented with the information to configure
the features described in this document.
Note: Use the
Command Lookup Tool
(registered customers only)
to obtain more information on
the commands used in this section.
Complete these steps:
The installation and enabling of
IMAP4 are a part of the Client Access Server (CAS) role of Exchange
2007, which means that no further installation is required to use it; it simply
requires enabling. In order to enable it, first set start-up mode of Microsoft
Exchange IMAP4 service to Automatic and then start the
service. See this figure for more information.
Change the server IMAP4 configuration to use TNEF
for MessageRetrievalMimeFormat. It can be done
with the use of the Exchange Management Console.
Choose Server Configuration > Client Access > IMAP4
> Properties and click Retrieval Settings. Choose
TNEF for Message MIME format. See this figure
for more information.
Restart the IMAP service. If you change the IMAP
settings, you need to restart the IMAP service on Exchange in order to make it
Use the Exchange Management Console in order to
create a new mailbox and ensure that the mailbox has the IMAP4
protocol enabled for use. It can be done with the Exchange
Choose Recipient Configuration > Mailbox, and
choose the new mailbox you created on Exchange 2007 server. Then choose
Properties and in the Mailbox Properties window, choose the
Mailbox Features tab and see if IMAP4 is
Enabled. See the figure for more
Use the Exchange Management Console in order to change the mailbox
IMAP4 Properties to use TNEF for
ImapMessagesRetrievalMimeFormat and set
ImapUseProtocolDefaults to false.
By default, ImapMessagesRetrievalMimeFormat is set
to Best body format and
ImapUseProtocolDefaults is set to true.
Choose Recipient Configuration > Mailbox, and choose the
specific mailbox you want on Exchange 2007 server. Then choose
Properties, click the Mailbox Features tab,
choose IMAP4, and choose Properties. In this
window, you can see that Use Protocol default is
Uncheck the checkbox for Use protocol default and
change Customized setting which takes precedence over the protocol
default settings to TNEF. After you make these
changes, click OK in order to return mailbox properties
dialog, click Apply in order to apply the changes, and then
click OK in order to exit the mailbox properties
This task can be done with the Exchange Management Shell. See this
Set-CasMailbox –identity T2Ex2007@cisco.com -ImapMessagesRetrievalMimeFormat Tnef -ImapUseProtocolDefaults $false
The steps to setup an Outlook IMAP profile for Exchange 2007 are very
similar to the ones for Exchange. On the Microsoft Outlook desktop client, you
need to configure an IMAP4 connection to the Cisco Unity message-store server
where the message-store account of the user resides. For each Outlook client,
complete these steps:
Open Outlook and choose Tools > E-mail
Choose Add new e-mail account, and then click
Choose IMAP and then click Next.
The E-mail Accounts dialog appear, and you need to fill out the
requested information. This information includes the User,
Server, and Logon Information.
Choose More Settings in order to change the
display name for the mail account. In the General tab, under
Mail Account, type the name by which you want to refer to this
Switch to the Outgoing Server tab and choose
My outgoing server (SMTP) requires authentication. You can
choose Use same settings as my incoming mail server.
Click OK in order to return to the E-mail Accounts
dialog. Then click Next and then Finish in
order to complete the settings, as shown in this figure.
After Rollup 2 is installed, the version shown in Exchange Management
Console is not changed. But, you see a new registry key
2007\SP2\KB948016 , and it has a registry with value name
PackageName and value data Update
Rollup 2 for Exchange Server 2007 Service Pack 1 (KB948016).
In Exchange 2007 the default settings are a little more secure than
in previous versions. By default Exchange 2007 requires SSL/TLS secured
connections (Secure logon), which means to ensure the client connects to the
secured port. See this figure, choose Server Configuration > Client
Access> IMAP4 > Properties, and click
Authentication. No change is needed here unless you want to
use a different logon method.
When you use the SSL/TLS connection, it is important to make sure
your client computer trusts the certificate path used for traffic encryption.
Otherwise a warning appears when you open Outlook as shown in this figure.
If you click Yes, the warning window goes away and
Outlook continues without any problem. But Outlook asks you the same question
again the next time you open Outlook.
If you want to use a different logon method, then Outlook E-mail
Accounts settings are required to change accordingly.
Exchange 2007 has three kinds of logon methods:
You have to configure the client side setting accorddingly. For
example, if server-side settings is secure
logon, then the client-side settings possibly need to be set up
If you use Outlook 2003, you need to have at least the SP3 installed
in order to use the SMTP server for outgoing emails. Without the SP3 installed,
you can receive this error message:
'Sending' reported error (0x800CCC7D) :
'Your outgoing (SMTP) server does not support SSL-secured connections. If SSL-secured connections have worked in the past, contact your server administrator or Internet service provider (ISP).'
Microsoft Office Service Pack 3 is available at:
There is currently no verification procedure available for this
There is currently no specific troubleshooting information available
for this configuration.