Message Headers In Exchange 2013

The Exchange Team has given a bit of thought to the message headers in Exchange 2013. This is a direct result of the number of transport services in 2013. The “new” message headers make it easier to figure out which transport service dealt with the email at a given time. This is quite handy as…

The Exchange Team has given a bit of thought to the message headers in Exchange 2013.

This is a direct result of the number of transport services in 2013. The “new” message headers make it easier to figure out which transport service dealt with the email at a given time. This is quite handy as there are three transport services in a mailbox role and one in CAS.

The header exposes the version of Exchange as well – 15.0.712.22 in my case (CU2).

Mailbox Transport in header

FET in header

Received: from HMBX1.HOWLYNCWORKS.LAB (192.168.0.102) by
HMBX1.HOWLYNCWORKS.LAB (192.168.0.102) with Microsoft SMTP Server (TLS) id
15.0.712.22 via Mailbox Transport; Thu, 18 Jul 2013 00:47:15 +0100
Received: from HCAS1.HOWLYNCWORKS.LAB (192.168.0.103) by
HMBX1.HOWLYNCWORKS.LAB (192.168.0.102) with Microsoft SMTP Server (TLS) id
15.0.712.22
; Thu, 18 Jul 2013 00:47:15 +0100
Received: from mail-we0-f181.google.com (74.125.82.181) by
HCAS1.HOWLYNCWORKS.LAB (192.168.0.103) with Microsoft SMTP Server (TLS) id
15.0.712.22 via Frontend Transport; Thu, 18 Jul 2013 00:46:50 +0100
Received: by mail-we0-f181.google.com with SMTP id p58so2264352wes.26
for <Rajith@howlyncworks.com>; Wed, 17 Jul 2013 16:46:48 -0700 (PDT)

Date: Thu, 18 Jul 2013 00:46:07 +0100
Message-ID: <CABXYMuSzBVuFSUwHdse_8zXSjUMZkQaMzZdjTU3G_CnyZLqyuw@mail.gmail.com>
Subject: Hello
To: <Rajith@howlyncworks.com>
Content-Type: multipart/alternative; boundary=”047d7ba975e6f4aab104e1bdb4d4″
Return-Path: X-MS-Exchange-Organization-Network-Message-Id: ee6f0447-6b29-4d10-aaa5-08d0515f19a4
X-MS-Exchange-Organization-AVStamp-Enterprise: 1.0
X-MS-Exchange-Organization-AuthSource: HCAS1.HOWLYNCWORKS.LAB
X-MS-Exchange-Organization-AuthAs: Anonymous

Keep an eye on the transport service in the message headers and you will be able to troubleshoot problems quicker ;)

Leave a Reply

Your email address will not be published. Required fields are marked *