GMVault disallowed for GMail/Google

[Craig Jones]

[Sorry, realized I left some links in that probably didn't need to be there.]

I have been using GMVault for a while and really like it. Each night I run this automatically:

/usr/bin/gmvault sync -t quick -c no -d <directory> <emailaddress>

Just now this came through my email:

Although you don’t need to take any action, we wanted to let you know that the following third-party apps will no longer be able to access some data in your Google Account, including your Gmail content. This change will go into effect starting March 31, 2019.

Gmvault

We are making this change as part of ongoing efforts to make sure your data is protected and private. These apps haven’t yet complied with our updated data privacy requirements announced on October 8, 2018.

You can always view, manage and remove apps you’ve given access to your account by visiting your Google Account.

Obviously, this probably isn't specifically related to GMVault, but it does affect my method of backup. Any ideas what I can do still be able to use GMVault?

[David AuBuchon]

I got the same email. Looksl ike GmVault will be made obsolete without some kind of change?

[djlu...@gmail.com]

Check out this GitHub discussion to see what is being done to try and avoid being locked-out by Google:

https://github.com/gaubert/gmvault/issues/335

[David AuBuchon]

Awesome. The steps outlined in that thread (https://github.com/gaubert/gmvault/issues/335) by gboudreau work for me. Repasting them here:

Procedure to get yourself a new client ID & secret:

• Start here: https://console.developers.google.com
• Accept conditions, if you never used the Google API Console (after reading all the terms and conditions, evidently)
• Create a new project (at the top); of choose one you already have, if that makes sense
• Go to https://console.developers.google.com/apis ; click + ENABLED APIS AND SERVICES at the top
• Search for Gmail; select it; click Enable
• Go to https://console.developers.google.com/apis/credentials; choose OAuth Consent Screen tab
• Fill name (enter anything), click Add scope
• Select the checkbox on the https://mail.google.com/ line; click Add
• Click Save
• Click Create Credentials; choose OAuth client ID
• Application Type: Other; give it a name (anything; I suggest gmvault, since this credential will be used by gmvault)
• Click Create

You will get a client ID and secret. Those two values needs to replace the existing ones in $HOME/.gmvault/gmvault_defaults.conf : gmvault_client_id=... and gmvault_client_secret=... Also, you might need to change the value of conf_version in that file; make sure it is conf_version=1.9 and NOT conf_version=1.9.1, otherwise, gmvault will overwrite it every time it runs.

Finally, make sure you delete the previously obtained OAuth2 token; running gmvault as you normally do will show you where the token file, that you need to delete, is. Eg:

Get OAuth2 credential from /home/gb/.gmvault/y...@gmail.com.oauth2.

[Francis Deweirdt]

Great stuff, it worked like a charm. While Mr. Google is reviewing my credential requests I have 100 logins allowed.

Thanks for the solution , I like to keep a local backup of all email just in case and gmvault gets the job done. 

Get OAuth2 credential from /home/gb/.gmvault/you@gmail.com.oauth2.

[Pierre Thonne]

Very good explanation. Many thanks for this.

Get OAuth2 credential from /home/gb/.gmvault/you@gmail.com.oauth2.