/mcpthe message to chris.jones@example.com, records audio for the message, and selects the Send button. The voice message is routed to Unity Connection for delivery because ViewMail is configured to use Unity Connection IMAP accounts to send the messages. When Unity Connection receives the voice message, it searches the list of SMTP proxy addresses for robin.smith@example.com (the sender) and chris.jones@example.com (the recipient). Unity Connection delivers the message as a voice message from Robin Smith to Chris Jones because these addresses are defined as SMTP proxy addresses for the user profiles of Robin Smith and Chris Jones respectively. When Chris opens Outlook, the email message from Robin shows up as a new message in the Microsoft Exchange Inbox. The voice message from Robin, on the other hand, shows up as a new message in the Inbox of the Unity Connection account that Chris accesses using IMAP. If Chris replies to either message, the Outlook client automatically route the reply using the account in which Chris received the original message. Important Points for Deploying Integrated Messaging Following are the considerations when deploying IMAP clients to send and receive Unity Connection messages: • Use a firewall to protect the SMTP port from unauthorized access. The SMTP port and domain are listed on the System Settings > SMTP Configuration > Server page in Cisco Unity Connection Administration. • Configure Transport Layer Security for IMAP client connections in order to protect user passwords. • Configure the corporate email address of each user as an SMTP proxy address for the user. When setting up theUnity Connection IMAP account on user workstation, use the corporate email address of the user instead of the Unity Connection specific email address. In this way, users are insulated from changes to the Unity Connection-specific addresses if the SMTP domain is changed. • Create a separate Outlook address book for ViewMail users that is limited to the objects in the user search space if you are using search spaces to limit the objects that users can reach and do not want users to receive NDRs for unreachable objects. Task List for Configuring IMAP Access Follow the given steps to configure IMAP access to Unity Connection messages: 1. (optional) Do the following tasks if you plan to configure Unity Connection to relay messages for users to another SMTP server: Configure the SMTP smart host to accept messages from Unity Connection server. For more information, see the documentation for the SMTP server you are using. Configure Unity Connection to relay messages to smart host. For more information, see the Configuring Unity Connection to Relay Messages to a Smart Host section. Review the settings that control whether private or secure messages can be relayed. For more information, see the Configuring Message Relay Settings section. 2. Configure message actions for users or user templates. For more information, see the Configuring Message Actions for Users or User Templates section. 3. Configure SMTP proxy addresses for users who send or receive messages from IMAP clients. For more information, see the Configuring SMTP Proxy Addresses for Users or User Templates section. System Administration Guide 141 Messaging Important Points for Deploying Integrated Messaging