I’m looking at replacing Outlook with eM (my trial finishes in about a week). Greate product, just 1 question really, not sure if its a bug or not…
I have 6 email accounts setup and I’ve noticed full headers are not shown for the 3 accounts connecting to and Exchange Server (2013 I think). Is this a limitation of connecting to an Exchange Server? I can see the full headers in Outlook ok.
Thanks for your time.
Hi Cary, not completely sure what you’re referring to, what information are you missing in the header?
Can you make a screenshot of the header in comparison to Outlook and post it here on the forum?
Thank you,
Paul.
Hi Paul - it’s mainly the routing information that appears to be missing - I occasionally use this to check/validate the source of an email
Example message headers below for the same message
Regards,
Cary.
emClient (View mail header)
From: …
To: …
Subject: - Important - Access to emails
Date: Fri, 21 Nov 2014 10:58:03 +0000
Message-Id: <5f22420a2709446a9ec46c800c845402@Derb…>
Reply-To: …
X-Priority: 1 (highest)
Importance: high
Mime-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Outlook 2013 (Message Options/Internet Headers)
X-Antivirus: AVG for E-mail
Received: from DERBY-EXCHANGE.TRACSIS.local (10.0.2.3) by
DERBY-EXCHANGE.TRACSIS.local (xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id
15.0.516.32 via Mailbox Transport; Fri, 21 Nov 2014 10:58:04 +0000
Received: from DERBY-EXCHANGE.TRACSIS.local (10.0.2.3) by
Derby-Exchange.TRACSIS.local (xxx.xxx.xxx.xxx) with Microsoft SMTP Server (TLS) id
15.0.516.32; Fri, 21 Nov 2014 10:58:03 +0000
Received: from DERBY-EXCHANGE.TRACSIS.local ([fe80::54b1:3e43:afb:9f58]) by
Derby-Exchange.TRACSIS.local ([fe80::54b1:3e43:afb:9f58%16]) with mapi id
15.00.0516.029; Fri, 21 Nov 2014 10:58:03 +0000
Content-Type: application/ms-tnef; name=“winmail.dat”
Content-Transfer-Encoding: binary
From: …
To: …
Subject: - Important - Access to emails
Thread-Topic: - Important - Access to emails
Thread-Index: AdAFd4z+COAqdTJDQ4usuHyH9jzoZw==
Importance: high
X-Priority: 1
Date: Fri, 21 Nov 2014 10:58:03 +0000
Message-ID: <5f22420a2709446a9ec46c800c845402@Derb…>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: <5f22420a2709446a9ec46c800c845402@Derb…>
MIME-Version: 1.0
X-MS-Exchange-Organization-AuthSource: Derby-Exchange.TRACSIS.local
X-MS-Exchange-Organization-AuthAs: Internal
X-MS-Exchange-Organization-AuthMechanism: 03
X-Originating-IP: [xxx.xxx.xxx.xxx]
X-MS-Exchange-Organization-Network-Message-Id: bb7e2bb7-b8f1-485f-c013-08d1d391287a
Return-Path: …
Hi Cary, this is not an issue of the application, this is due to different protocol use. Outlook is using ActiveSync to synchronize your Exchange account and ActiveSync protocol contains more information about the message in the message header. eM Client on the other hand is using Exchange Web Services protocol to synchronize your data with the server and displays a considerable less amount of information in the header.
Hope this explains it,
Paul.
Perfect Paul - thank you.
Glad I could help, please make sure to let us know if you come across any other issues or questions about the application, we’ll be happy to help.
Thank you,
Paul.