Figure out how to parse these - they miss the ; before the date
Received: by filter0383p1iad2.sendgrid.net with SMTP id filter0383p1iad2-15318-5AB8F728-C
2018-03-26 13:35:36.270951634 +0000 UTC
Received: from smtp.github.com (out-8.smtp.github.com [192.30.252.199])
by ismtpd0003p1iad2.sendgrid.net (SG) with ESMTP id gDQRSEGgSqCsi9tFtF1Vtg
Mon, 26 Mar 2018 13:35:36.102 +0000 (UTC)

Reported in comments for #37 by @luisjmoreno

-------- Outlook for Mac
User Agent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/604.5.6 (KHTML, like Gecko)
Requirement set = 1.5
hostname = Outlook
hostVersion = 16.9 (180116.02)
itemType = message
itemClass = IPM.Note
contentLanguage = en-US
displayLanguage = en-US
touchEnabled = false
ERROR: Unable to obtain callback token.
[object Object]
ShowError()@https://mha.azurewebsites.net/Scripts/uiToggle.js:93:13
{anonymous}()@https://mha.azurewebsites.net/Scripts/GetHeadersRest.js:21:22
{anonymous}()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-mac-16.00.js:9:165814
{anonymous}()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-mac-16.00.js:9:158350
agaveResponseCallback()@user-script:9:1:9847
agaveHostCallback()@user-script:9:1:5046
agaveHostCallback()@user-script:9:1:2578
{anonymous}()@https://mha.azurewebsites.net/pages/default.html?_host_Info=Outlook$Mac$16.02$en-US:1:60
global code()@https://mha.azurewebsites.net/pages/default.html?_host_Info=Outlook$Mac$16.02$en-US:1:135
ERROR: Unable to obtain callback token.
[object Object]
ShowError()@https://mha.azurewebsites.net/Scripts/uiToggle.js:95:23
{anonymous}()@https://mha.azurewebsites.net/Scripts/GetHeadersRest.js:21:22
{anonymous}()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-mac-16.00.js:9:165814
{anonymous}()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-mac-16.00.js:9:158350
agaveResponseCallback()@user-script:9:1:9847
agaveHostCallback()@user-script:9:1:5046
agaveHostCallback()@user-script:9:1:2578
{anonymous}()@https://mha.azurewebsites.net/pages/default.html?_host_Info=Outlook$Mac$16.02$en-US:1:60
global code()@https://mha.azurewebsites.net/pages/default.html?_host_Info=Outlook$Mac$16.02$en-US:1:135
User Agent = Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/604.5.6 (KHTML, like Gecko)
Requirement set = 1.5
hostname = Outlook
hostVersion = 16.9 (180116.02)
itemType = message
itemClass = IPM.Note
contentLanguage = en-US
displayLanguage = en-US
touchEnabled = false
ERROR: Unable to obtain callback token.
[object Object]
ShowError()@https://mha.azurewebsites.net/Scripts/uiToggle.js:93:13
{anonymous}()@https://mha.azurewebsites.net/Scripts/GetHeadersRest.js:21:22
{anonymous}()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-mac-16.00.js:9:165814
{anonymous}()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-mac-16.00.js:9:158350
agaveResponseCallback()@user-script:13:1:9847
agaveHostCallback()@user-script:13:1:5046
agaveHostCallback()@user-script:13:1:2578
{anonymous}()@https://mha.azurewebsites.net/pages/default.html?_host_Info=Outlook$Mac$16.02$en-US:1:60
global code()@https://mha.azurewebsites.net/pages/default.html?_host_Info=Outlook$Mac$16.02$en-US:1:13

Outlook desktop and ios keep caching the pages and refusing to look for new version. See if we can no-cache our way out of this:
https://stackoverflow.com/questions/49547/how-to-control-web-page-caching-across-all-browsers

Not that it's always bad, but it is a hallmark of phishing, so may be worth calling out

If we've done the data/view split right, I should be able to toggle between old and new UI. Explore how to do this...

This is such a well known scenario we don't need to generate any logs for it.

Suppress logging for errors like this:
"Message was missing transport headers. If this is a sent item this may be expected."

