Showing results for 
Search instead for 
Did you mean: 
Koz Ent

CUC 8.6(1a) - Single Inbox - Seeing NDR Failures to/from root@UCSERVER in Postini

CUC 8.6(1a) - Single Inbox - Seeing NDR Failures to/from root@UCSERVER in Postini

I need some help with something we are seeing after deploying Unity Connection 8.6(1a) with Single Inbox configured. (We are not using the VMO plugin)

Everything client facing is working great, voice messages and single inbox are being received properly. What we continue to see is Postini continuing to send out reports for failed message being sent from root@UCSERVER1 to root@UCSERVER1 and postmaster@UCSERVER1. We are also seeing the message being sent from root@UCSERVER2 to root@UCSERVER2 and postmaster@UCSERVER2 (The second server in the cluster). They are receiving failures as UCSERVER1 and UCSERVER2 are not a valid email address or domain, so no email server including Postini would route that.

I have pasted the failure below for reference. These appear to be some sort of job that periodically kicks off, sending emails to that address. I spent the last 2 days trying to research this, working with Cisco TAC (who pointed me towards the SMTP configuration for VMO, which we are not using), trying to find solution but nothing yet. The SMTP domain and configurations have verified, the relay connectors on the SMTP smart host are setup. Everything else is working smooth except we are receiving alerts from Postini on these 4 different failures.

What is this automated job, why is it sending out email messages, where is it configured, and what does it do? I could not find any details regarding this specifically just from the data I have. Cisco TAC also didn’t have details.

Anyone familiar with this? Has anyone ran into this before? Is there a fix?

Any help would be greatly appreciated. Thank you!

Referenced failure e-mail:


Received: from ([##.##.##.##]) (using TLSv1) by ([##.##.##.##]) with SMTP

        ID xxxxxxxxx/xxxxxxxxxxxxxxx/; Tue, 29 Nov 2011 01:20:04 PST

MIME-Version: 1.0

From: <>

To: <root@UCSERVER1>

Date: Tue, 29 Nov 2011 03:20:03 -0600

Content-Type: multipart/report; report-type=delivery-status;


Content-Language: en-US

Message-ID: <>

In-Reply-To: <>

References: <>

Subject: Undeliverable: Cron <root@UCSERVER1>   /etc/rc.d/init.d/fiostats show


Date: Tue, 29 Nov 2011 03:20:03 -0600

From: <>

To: <root@UCSERVER1>

Subject: Undeliverable: Cron <root@UCSERVER1> /etc/rc.d/init.d/fiostats show

Delivery has failed to these recipients or groups:


A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.

The following organization rejected your message: Postini.

Diagnostic information for administrators:

Generating server:


Postini #550 Host not found for domain:UCSERVER1 - psmtp ##

Original message headers:

Received: from UCSERVER1 (##.##.##.##) by

(##.##.##.###) with Microsoft SMTP Server id ##.##.##.##; Tue, 29 Nov 2011

03:20:01 -0600

Received: by UCSERVER1 (sSMTP sendmail emulation); Tue, 29 Nov 2011 03:20:01


From: root <root@UCSERVER1>

Date: Tue, 29 Nov 2011 03:20:01 -0600

To: root

Subject: Cron <root@UCSERVER1> /etc/rc.d/init.d/fiostats show

Content-Type: text/plain; charset="UTF-8"

Auto-Submitted: auto-generated

X-Cron-Env: <SHELL=/bin/sh>

X-Cron-Env: <HOME=/root>

X-Cron-Env: <PATH=/usr/bin:/bin>

X-Cron-Env: <LOGNAME=root>

X-Cron-Env: <USER=root>

MIME-Version: 1.0

Message-ID: <>

Return-Path: root@UCSERVER1




Cisco UC Tech Lead Senior Engineer


This is knonw issue on callmanager 8.6.

Bug: CSCtx32394

UC 8.6. Customer running an MCS HP Platform. Is seeing NDR when messages are being delivered to Exchange from CRON jobs. 

This is seen when the customer has an Exchange server called Mail


MCS HP Platform

The fix was added on callmanager 9.x however there is a workaround, open a new SR with TAC, so they can root on your system to apply the workaround.



Workaround available thru TAC if needed