HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
GAM-team
got-your-back
Python2016–2025
GAM-team / got-your-back

got-your-back

Got Your Back (GYB) is a command line tool for backing up your Gmail messages to your computer using Gmail's API over HTTPS.

24Distinct people
32Mentions
1Explicit recommenders
3.1KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Got Your Back (GYB) is a command line tool for backing up your Gmail messages to your computer using Gmail's API over HTTPS.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

I have not tried Gmvault, but I have tried two other backup solutions. I recommend [GYB]: - I have successfully migrated a 10+ GB gmail account to another account. - There were…

Leftium used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 1:56:48 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year32 dated mentions

Observed mentions: 2016-11-18 13:31:18 UTC to 2025-12-31 15:09:43 UTC.

02462016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 7 mentions; 0 submissions, 7 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 6 mentions; 0 submissions, 6 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC202
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC404
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC707
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC606
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC404
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303

What Hacker News says

6 sources
I did a bunch of research on this earlier this year. I really do enjoy Gmail, even if it is technically a cloud service. So, I split the difference on this one. I use a Gmail account as "primary", but I still have my own domain for email inboxes. The best option I found is to have my own domain (e.g. at Hover) and then have the MX servers managed by Cloudflare's new product, email routing. They also handle SPF, DKIM, and DMARC. That's described here[1] and here[2]. What's nice about this setup: you have your own domain; you can setup custom forwarding rules; all email flows to a single GMail inbox. You can also still send email "from" those domains if you use the Gmail SMTP server[3]. So then your only concern is backup and email message export. For this, I setup automation with a script called got-your-back (gyb)[4]; it's a nice Python s
Read the rest
cript with incremental backup that can archive your Gmail account and restore it to another account. I set up a second Gmail account to test this restore functionality. [1]: https://blog.cloudflare.com/introducing-email-routing/ [2]: https://www.cloudflare.com/products/email-routing/ [3]: https://jhart99.com/cloudflare-outbound-email/#outbound-emai... [4]: https://github.com/GAM-team/got-your-back
In Ask HN: Do You Host Your Own Email?
Notice that Google Takeout is broken with regards to non-UTF8 email encodings (for some of you who archive old emails). I noticed it when coding a small tool https://github.com/karteum/gmvaultdb to (among other things) import the mbox from Takeout into an sqlite DB : Google performs some encoding conversions that permanently break all non-ascii characters in non-UTF8 emails (they are all replaced by 0xEFBFBD). In order to archive old emails, I had to use mbsync with IMAP (gmvault does not work anymore with Python 3, and I didn't try yet https://github.com/GAM-team/got-your-back ).
In Google terminated our Developer Account, says it is “associated”

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.