The message is received by the exchange server on the correct email address as shown by this exchange message tracking log.
However the message headers below do not show my real email address anywhere.
Can you explain this behavior? I am trying to under the stand the process so I can explain it to my boss. I am also wondering if using the domain on xyz-cuc is best practices or not, and how to prevent these messages from getting flagged as spam.
Received: from xyz-CUC (10.10.10.10) by xyz-Mail01.xyz.local (10.10.10.11) with Microsoft SMTP Server id 14.2.347.0; Tue, 10 Jun 2014 12:47:31 -0700 X-CiscoUnity-RelayCount: 1 Date: Tue, 10 Jun 2014 19:47:27 +0000 From: Cisco Unity Connection Messaging System <unityconnection@xyz-cuc> To: <john.john@xyz-cuc> MIME-Version: 1.0 Message-ID: <MAL.8f0759f8-c58a-400d-969e-bf0bbae0fe56@xyz-cuc> X-CiscoUnity-HandlerId: c6ee9dc9-00a5-4538-84b9-210f4cd85b50 X-CiscoUnity-CallerAni: 87342233342 X-CiscoUnity-CallerName: ANN ARBOR MI X-CiscoUnity-CallerLang: ENU Importance: Normal X-Priority: 3 Sensitivity: None Subject: Message from ANN ARBOR MI (87342233342) X-CiscoUnity-MessageType: Voice Content-Type: audio/wav; name="VoiceMessage.wav" Content-Transfer-Encoding: Base64 Content-Disposition: inline; filename="VoiceMessage.wav"; voice=Voice-Message Return-Path: unityconnection@xyz-cuc X-MS-Exchange-Organization-AuthSource: xyz-Mail01.xyz.local X-MS-Exchange-Organization-AuthAs: Anonymous X-MS-Exchange-Organization-PRD: xyz-cuc X-MS-Exchange-Organization-SenderIdResult: Fail Received-SPF: Fail (xyz-Mail01.xyz.local: domain of unityconnection@xyz-cuc does not designate 10.10.10.10 as permitted sender) receiver=xyz-Mail01.xyz.local; client-ip=10.10.10.10; helo=xyz-CUC;
You could change the SMTP domain but, generally speaking, that's not the preferred/recommended route. Instead, you can setup a recipient policy in Exchange that defines an alternate SMTP name for the users in the format of the CUC SMTP domain.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...