10 December 2013
You could always use IMAP or POP with your favorite email program to extract your data out of Gmail. For most, the primary interface to email is the Gmail website, which means launching a separate email app just to make sure your email is backed up. With this addition to Google's Takeout service you can easily download your email in a standard format without having to use a separate app.
You still have to remember to visit the takeout service regularly and manually download your data. You could create a recurring calendar event or maybe even an ifttt recipe to remind you.
A better approach is to automate your email backups because a solution that relies on the user taking regular action is brittle and likely to fail.
$ brew install getmail
$ getmail --version getmail 4.43.0
launchd is an open-source management framework for starting and stopping applications, processes, scripts, and daemons. It comes installed on all OS X systems. You interface with launchd using launchctl.
$ launchctl help usage: launchctl <subcommand> load Load configuration files and/or directories unload Unload configuration files and/or directories start Start specified job stop Stop specified job submit Submit a job from the command line ...
After getmail has been successfully installed you need to create a configuration file and store it in
[retriever] type = SimpleIMAPSSLRetriever server = imap.gmail.com username = firstname.lastname@example.org mailboxes = ("[Gmail]/All Mail",) [destination] type = MultiDestination destinations = ('[mboxrd-destination]', '[maildir-destination]') [mboxrd-destination] type = Mboxrd path = ~/Documents/backups/gmail/gmail-backup.mbox [maildir-destination] type = Maildir path = ~/Documents/backups/gmail/ [options] # print messages about each action (verbose = 2) # Other options: # 0 prints only warnings and errors # 1 prints messages about retrieving and deleting messages only verbose = 2 message_log = ~/.getmail/gmail.log # preserves your mail after backup delete = false # just get new mails read_all = false # do not alter messages delivered_to = false received = false
On OS X if you do not provide a
password in the configuration file getmail will check the Keychain first. If the password is not in the Keychain it will then ask with a prompt.
I recommend backing up your email in two formats: mbox and Maildir. In order for the Maildir option to work you need to manually create the path directory specified under
[maildir-destination] and add three sub-folders:
~/Documents/backups/gmail $ ls -t gmail-backup.mbox new tmp cur
By using two independent storage formats you have more flexibility if you ever need to retrieve a message from the backup.
Now test the configuration:
$ getmail -r /Users/matt/.getmail/getmail.gmail
Depending on how much email you have the first execution of this script can take several hours. If you need to pause or stop the backup just
CTRL+c the process. Once you are ready to continue you run getmail with the same configuration and it will resume where it left off.
Once you're happy with the configuration create a bash script and make it executable.
#!/usr/bin/env bash # Note: -q means fetch quietly so that this program is silent /usr/local/bin/getmail -q -r /Users/matt/.getmail/getmail.gmail
$ chmod +x backup-gmail.sh
Once you have getmail working you can automate it with cron or launchd. I recommend using launchd because unlike cron which skips jobs when the computer is asleep, launchd will start the job the next time the computer wakes up.
To create a launchd job create a configuration plist file and store it in
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>Label</key> <string>com.matthewmorey.backup-gmail</string> <key>LowPriorityIO</key> <true/> <key>Program</key> <string>/Users/matt/scripts/backup-gmail.sh</string> <key>ProgramArguments</key> <array> <string>/Users/matt/scripts/backup-gmail.sh</string> </array> <key>StartCalendarInterval</key> <dict> <key>Minute</key> <integer>0</integer> <key>Hour</key> <integer>3</integer> </dict> </dict> </plist>
To set the schedule of the job use the
StartCalendarInterval key, which follows the crontab scheduling convention. In this example the job is scheduled to run everyday at 3 AM.
To notify launchd of the new job you can use the
launchctl load command.
$ launchctl load ~/Library/LaunchAgents/
To verify the new job has been loaded execute the
launchctl list command and look for the
Label key of your configuration file.
$ launchctl list ... - 0 com.matthewmorey.backup-gmail ...
Finally, to test everything, execute the
launchctl start command.
$ launchctl start com.matthewmorey.backup-gmail
After it has run for a couple of days you should check the log
~/.getmail/gmail.log and verify that new messages are being successfully backed up everyday.
Now I just need to figure out how to receive a notification if the backup ever fails, which is bound to happen the next time I change my email password. Any suggestions?