Gnome Online Accounts fails to sign in Exchange emails

[Kevin L.]

After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked.

I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-online-accounts 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 16:38:32 2019
InstallationDate: Installed on 2018-03-24 (391 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you add your journalctl log after getting the issue?

[Kevin L. (demon1109)]

Added journalctl full log on a new install. Let me know if there's more specific info I can look up or provide.

[Kevin L. (demon1109)]

Added a log filtered for "goa-" items. Let me know if there's more specific info I can look up or provide.

[Kevin L. (demon1109)]

Also seeing this:

Apr 23 19:43:57 kevin-Dell-17 gnome-control-c[5696]: goa_ews_client_autodiscover() failed: 401 — Unauthorized
Apr 23 19:44:52 kevin-Dell-17 gnome-control-c[5696]: goa_ews_client_autodiscover() failed: 401 — Unauthorized
Apr 23 19:45:52 kevin-Dell-17 gnome-control-c[5696]: goa_ews_client_autodiscover() failed: 7 — Could not connect: Socket I/O timed out

[Sebastien Bacher (seb128)]

thanks

[Sebastien Bacher (seb128)]

Could you provide some extra details on what you are doing exactly. Is the account reporting an error in the settings/online account panel? Or in evolution?
Where is "Error 7: Unexpected response from server" displayed?
What version of exchange/server are you using?

[Kevin L. (demon1109)]

The error is in the Online Accounts menu from the settings panel. The Error 7 appears as a red box over the account sign in window after I enter the same credentials and server address I used in 18.10. I tested this on Majaro, Pop_OS and Ubuntu with Gnome 3.32 and it happens on all of them, so seems to be related to Gnome itself.

I believe we're on Exchange 2010 still. The account doesn't show up at all in Evolution since it never gets added to Online Accounts or Seahorse due to the error.

[Kevin L. (demon1109)]

And on the one machine, the install of 18.10 had the EWS account working, then on upgrade it wouldn't connect--kept asking for the password even after entering multiple times. I deleted the account and tried to set up again, but it failed with this same error.

On all of my installs (even fresh installs) the Microsoft Exchange option on Online Accounts appears with a red icon instead of the Exchange icon.

[Sebastien Bacher (seb128)]

Thanks, it does sound like an upstream issue indeed and should be reported upstream on https://gitlab.gnome.org/GNOME/gnome-online-accounts/. Could you do that or would you prefer us to resubmit it there for you?

[Kevin L. (demon1109)]

I have submitted upstream: GNOME/gnome-online-accounts#60

Thanks for your attention to this!

[Kevin L. (demon1109)]

https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/60

[Sebastien Bacher (seb128)]

Thanks!

[Sebastien Bacher (seb128)]

could you try if that's still an issue in newer Ubuntu series?

[Kevin L. (demon1109)]

Still seeing it on Ubuntu 20.04: Code 6: Unexpected response from server.

We did upgrade the version of Exchange used at my work within the last
year, but the odd part is setup and use works when I'm on the work network,
but not when I work from home (where it used to in versions of Gnome prior,
and in the Exchange version prior).

Not sure if it is a server issue on my employer's side, a network
configuration issue, or a Gnome issue, at this point.

On Mon, May 11, 2020 at 6:01 AM Sebastien Bacher <email address hidden> wrote:

> could you try if that's still an issue in newer Ubuntu series?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1825580
>
> Title:
> Gnome Online Accounts fails to sign in Exchange emails
>
> Status in gnome-online-accounts:
> New
> Status in gnome-online-accounts package in Ubuntu:
> Triaged
>
> Bug description:
> After upgrading from 18.10 and/or on fresh install, a known-working
> Exchange email setup fails to sign in, giving "Error 7: Unexpected
> response from server". Tested the same settings and credentials on a
> new install of 18.10 and it worked.
>
> I have Evolution and Evolution-ews installed on all instances, working
> in 18.10, not in 19.04.
>
> ProblemType: Bug
> DistroRelease: Ubuntu 19.04
> Package: gnome-online-accounts 3.32.0-1ubuntu1
> ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
> Uname: Linux 5.0.0-13-generic x86_64
> ApportVersion: 2.20.10-0ubuntu27
> Architecture: amd64
> CurrentDesktop: ubuntu:GNOME
> Date: Fri Apr 19 16:38:32 2019
> InstallationDate: Installed on 2018-03-24 (391 days ago)
> InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64
> (20180208)
> ProcEnviron:
> TERM=xterm-256color
> PATH=(custom, no user)
> XDG_RUNTIME_DIR=<set>
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: gnome-online-accounts
> UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+subscriptions
>

[Kevin L. (demon1109)]

Looking around some more, it seems it may be related to this: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974

I did add the suggested item to the /etc/gnutls and the account successfully is added to GOA now, but still isn't letting me download email due to a different error, but it does seem that it could be related to the TLS key length issue cited above.