![mac mail exchange connection mac mail exchange connection](https://cdn.ten9itservices.com/assets/uploads/2017/08/1791_2.png)
But if that was the issue, why did Outlook for Mac work without any errors?Īnyhow, I proceeded changing the 100-continue handling by changing it from default setting of RFC-2616 compliant, to RFC-7231 compliant instead:Īfter changing this setting, I ran the EWS test from exrca website again, and as one would expect, the test passed with no issues. They may could find some information for you.
![mac mail exchange connection mac mail exchange connection](https://cdn.osxdaily.com/wp-content/uploads/2019/12/add-account-to-mac-mail-1-610x415.jpg)
So, I would suggest you open a service request to confirm with Office 365 team. It would be easy to blame load balancer at this point and implement the recommended fix by changing 100-continue handling on LoadMaster. This article talks about this limitation about Exchange online mailbox, however it doesnt contains the limitation about mailbox connection. The issue is also documented by Brian Reid: Exchange Web Services (EWS) and 501 Error and Phil Sharp: Kemp Load Balancer and Lync Unified Contact Store Integration Note.Īfter enabling L7 debug tracing on my KEMP LoadMaster I observed the same error mentioned in the above articles “lb100 kernel: L7: badrequest-client_read (-501):
#MAC MAIL EXCHANGE CONNECTION PASSWORD#
Enter your exchange account information and select 'Add Account.' Enter your email ID and password for NMU. Go to Tools > Accounts in your Outlook for Mac and check over the Exchange Account. I knew about this particular error as I had worked with Michael Van Horenbeeck and is documented here: Click the 'Tools' menu and select 'Accounts.' 3. The remote server returned an error: (501) Not Implemented.” To my surprise, the test failed with the error “Message: The request failed. Microsoft provides great testing tools for Exchange on so I decided to run EWS connectivity test from the toolset.
![mac mail exchange connection mac mail exchange connection](https://d33wubrfki0l68.cloudfront.net/1ae31e17d21340ca2072a5b793aa3102dbfdb9e6/09b5f/how-to/manually-configure-mac-mail-for-email-hosted-on-exchange-2010/mm102.png)
What I didn’t know at that point is which element in the HTTP request was causing the server to reject the request. The error is somewhat misleading as when you look at EWS logs on Exchange server, you see that the server rejected the request with HTTP error 400 which translated to “bad request”. Mac Mail would show “Account Error” which read “Unable to connect … The server returned error: Connections to host on default ports failed.” It is worth pointing out that while Outlook 2013/2016 on PC use MAPI/HTTP or RPC/HTTP to connect to Exchange 2013/2016 servers, both clients on Mac (Mac‘s own Mail client and Microsoft Outlook for Mac) use EWS to connect. Latest Microsoft Outlook for Mac did not exhibit any issues either! Microsoft Outlook 2013/2016 clients on PC did not exhibit any issues.