3 ms·
Sadly, Thunderbird is becoming (or has become) a non-option in companies that use Outlook365/Microsoft365. Microsoft seems to have been quite effective in disab
by AnonC 3y ago
Sadly, Thunderbird is becoming (or has become) a non-option in companies that use Outlook365/Microsoft365. Microsoft seems to have been quite effective in disabling IMAP and SMTP as a default in these tenants and scaring companies that even with OAuth2, these are insecure and not as safe as sticking with Outlook as the client.
Companies (actually the information security teams) may be taking shortcuts based on Microsoft’s recommendations to reduce their work while imposing a huge cost on every worker.
It used to be that companies were locked in with Windows and MS Office. But there were some alternative options for those. IMO, now companies are heavily locked in to Microsoft by subscribing to Microsoft365. There is no migrating out or exit path for this. They just have to suffer through whatever Microsoft puts them through.
- Propelloni 3y agoWell, there is Owl [1], which I have mentioned before. Of course, it is the old "chase the rabbit" game we know since the 2000s -- MS365 is just a faster moving target than Exchange on MS Windows Server. So far the devs have kept up well, I can count the instances I had to fall back to OWA on one hand over the last year. And I use it daily within my company. [1] https://addons.thunderbird.net/en/thunderbird/addon/owl-for-exchange/ https://addons.thunderbird.net/en/thunderbird/addon/owl-for-...
- AnonC 3y agoYes, I know there’s Owl as well as some other (non-Thunderbird) options. But at the higher level, the teams defining what protocols to allow or disallow also manage the policies. That’s what I meant by Microsoft (influencing and) locking in companies.