Re: [Evolution] OAUTH bellsouth.net and att.net addresses

[Japhering <japhering gmail com>]

On Sat, 2018-10-06 at 07:29 +0200, Andre Klapper wrote:

On Fri, 2018-10-05 at 21:51 -0400, Dr. John H. Lauterbach wrote:

I went to find the cause of send/receive problems with my

bellsouth.net e-maill address (has always worked fine on evolution)

and the first thing I found was version of evolution is now: 3.28.5-

0ubuntu0.18.04.1 and not 3.28.1-2 as it was previously.  Does this

new version of evolution do anything different that the previous one?

See https://gitlab.gnome.org/GNOME/evolution/commits/gnome-3-28 and 

https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-28

 for all the magic that has taken place in the mean time.

The second thing that I found is that I am caught up in the "OAUTH"

problem I saw some prior posts on for gmail.

Noone knows what "the OAUTH problem" is, I'm afraid...

Since I'm running a very similar configuration, I'll take a stab at it.

With said combination, every time Evolution shuts down and restarts, it reverts to attempting to use

OAuth2 for all Google connections, regardless of how it was configured when you shut it down. So every

time you start up Evolution, you have to re-edit the preferences to turn off OAuth2 and restart password/login.

Yet. even doing that, there are some Google calendars that only accept OAuth2 connections so you always

have an error bar at the top and no calendar availabilty.

Assuming that I can get the OAUTH key or whatever it is, where do I

put it in evolution to make things work?

Hard to say without clear details and more information why you think

that some yet undefined problem is somehow related to OAuth.

andre