<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<font size="-1">Ben,<br>
<br>
</font>On 11/10/2018 16:30, Ben Bucksch wrote:<br>
<blockquote
cite="mid:97891b41-1a3c-029b-1f71-718ac4d19d8f@beonex.com"
type="cite">
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<font face="Yu Gothic UI">So, with my company, we have been
developing a Thunderbird addon that uses the OWA protocol to
connect to Exchange servers. This should allow to read and write
email in Thunderbird with your Exchange account that has OWA
enabled. The name of the new extension is Owl.</font><br>
<p><font face="Yu Gothic UI">We are currently in the early alpha
stages, where we test internally and fix bugs. We should be
going into beta soon. We are currently fixing bugs and other
roadblocks in Thunderbid to make this happen and working with
Thunderbird developers to integrate these patches.</font></p>
</blockquote>
<br>
<font size="-1">This is a very interesting idea. Using OWA's
internal protocol is not something that I think I would have
thought of.<br>
<br>
Third party access to Exchange Server seems to be an ever-moving
target. According to one note about Exchange 2016 when it was
first launched[1], EWS itself is effectively deprecated, to
eventually be replaced by similar REST protocols to the ones used
by Office 365 for third party access.<br>
<br>
So using something other than EWS makes sense (especially, as you
say, as it's not necessarily available on all corporate
installations). On the other hand, Microsoft could change the OWA
protocol at any time, couldn't they?<br>
<br>
Of course, EAS (ActiveSync) would be the best, longer-term
supported third party access protocol but that requires a patent
licence. May I ask, did you look into doing that?<br>
</font><br>
<br>
<br>
Footnote:<br>
1: Sorry, I can't find a link to it now. It was probably on the
Exchange blog back when E2016 was launched. It promoted the
still-to-be-released (at the time) REST protocols for on-premises
Exchange 2016 (and later) as a future direction for third party
access instead of EWS.<br>
<br>
<pre class="moz-signature" cols="72">--
Mark Rousell
</pre>
</body>
</html>