EWS experimental.mail.ews.overrideOAuth.enabled seems to not be applied to send emails
I have been testing the new EWS support for thunderbird using version 144.0.1. My account needs the option `experimental.mail.ews.overrideOAuth.enabled` set to `true` to specify specific OAuth2 values (Application ID, Tenant ID,...). I see that receiving emails is OK (although the OAUth2 login page is popped up all the time and immediately hidden again, for every email I select, but maybe I have something weird because this is just a test).
But I cannot send emails using that account. My feeling is the advanced overrideOAuth configuration is not used for the sending/outgoing server. Just for the incoming server part. Am I alright? Is there anyway of setting this overrideOAuth values for the outgoing sending server?
I have tested the same with evolution and I can receive and send emails. So I'm pretty sure that the outgoing part can work when using the correct overridden OAuth2 values.
所有回复 (2)
Thanks for testing out the custom OAuth2 parameters in Exchange! It's still an experimental feature, and we don't have access to accounts with all of the options that are available, so it's really helpful for folks to try this with their own setups. It looks like you're using 144. For that version, we had the incoming server customization, but the outgoing server wasn't yet using it. However, in 145, which is currently in beta, both incoming and outgoing should be using the same parameter set. Would you be interested in trying the current 145 beta to see if incoming and going both work for you there?
Also, if you're interested in trying beta builds, you can join the beta mailing list here and/or the Thunderbird developers Matrix channel here .
Thanks again!
More about beta at https://support.mozilla.org/en-US/kb/thunderbird-beta