Are there any plans to switch to OAuth2.0 in emClient in line with this recommendation from Google? Alternately, is there any reason I should (or should not ) be concerned about this?
Hi, yes this is planned for future releases of eM Client, however it might be included in version 7 or some of it’s early updates.
We are not using OAuth at the moment since som of the features we were using were still not supporting this, however there’s no need to be concerned about eM client and OAuth at the moment since with eM Client your password and your data is still on your computer, you should only be concerned when using 3rd party apps, where you provide the password to a service that manages these data (online apps etc.).
I received the following reply to my eM Client support ticket: “At this moment it is not supported and unfortunately due to some implementation difficulties I cannot provide any ETA but in general we would like to implement this functionality in the future.” Darn.