Comment Re:Microsoft might be right about this one (Score 1) 29
As you say that, I can't help but notice that this is a Microsoft story that didn't immediately spur a hundred knee-jerk, "M$ sux, use Linux" posts.
IMO, it's because OWA Light was a last resort, and the wrong one. For a Linux user that was looking for lightweight access, using a 3rd party email client over IMAP was the way to go. HOWEVER, Microsoft effectively killed that already.
One can technically access O365 mail from 3rd party clients, even making correct use of XOAUTH2 from ancient clients like Mutt and Pine (now "Alpine"). But that requires the domain admin to specifically allow those clients because the auth flow includes a client identifier - and you can't just fake it like the HTTP User-Agent. That effectively bars use of all 3rd party clients (Ex. I can't even use Thunderbird to get my work email). In addition, they've recently changed some things related to the "Authorize" and "Device" flows (https://support.mozilla.org/en-US/kb/microsoft-oauth-authentication-and-thunderbird-202). Lastly, the "Authorize" flow requires that a company exists and is registered to the client (FWIW, this is currently preventing Alpine from supporting the Authorize flow, as it is a one developer open source thing).
Long story short: The exchange ship already set sail. The real argument/debate (besides not using exchange to begin with) is in ensuring other IMAP clients can still use the service. Who cares about OWA Light?