Bug 22655

Summary:	KMail/Akonadi: Cannot reconfigure Googlemail IMAP account
Product:	Mageia	Reporter:	Ulrich Beckmann <bequimao.de>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	Normal	CC:	mageia, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
See Also:	https://bugzilla.redhat.com/show_bug.cgi?id=1543140 https://bugs.mageia.org/show_bug.cgi?id=23035
Whiteboard:	MGA6-64-TOO
Source RPM:		CVE:
Status comment:
Attachments:	Excerpt of journal and list of installed packages

Description Ulrich Beckmann 2018-02-25 17:35:33 CET

I had a working KMail instance with a Googlemail IMAP account on Cauldron. Some time ago, there was a workflow that required access to Google Services for Akonadi. The workflow failed, and now I am trying to reconfigure my KMail accout.

The workflow passes now, but no mail is retrieved. The Akonadi resource is marked as ready. The connection settings under Accounts => Receiving => Modify => Advanced can no longer be configured manually. They are greyed out. Although another IMAP account (non-Google) is working fine.

Greetings
Ulrich

N.B. I installed libkgapi, see also https://bugzilla.redhat.com/show_bug.cgi?id=1543140
Here libkgapi was used to fix an workflow error, so I guess that it is necessary, though not installed through dependencies in Mageia.

Comment 1 Ulrich Beckmann 2018-02-25 17:37:29 CET

Created attachment 10004 [details]
Excerpt of journal and list of installed packages

Comment 2 Marja Van Waes 2018-02-26 08:51:50 CET

did you try whether installing libkgapi fixed it, Ulrich?

See Also: (none) => https://bugzilla.redhat.com/show_bug.cgi?id=1543140
Assignee: bugsquad => kde
CC: (none) => marja11

Comment 3 Marja Van Waes 2018-02-26 08:52:42 CET

(In reply to Marja van Waes from comment #2)
> did you try whether installing libkgapi fixed it, Ulrich?

forget that, it is in your list of installed packages:

libkgapi-17.12.2-1.mga7

Comment 4 Ulrich Beckmann 2018-03-02 21:11:05 CET

After a full upgrade against updates_testing I find the issue in Mageia 6, too.

Whiteboard: (none) => Mg

Ulrich Beckmann 2018-03-02 21:12:13 CET

Whiteboard: Mg => MGA6-64-TOO

Comment 5 Nicolas Lécureuil 2018-03-02 21:23:57 CET

Please open an upstream bugreport about this.

CC: (none) => mageia

Comment 6 Ulrich Beckmann 2018-03-04 11:49:37 CET

The Fedora bug report linked in comment #1 is now marked as CLOSED ERRATA. Unfortunately there is no explanation, why and what is the real solution. I tested now KMail in Fedora 27 and it works fine. The configuration items are greyed out, too. libkgapi is installed through dependencies.

Version numbers are
akonadi-1.13.0-107.fc27.x86_64
kmail-17.12.2-1.fc27.x86_64
libkgapi-17.12.2-1.fc27.x86_64

Comment 7 Ulrich Beckmann 2018-03-04 11:51:15 CET

I found additional info:

https://lists.opensuse.org/opensuse-factory/2017-05/msg00182.html

Quote Carlos E. R.
"Yes, gmail by default uses an auth method called oauth2. Normal mail
clients like daemons can not use this method, they need user
interaction with a web page. Thunderbird currently does support it
8since about a year or so). I don't know if kmail does or not.

If it doesn't, you have to log into the gmail control web page and
"allow login by less secure applications" or similar wording.

That's the trick we have to do to use, for instance, fetchmail."

https://lists.opensuse.org/opensuse-factory/2017-05/msg00189.html

Quote Luca Beltame
"Note that KMail 5.5, from Applications 17.04 (which should have landed
in TW, or will soon) supports OAuth2 for GMail natively now."


I checked now the Google configuration under
=> My Account => Sign in and Security => Allow less secure Apps is ON

That is why it worked before.

Ulrich

Comment 8 Ulrich Beckmann 2018-03-05 15:03:07 CET

There is a workaround: When you use the server imap.googlemail.com instead of imap.gmail.com, Google oauth is not needed.
You can configure manually e.g. SSL/TLS and Plain.

I had to invoke $ akonadictl vacuum.

Ulrich

Comment 9 Ulrich Beckmann 2018-04-04 20:42:55 CEST

As Google identification method works in Fedora, I won't write an upstream bug report as sugested. It is most probably fixed there, and the fix will appear in Mageia.

Closing the bug report as "works for me".

Ulrich

Resolution: (none) => WORKSFORME
Status: NEW => RESOLVED

Ulrich Beckmann 2018-05-15 21:29:24 CEST

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=23035