Hi,
Am I missing something? I have installed MHA and it works fine in OWA but in outlook 2016 (1801 Build 8828.2010) I get the following error.

ADD-IN Error
The Add-in could not be started. Close this dialog to ignore this problem or click "Restart" to try again.

No matter how many times i click restart nothing happens

Thanks

Hi,
Is this project also licensed under the MIT License?

Browser version: Chrome 49.0
Exception type: Unsupported time zone specified undefined
Failed method: Received.init
Operation name: /pages/newDesktopFrame.html
Problem Id: Unsupported time zone specified undefined at Received.init
url: https://mha.azurewebsites.net/Scripts/Received.js

row.date = new Date(row.date).toLocaleString();

View this instance in the Azure portal<\a>
View similar exceptions in this time range<\a>

(ported from #18 for @luisjmoreno)
Hi Stephen,
Bad news, I noticed a new change on the MHA version. Unfortunately, this new version broke everywhere in all my devices Mac, Windows and Internet Browsers. MHA doesn't work on any browser or email client such as Outlook for Windows or Mac.
Before this new version / change, MHC was working only on Outlook for Windows. Now, when I run MHA on an email on Windows, I get a message that says "Failed to retrieve headers". I have removed and re-added the app and still does not work.
Screen shot in Outlook for Mac

Screen shot in Outlook for Windows

Screen shot within OWA using Google Chrome (same results within other browsers, including IE)

We are running Exchange 2013 CU18 on premises. I have a different email on Outlook.com where I use MHA too and it works there. Please help!!

IE - https://unpkg.com/[email protected]/dist/sbcs.full.js

Reported in comments of #38 by @Vierxa and #37 by @luisjmoreno.

From @Vierxa
User Agent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36
Requirement set = 1.5
hostname = OutlookWebApp
hostVersion = 15.1.1415.2
OWAView = ThreeColumns
itemType = message
itemClass = IPM.Note
contentLanguage =
displayLanguage = fr-FR
touchEnabled = false
ERROR: Cannot parse given Error object
OK

From @luisjmoreno
----- ------- --Firefox on Windows
User Agent = Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:58.0) Gecko/20100101 Firefox/58.0
Requirement set = 1.3
hostname = OutlookWebApp
hostVersion = 15.0.1347.5
OWAView = ThreeColumns
itemType = message
itemClass = IPM.Note
contentLanguage =
displayLanguage = en-US
touchEnabled = undefined
ERROR: Cannot parse given Error object
parse@https://cdnjs.cloudflare.com/ajax/libs/stacktrace.js/2.0.0/stacktrace-with-promises-and-json-polyfills.min.js:1:1299
fromError/<@https://cdnjs.cloudflare.com/ajax/libs/stacktrace.js/2.0.0/stacktrace-with-promises-and-json-polyfills.min.js:2:14676
fromError@https://cdnjs.cloudflare.com/ajax/libs/stacktrace.js/2.0.0/stacktrace-with-promises-and-json-polyfills.min.js:2:14644
LogError@https://mha.azurewebsites.net/Scripts/uiToggle.js:117:9
ShowError@https://mha.azurewebsites.net/Scripts/uiToggle.js:93:5
callbackEWS@https://mha.azurewebsites.net/Scripts/GetHeadersEWS.js:60:9
sendHeadersRequestEWS/<@https://mha.azurewebsites.net/Scripts/GetHeadersEWS.js:18:13
makeEwsRequestAsync/i.onreadystatechange@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlookwebapp-15.01.js:17:5497
$2P_1@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlookwebapp-15.01.js:17:55509
$m_1/<@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlookwebapp-15.01.js:17:59912

{"error":{"code":"ErrorInvalidRequest","message":"The OData request is not supported. REST APIs for this mailbox are currently in preview. You can find more information about the preview REST APIs at https://dev.outlook.com/."}}

Also - figure out why I had to go to fiddler to get this - why didn't it bubble up?

https://github.com/framework7io/framework7

Exception type: Unable to get property 'itemId' of undefined or null reference
Failed method: sendHeadersRequestEWS
Operation name: /pages/parentframe.html
Problem Id: Unable to get property 'itemId' of undefined or null reference at sendHeadersRequestEWS
Telemetry type: exception

