Sorry, but your institution id conflating protocols with authentication. It does not help you any that they apparently are not able to define a difference. SMTP, IMAP, POP and activesync are all access protocols. Oauth is an authentication method that is used to authenticate to those services.

I think it would be a slightly more accurate to say we demand you use activesync (Microsoft Exchange Proprietary) protocol. If you don't we are not playing. The rest is just so much dross and excuses.

I have dropped a note to the developer of the owl addon for exchange. Perhaps he can tell me if the addon might be a solution for you.

.

Hi epoehler,

I'm the owner of Beonex and Owl. First, to answer Matt's question, Owl does not use SMTP, but implements the native Exchange protocols for sending and receiving mail. It can use both password-based auth and "Modern Authentication" / OAuth2. Owl is made specifically to receive and send mail via Exchange and Office365.

I have difficulty to understand what "your institution" wrote. SMTP can use either OAuth2, or password based authentication, or IP-address-based authentication. While it's true that Thunderbird without Owl can send mail only via SMTP, Thunderbird can use SMTP with OAuth2.

Ben Bucksch Beonex, Owl addon

Thanks, Matt for helping me understand that distinction. Thanks, also, to Ben for creating Owl. I was able to install owl and am now sending mail. To do so, however, I needed to roll back to Thunderbird 91.5. Will Owl be compatible with later versions of Thunderbird eventually?

Hi epoehler, Owl supports the official Thunderbird releases, but not Thunderbird betas. We make an effort to make Owl compatible shortly before the TB release comes out. Once the next official Thunderbird release comes out, Owl should be compatible with it by then.