• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 387
  • Last Modified:

Exchange 2007 outgoing mail seems to be leaving out header field data

Exchange 2007 server with Blackberry Ent. Server, also sends external mail through Postini service. We are trying to implement Spiceworks management, especially the help desk ticket system which is supposed to read emails from an inbox and create trouble tickets  from them.

We have a working email setup for Spiceworks to talk to Exchange, incoming and outgoing, using the Exchange settings. However, when we send a ticket via email to the Spiceworks mailbox and have Spiceworks refresh tickets, we see the mailbox message go from inbox to deleted, but no ticket gets created. Spiceworks tech support says that based on the log files we've sent them, the ticket system is reading the message and not seeing a "From" address for whom the ticket can be created, so no ticket is made.

I'm including a section of the logs below from a conversation with tech support to see if anyone else can suggest what might be wrong with my Exchange configuration to cause this.

Spiceworks support has asked me to switch to IMAP and SMTP instead of Exchange connectivity, but I don't see how that's going to affect the message headers. I will also add that the guy who configured this server originally did a half-xxx job, so we're just thankful it mostly works in general. I also am having all kinds of problems with IMAP but that belongs in another question. Spreading the love and the points around.

I[10:40:04.73 e500d4] =====
Content-Type: multipart/mixed; boundary=mimepart_4da47254b2eac_b80272806a1c3

Content-Type: text/plain; charset=utf-8

Content-Transfer-Encoding: Quoted-printable
Content-Disposition: inline

Below is an example from another system that is sending notifications correctly:

I[16:33:25.86 aa5f6c] =====
Received: from Magnafix.aastvedt.lokal by Magnafix.aastvedt.lokal with mapi; Tue, 12 Apr 2011 16:33:10 +0200
Date: Tue, 12 Apr 2011 16:33:10 +0200
From: [email address]
To: [email address]
Message-Id: <E2EC5496AB4FB5438E656BC5C42C8BDE07B9DB8A00@Magnafix.aastvedt.lokal>
Subject: Test 11
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary=mimepart_4da462b5d22f7_3003d52fb61c1
Content-Transfer-Encoding: Binary
Thread-Topic: Test 11
Thread-Index: Acv5HoWuf6TNIODgRw+hzS52HKTp0Q==
Accept-Language: nb-NO
Content-Language: nb-NO
X-Ms-Exchange-Organization-Scl: -1
X-Ms-Tnef-Correlator: <E2EC5496AB4FB5438E656BC5C42C8BDE07B9DB8A00@Magnafix.aastvedt.lokal>


Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: Quoted-printable
Content-Disposition: inline

Open in new window

This is the "message details" text from a recent attempt at the same thing:

Received: from EXCHANGE.mmi.local ([]) by EXCHANGE.mmi.local
 ([]) with mapi; Mon, 18 Apr 2011 21:20:49 -0500
Content-Type: application/ms-tnef; name="winmail.dat"
Content-Transfer-Encoding: binary
From: Shannon Testing <shan.test@mmiincorp.com>
To: IT <IT@mmiincorp.com>
CC: "smollenhauer@gmail.com" <smollenhauer@gmail.com>
Date: Mon, 18 Apr 2011 21:20:02 -0500
Subject: help desk ticket request
Thread-Topic: help desk ticket request
Thread-Index: AQHL/jhlRw7i1lUmBE+Y2DuCC+BDkQ==
Message-ID: <EC32C5A8D86DDA4483A9A431C864F99F5C8E00A898@EXCHANGE.mmi.local>
Accept-Language: en-US
Content-Language: en-US
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: <EC32C5A8D86DDA4483A9A431C864F99F5C8E00A898@EXCHANGE.mmi.local>
MIME-Version: 1.0
All the fields appear to be there so I'm trying to narrow down whether this is Exchange's fault or Spiceworks'.

Open in new window

Shannon Mollenhauer
Shannon Mollenhauer
1 Solution

Kindly find the below article
look for the "How Header Firewall is Applied to Organization X-Headers " in article.


Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now