Bug 27266 - KMail can no longer connect to gmail in Mageia 7: BACKPORT request for the fixed Mageia 8 version
Summary: KMail can no longer connect to gmail in Mageia 7: BACKPORT request for the fi...
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-09 19:12 CEST by Ole Reier Ulland
Modified: 2020-09-11 20:44 CEST (History)
6 users (show)

See Also:
Source RPM: kmail-19.04.0-1.mga7.src.rpm
CVE:
Status comment:


Attachments
pop.gmail.com (40.64 KB, image/png)
2020-09-11 17:05 CEST, Rolf Pedersen
Details
less secure apps (273.42 KB, image/png)
2020-09-11 17:10 CEST, Rolf Pedersen
Details

Description Ole Reier Ulland 2020-09-09 19:12:34 CEST
Description of problem:
KMail can not fetch gmail e-mails any more. The problem is described in these two links, 

https://www.reddit.com/r/kde/comments/gi5bol/kmailkontact_oauth_signin_with_gmail_enabled_again/

https://www.dvratil.cz/2019/08/kontact-google-integration-issue/

Aurélien Oudelet has written in the Mageia Discuss e-mail list that "Current Mageia 8 Cauldron version of KMail (5.15 - 20.08) is able to connect
via an application password."

May someone please backport this solution to Mageia 7 if possible, because to wait until Mageia 8 is available may be a very long wait.
Comment 1 Lewis Smith 2020-09-09 20:53:21 CEST
Thank you for reporting this; and giving the useful URLs. Re the following citation, can you say whether this blocks your existing account or just new ones?

According to the second ref above:
"Existing users should not be affected by this - if you already had Google Calendar or Gmail set up in Kontact, the sync should continue to work. It is only new accounts that cannot be created."
 and this useful adice:
"In case of Gmail the problem can mostly be worked around when setting up the IMAP account in KMail by selecting PLAIN authentication1 method in the Advanced tab and using your email and password. *You may need to enable Less Secure Applications in your Google account settings* in order to be able to log in with regular email address and password."

It is not just Kmail, Thunderbird has problems too:
"Having another go at this after discovering that Google was blocking 
Thunderbird ... Found a setting for  "Allow access for insecure apps" = tbird.  
Turned that on".

Have you tried that ?

CC: (none) => lewyssmith

Johnny A. Solbu 2020-09-09 22:30:03 CEST

CC: (none) => cooker

Comment 2 Ole Reier Ulland 2020-09-10 14:33:32 CEST
I have selected PLAIN authentication method, that made no difference. I have had to have the "Less Secure Application" enabled for all the years I have been using gmail for KMail to log in. This bug I am reporting became a reality when the "Less Secure Application" option was abolished by Google.

The problem is, as I understand it, that the KDE maintainer for KMail, did not take the necessary steps to comply with this change early enough. That is why the bug is only resolved in KMail for Mageia 8 as it is now. So my request is for it to be backported to Mageia 7, if that is at all possible. Because to be confined to gmail's webmail until I have Mageia 8 on my computer, is for me not a good thing at all.

Whether the maintainer for Thunderbird has resolved this for Mageia 7 or Mageia 8, I have no idea.
Comment 3 Lewis Smith 2020-09-10 21:22:05 CEST
Thank you for your additional explanations, which make your backport request look not just reasonable, but necessary.

Assigning to the KDE team, CC'ing neoclust & DavidG as maintainers of Kmail.

CC: lewyssmith => geiger.david68210, mageia
Summary: KMail can not connect to gmail => KMail can no longer connect to gmail in Mageia 7: BACKPORT request for the fixed Mageia 8 version
Assignee: bugsquad => kde

Comment 4 Arne Spiegelhauer 2020-09-10 21:58:56 CEST
To my knowledge no code changes are involved in solving this issue.
The problem was with providing timely information to Google in order to get akonadi certified as a secure application.
I am currently using kmail with gmail account and OAUTH2 authentication on Mageia 7.

Only problem has been this less severe bug:

https://bugs.kde.org/show_bug.cgi?id=421664

CC: (none) => gm2.asp

Comment 5 Ole Reier Ulland 2020-09-11 16:34:52 CEST
The error message is,

QUOTE

Unable to login to the server pop.gmail.com.
Could not login to pop.gmail.com. The password may be wrong.
The server said: "[AUTH] Username and password not accepted."

END QUOTE

I know that the username and password are correct because I use them to log in to webmail for gmail.
What can I do to get KMail to log in and download my gmail e-mails?
Comment 6 Aurelien Oudelet 2020-09-11 16:41:26 CEST
I don't think gmailis available with POP3 server.
I think correct access is with imap protocol.

CC: (none) => ouaurelien

Comment 7 Rolf Pedersen 2020-09-11 17:05:30 CEST
Created attachment 11876 [details]
pop.gmail.com

FWIW, I access gmail pop with the shown settings.  It's in seamonkey and set up about 20 years ago, so FWIW.

CC: (none) => rolfpedersen

Comment 8 Rolf Pedersen 2020-09-11 17:10:43 CEST
Created attachment 11877 [details]
less secure apps

Again, FWIW, my understanding of "the "Less Secure Application" option" is shown at the url in attached screenie.
Comment 9 Ole Reier Ulland 2020-09-11 20:44:08 CEST
This is a little embarrassing. I have been lead to believe, from Mageia Discuss, different blogs and what not, that the "Less Secure Application" option had been removed, so I must have not looked hard enough for it. It must have been turned off automatically since I had not fetched e-mails with KMail from gmail for a month. When I turned it back on again KMail received e-mails from gmail. Not only that I got all my e-mails from the last month, but I also got a copy of all the e-mails I have sent with the gmail server for about the last three years. I have now 813 unread e-mails in my inbox that I have to go through. But of course thank you very much Rolf Pedersen, I breath easier now, I just have a job to do.

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


Note You need to log in before you can comment on or make changes to this bug.