TypeError: Unable to get property 'itemId' of undefined or null reference
at sendHeadersRequestEWS (https://mha.azurewebsites.net/Scripts/GetHeadersEWS.js:24:9)
at Anonymous function (https://mha.azurewebsites.net/Scripts/GetHeadersRest.js:32:17)
at Anonymous function (https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-win32-16.02.js:9:165885)
at Anonymous function (https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-win32-16.02.js:9:157860)

View this instance in the Azure portal<\a>
View similar exceptions in this time range<\a>

Looks like I can use this:
https://www.npmjs.com/package/uri-js

https://stackoverflow.com/questions/3457391/how-do-you-use-window-postmessage-across-domains

EWS requires too many permissions and only REST will work on mobile

I can see the MessageHeaderAnalyzer for messages in my primary Exchange mailbox.

Other add-ins like the "Unsubscribe" add-in shows up for other mailboxes I access in my Office 365 Exchange Online environment like shared mailboxes and directly set up Exchange accounts.

However, MessageHeaderAnalyzer is nowhere to be seen when I look at shared mailboxes or secondary Exchange accounts.

It is the same both for local Outlook 2016 and for OWA.

Any suggestions? Thanks! :)

Have confirmed I can import codepage from npm. Need to migrate remaining HTML from my copy of codepage and remove it completely.

Hi Stephen. Great plugin!

Mine has been erroring out on every system with "The operation failed"

Have you seen this reported? Any ideas? Outlook 2016 running on Exchange 2016 server.

Migrated from #18 for @Vierxa.
Hello Stephen,
I exerience the same issue.
https://user-images.githubusercontent.com/36500601/36247894-e75ce784-1235-11e8-963a-49e11e361309.png

Thanks for helping me.

https://user-images.githubusercontent.com/36500601/36727851-0dec61ee-1bbf-11e8-8567-e566cf605ad0.png

Installed and visible in all Outlook clients, but only works on my laptop - on all three desktop PCs the MHA window just displays 'Message Header Analyzer' with a partial rendering of what should be visible in the area immediately below (or nothing at all). Here's a screen clip:

...and no header info.
This is a real pity because it'd be a real time-saver if it worked on the machines I need it to.
Hope you can help.
I'm running Windows Pro 32 (1703) with Firefox 54.0.1

https://stackoverflow.com/questions/30546795/how-to-detect-when-one-or-more-js-css-library-fail-to-load-e-g-cdn

Probably need to rethink registerItemChangeEvent - maybe unregister the old one?

Repro Steps:
1 - Pin app
2 - In folder with many items, hold down down arrow
3 - Profit!

Browser version: Internet Explorer 11.0
Exception type: Unable to get property '_permissionLevel$p$0' of undefined or null reference
Failed method: canUseRest
Operating system: Windows 10
Operation name: /pages/desktoppane.html
Problem Id: Unable to get property '_permissionLevel$p$0' of undefined or null reference at canUseRest
SDK version: javascript:1.0.15
Telemetry type: exception

View this instance in the Azure portal<\a>
View similar exceptions in this time range<\a>

Hey,

I use the plugin quite extensively. Also on the Outlook for iOS. However, since a couple of days, it stopped working. I always end up with a screen titled "MOBILE DIFFERENTIATION PAGE" and it tells me "YOU SHOULD NOT BE HERE" and "Diagnostics". That's all. I guess the message is right, I shouldn't be there. How can I avoid getting there and get the information it is supposed to show?
It doesn't matter what mail I use the plugin on. The result is always the same. However, on Outlook for Windows, it works as expected for the same emails. I am using Office 365.
Any ideas?

Add stack of error to diagnostics

Right now dependent on [email protected]. Watch for SheetJS/js-codepage#14 to be fixed and update when it is.

Resources:
https://enable-cors.org/server_iis7.html <- server side stuff
https://stackoverflow.com/questions/41069330/with-script-crossorigin-anonymous-why-is-a-script-blocked-by-cors-policy <- script tags
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-asp-net-exceptions#browser-exceptions <- app insight reasoning for CORS

All landing pages do the same thing now with the only difference being the default UI - so we can use one single landing page with options passed in to control the default. We can use redirects to avoid changing the manifest for now, and then change manifest later and ditch redirects

If we have many errors, diagnostics is too tall - limit the size of the viewport and let it scroll

We have many users who access their primary mailbox in Outlook but also use Shared mailboxes. We use the latest version of MHA add-in (v3.1). The add-in works perfectly for messages sent to the primary mailbox but it fails when looking at message headers sent to those shared mailboxes. It simply displays summary diagnostics as shown below.

The users have disabled/re-enabled the add-in to no avail. I also tried disabling all other add-ins in Outlook but that made no difference. Any hints for us? This has stumped me so far.

Thank you!

Or Node - either way - get rid of my local copy

Should be based on the apple UI, but done the android way.

It would be great, if the ip-address and dns-names are clickable to analyze the information about that address.
E.G. By www.Utrace.de or www.mxtools.com or another Information source.

Need to ensure any exception in the GetHeaders path (including async) is caught and logged, and doesn't leave us with a spinny.

Headers aren't displayed and you receive this error:

{ "readyState": 4, "responseText": "", "status": 404, "statusText": "Not Found" }

Log whether we used EWS or Rest into diagnostics. Bonus points for working the logic into the log.

First and foremost this is a great product. Thank you for working tirelessly on it.

We are using O365 Gov cloud and I know REST has been disabled there. Also we do EWS filtering and our allow list consist of the following agents.
-EwsAllowList "Outlook-Android/","Outlook-iOS/","ExchangeService
sClient/","outlook","MAPI","skype","Microsoft+Office/","UCCAPI/","OC/","OCPhone/","Microsoft Office/","MacOu
tlook/*"

Could either of these issues be the cause of why MHA is not working for us. Any ideas?

We get the following when we click the MHA icon on an email within Outlook.
textStatus: error errorThrown: State: rejected jqXHR: { "readyState": 4, "responseText": "{"error":{"code":"ErrorAccessDenied","message":"Access to OData is disabled."}}", "responseJSON": { "error": { "code": "ErrorAccessDenied", "message": "Access to OData is disabled." } }, "status": 403, "statusText": "error" }

Need to update your add-in to add buttons on the ribbon. See https://dev.office.com/docs/add-ins/outlook/add-in-commands-for-outlook.

Now that we have a top level menu, we can host diagnostics there which should always work, even when the rest of the UI is failing for some reason

User Agent = Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; rv:11.0) like Gecko
Requirement set = 1.5
contentLanguage = en-US
displayLanguage = en-US
touchEnabled = 0
hostname = Outlook
hostVersion = 16.0.8431.2236
itemType = message
itemClass = IPM.Note
permissions = 3
ERROR: Unable to obtain callback token.
{
"value": null,
"status": "failed",
"error": {
"name": "Internal Error",
"message": "An internal error has occurred."
}
}
Anonymous function()@https://mha.azurewebsites.net/Scripts/GetHeadersRest.js:36:21
Anonymous function()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-win32-16.02.js:9:165885
Anonymous function()@https://appsforoffice.microsoft.com/lib/1.1/hosted/outlook-win32-16.02.js:9:157860

It would be very useful if MHA worked on mail-enabling a public folder.

Currently compares "You cannot perform this action. This add-in scenario is not supported in this folder."

[maybe related to #17 Enhancement Request: support for Shared Mailboxes]

Summary shows the subject is
�j fiók meger�sítés Törölj ki kérlek Törlend� részére

Source

Subject: =?utf-8?B?w5pqIGZpw7NrIG1lZ2VyxZFzw610w6lzIFTDtnLDtmxqIGtpIGvDqXJsZWsgVMO2cmxlbmTFkSByw6lzesOpcmU=?=

Please advise.

on https://outlook.live.com/owa/

MHA is proving very useful for Incident Response teams. It would be terrific if MHA worked with Shared Mailboxes. Proposed use-case: potential phishing messages are redirected to a shared mailbox. Admins log into the Shared Mailbox to triage messages, confirm they are phishing attacks, and inspect the message headers for useful detection data.

The ability to quickly export the headers or print them right from the addin would be very helpful when analyzing multiple messages.