This release is a pre-release and may not be stable for production use.
# Encrypted Gmail Backup
Place your config in in ~/.encrypted_gmail_backup
Sample Config:
[gmail] username = stephen.holiday@gmail.com password = changeme
[gpg] keyid = 76AA7B2CF3FD360E binary = gpg
[backup] path = /backup/gmail/ metafile = gmailmeta.txt archive = messages.tar
[gmail] username = NONE password = NONE server = imap.gmail.com folder = [Gmail]/All Mail
[gpg] # The recipient to encrypt to. keyid = 76AA7B2CF3FD360E binary = gpg home = ~/.gnupg encoding = utf-8
[backup] # Target directory for the backup. Must exist and end in a trailing slash. path = /tmp/
# Name of the target archive. # Appended to the backup path. archive = messages.tar
# Stores the ID of the last fetched message. metafile = gmailmeta.txt
# If your backup directory is on mounted device, # the script can check if the target directory exists first and fail gracefully. onexternal = no
# Ensure only one instance of the script per username. use_pid = yes pid_prefix = /tmp/encrypted_gmail_backup
Be sure to chmod 600 ~/.encrypted_gmail_backup so that other users can’t read your password.
I have MacGPG installed on my system, so I changed binary to:
binary = /usr/local/MacGPG2/bin/gpg2
Then run gmail-backup and it will start to fetch your mail!
Based on Andrew Jennings’ [gmail-backup](https://github.com/abjennings/gmail-backup)
1 maintainer
Metadata
1 maintainer
Release files for EncryptedGmailBackup 0.0.4beta1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| EncryptedGmailBackup-0.0.4beta1.tar.gz | 4.6 kB | Without provenance | Details for EncryptedGmailBackup-0.0.4beta1.tar.gz |
Release files / EncryptedGmailBackup-0.0.4beta1.tar.gz
| Download URL | EncryptedGmailBackup-0.0.4beta1.tar.gz |
|---|---|
| Size | 4.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b4c9777ddf8dc6f0de2a90791a39e0b8c9d9be96fb8330552274cc53ffb5924a
|
|
BLAKE2b-256 checksum How to use checksums |
7a4cb17d5ae4ea6f1cd2751043ad0c8063dea1e190fa9cef433c120a3d60690f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for EncryptedGmailBackup 0.0.4beta1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
