https://bugs.kde.org/show_bug.cgi?id=404990
--- Comment #98 from Alexander Potashev <aspotas...@gmail.com> --- I have a idea for workaround. For the context, read carefully: https://developers.google.com/gmail/api/auth/about-auth It mentions verification of *public* applications. Google permits usage of Google APIs without app verification unless you application is published. For example, I use my own little script for automated processing of some specific types of emails that I receive daily on my Gmail address - Google doesn't care about verification in this case because it's my personal app. So, what if we let KMail users create their "applications" at Google API Console [1] and force KMail to use the new app token instead of the KMail's official token? This sounds like an abuse Google APIs at first, but we can view this as if the user forked KMail and created a new app token for it since their "forked" version of KMail is now personal application. To make this workaround easy to employ, we need to un-hardcode the Akonadi's Google app ID and put it in a configuration file. At the moment it is hardcoded as https://github.com/KDE/kdepim-runtime/search?q=554041944266 - in these two files: - resources/google/common/googlesettings.cpp - resources/imap/gmailpasswordrequester.cpp [1] https://console.developers.google.com/ -- You are receiving this mail because: You are the assignee for the bug.