/mcp• Future delivery: A user can mark a message for future delivery to a recipient using the touchtone conversation or the voice recognition conversation. Unity Connection waits to send the message on the day and time that the user specifies. Once future delivery is set on the message, the user can cancel the future delivery as long as the user has not yet selected the option to send the message. An administrator can cancel the pending messages set for future delivery using the delete cuc futuredelivery CLI command. The unidentified callers or users who are not signed in to mailboxes, can mark a message urgent, private, or secure depending on the user or user template settings. If any other Unity Connection user calls a user extension and the user does not answer. Unity Connection identifies the caller as unidentified callers. The message delivery and sensitivity settings can be managed in either of the following ways: • In Cisco Unity Connection Administration> Users> Users> select a user> Edit> Message Settings> select the desirable action under the Message Urgency, Message Security, and Message Sensitivity fields. • In Cisco Unity Connection Administration> Templates> User Template> select a user template> Edit> Message Settings> select the desirable action under the Message Urgency, Message Security, and Message Sensitivity fields. Message Delivery Issues Following are the information pertaining to message delivery issues: • If a message failed to be delivered to a recipient that the caller intended to reach, the message is sent to the Undeliverable distribution list. Unity Connection sends a non delivery receipt (NDR) to the sender if the sender is configured to accept NDRs. NDRs are not send if the sender is an unidentified caller or the mailstore of the recipient is offline. Note If the original message is malformed, the message is not sent to Undeliverable distribution list. The message is instead sent to the MTA bad mail folder (UmssMtaBadMail). • If the Unity Connection components involved in message delivery are unavailable, the recorded messages are queued and delivered when the components are available. For example, if a mailbox store is disabled, messages are held in queue, and delivered once the mailbox store is enabled again. For single inbox configuration, if network or other conditions are slow and prevent attempts to retrieve messages from Exchange, Unity Connection announces to users that email is unavailable. The time period that Unity Connection waits for a response from Exchange is four seconds by default. This can be configured in Cisco Unity Connection Administration> System Settings> Advanced> Unified Messaging Services> the TTS and Calendars: Time to Wait for a Response (in seconds) field. The messages are held in queue for delivery but they are not synchronized with Exchange mailboxes. The synchronization between Unity Connection and Exchange resumes once Exchange is available. • If a call is disconnected while users are in the process of sending, replying, or forwarding messages, the messages are handled in the way depending on user configuration. This configuration is specified in either of the following ways: System Administration Guide 132 Messaging Message Delivery Issues