-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parse Outlook's ARHs #423
Comments
Thanks for extracting this feature request from the liked issue, let's see how many up votes this will get. Sadly my first attempt at reporting this to Microsoft in the hope they will improve compatibility with the RFC failed miserably, did not get over the first level support (https://answers.microsoft.com/en-us/outlook_com/forum/all/authentication-results-header-written-by-outlook/890b304c-3c81-48b6-b065-36fad3b551e4). |
I found that microsoft support thread before I looked here @lieser, that was good for a laugh! A typical support experience indeed. Just throwing in my vote for outlook compatibility. While there is certainly some merit to applying pressure to Microsoft to comply with the relevant standards, it is the users who suffer in the intervening years. |
That's a very sad example of the ineffective support form Microsoft. Sadly it's typical, at lest the advice didn't include re-installing windows! |
@GlenWi It would be nice if you (and anyone else who wants this) could add a 👍 vote to the top post, that is the easiest way for me to track how often this is requested. |
Thanks Phillipe, I've done that now!
|
Hi, in #300 (comment) you suggest to open an issue to track this.
I'd be nice if the extension could parse (and trust) Authentication-Results header from Outlook. I did enable the "try non RFC compliant" option before reporting this.
Below are few samples of headers and their error:
The text was updated successfully, but these errors were encountered: