diff --git a/Makefile b/Makefile index d3ee7520..9be8dc7f 100644 --- a/Makefile +++ b/Makefile @@ -9,9 +9,12 @@ ifeq ($(origin .RECIPEPREFIX), undefined) endif .RECIPEPREFIX = > -## server: run server locally on port 51313 +build: +> hugo + +## server: run server locally on port 1313 and open in a browser server: -> hugo server -D -p 51313 +> xdg-open http://localhost:1313 && hugo server ## help: Print this help message help: diff --git a/content/post/backing-up-gmail-with-synology.md b/content/post/backing-up-gmail-with-synology.md new file mode 100644 index 00000000..d845925b --- /dev/null +++ b/content/post/backing-up-gmail-with-synology.md @@ -0,0 +1,74 @@ +--- +title: "Backing Up Gmail With Synology" +date: 2022-03-13T18:49:10-04:00 +lastmod: 2022-03-13T18:49:10-04:00 +draft: false +keywords: [] +description: "" +tags: ['degoogle', 'synology', 'gmail', 'backup', 'ransomware'] +categories: [] +author: "" + +# You can also close(false) or open(true) something for this content. +# P.S. comment can only be closed +comment: false +toc: false +autoCollapseToc: false +postMetaInFooter: false +hiddenFromHomePage: false +# You can also define another contentCopyright. e.g. contentCopyright: "This is another copyright." +contentCopyright: false +reward: false +mathjax: false +mathjaxEnableSingleDollar: false + +flowchartDiagrams: + enable: false + options: "" + +sequenceDiagrams: + enable: false + options: "" + +--- + + + + I've used gmail since the beta launched touting a whopping 1GB of storage. I thought this was a massive leap in email technology at the time. I was lucky enough to get an invite fairly quickly. Not suprisingly, I have many years of emails, attachments, and photos. I certainly do not want to lose the content of many of these emails. Despite the redundancy of the data that Google secures, I still feel better retaining a copy of this data on my own physical machines. + +The thought of completely de-googling has crossed my mind on occassion. The convenience coupled with my admiration for their engineering has prevented me from doing so thus far. Though, I may end up doing so at some point in the future. + +## Synology MailPlus Server + +Synology products are reasonably priced for what you get (essentially a cloud-in-a-box) and there is very little maintenance required. I've recently been in interested in syncing and snapshotting my personal data. I've setup [Synology's Cloud Sync](https://www.synology.com/en-ca/dsm/feature/cloud_sync) and keep copies of most of my cloud data. + + I've used tools such as [gmvault](http://www.gmvault.org) with success in the past. Setting this up on a cron seems like a viable option. However, I don't really need a lot of the features it offers and do not plan to restore this data to another account. + +Synology's MailPlus seems to be a good candidate for backing up this data. By enabling POP3 fetching, it's possible to fetch all existing emails, as well as periodically fetch all new emails. If a disaster ever did occur, having these emails would be beneficial, as they are an extension of my memory bank. + +Installing MailPlus can be done from the Package Center: + +![image](/images/backing-up-gmail-with-synology/install-mailplus-server.png) + +Next, I went into **Synology MailPlus Server** and on the left, clicked on **Account** and ensured my user was marked as active. + +Afterwords, I followed [these instructions](https://kb.synology.com/en-in/DSM/tutorial/How_should_I_receive_external_email_messages_via_MailPlus) in order to start backing up emails. + +When entering the POP3 credentials, I created an [app password](https://myaccount.google.com/apppasswords) solely for authenticating to POP3 from the Synology device. This is required because I have 2-Step verification enabled on my account. There doesn't seem to be a more secure way to access POP3 at the moment. It does seem like app password access is limited in scope (when MFA is enabled). These app passwords can't be used to login to the main Google account. + +I made sure to set the `Fetch Range` to `All` in order to get all emails from the beginning of time. + +After this, mail started coming in. + +![image](/images/backing-up-gmail-with-synology/mail-plus-incoming-mail.png) + + After fetching 19 years worth of emails, I tried searching for some emails. It only took a few seconds to search through ~50K emails, which is a relief if I ever did have to search for something important. + +## Securing Synology + +Since Synology devices are not hermetically sealed, it's best to secure them by [enabling MFA](https://kb.synology.com/en-us/DSM/tutorial/How_to_add_extra_security_to_your_Synology_NAS#x_anchor_id8) to help prevent being the [victim of ransomware](https://www.bleepingcomputer.com/news/security/qlocker-ransomware-returns-to-target-qnap-nas-devices-worldwide/). It is also wise to backup your system settings and volumes to the cloud using a tool such as [Hyper Backup](https://www.synology.com/en-ca/dsm/feature/hyper_backup). +Encrypting your shared volumes should also be done, since unfortunately [DSM does not support full disk encryption](https://community.synology.com/enu/forum/12/post/144665). + +## Summary + +Having backups of various forms of cloud data is a good investment, especially in these [uncertain times](https://en.wikipedia.org/wiki/2022_Ukraine_cyberattacks). I certainly feel more at ease for having backed up my emails. diff --git a/public/404.html b/public/404.html index bd39559b..4d8165e2 100644 --- a/public/404.html +++ b/public/404.html @@ -9,7 +9,7 @@ - + @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/about/index.html b/public/about/index.html index b25d2bb4..918a49c2 100644 --- a/public/about/index.html +++ b/public/about/index.html @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/authors/index.html b/public/authors/index.html index 3bd52468..a59e8803 100644 --- a/public/authors/index.html +++ b/public/authors/index.html @@ -9,7 +9,7 @@ - + @@ -75,12 +75,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -109,8 +115,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/blog/2020/03/16/appgate-sdp-on-arch-linux/index.html b/public/blog/2020/03/16/appgate-sdp-on-arch-linux/index.html index 927b29ab..40bff6ec 100644 --- a/public/blog/2020/03/16/appgate-sdp-on-arch-linux/index.html +++ b/public/blog/2020/03/16/appgate-sdp-on-arch-linux/index.html @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/blog/2021/09/06/what-to-do-with-a-homelab/index.html b/public/blog/2021/09/06/what-to-do-with-a-homelab/index.html index e7feffdf..f43b6f5b 100644 --- a/public/blog/2021/09/06/what-to-do-with-a-homelab/index.html +++ b/public/blog/2021/09/06/what-to-do-with-a-homelab/index.html @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/blog/2021/09/08/why-i-threw-out-my-dotfiles/index.html b/public/blog/2021/09/08/why-i-threw-out-my-dotfiles/index.html index fa88a8c4..46a3213d 100644 --- a/public/blog/2021/09/08/why-i-threw-out-my-dotfiles/index.html +++ b/public/blog/2021/09/08/why-i-threw-out-my-dotfiles/index.html @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/blog/2021/09/17/automatically-rotating-aws-access-keys/index.html b/public/blog/2021/09/17/automatically-rotating-aws-access-keys/index.html index f3e791c2..ce227ccf 100644 --- a/public/blog/2021/09/17/automatically-rotating-aws-access-keys/index.html +++ b/public/blog/2021/09/17/automatically-rotating-aws-access-keys/index.html @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/blog/2021/10/11/replacing-docker-with-podman-on-macos-and-linux/index.html b/public/blog/2021/10/11/replacing-docker-with-podman-on-macos-and-linux/index.html index a169bfa9..ecb3b575 100644 --- a/public/blog/2021/10/11/replacing-docker-with-podman-on-macos-and-linux/index.html +++ b/public/blog/2021/10/11/replacing-docker-with-podman-on-macos-and-linux/index.html @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • diff --git a/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html b/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html index a7a0905e..2e0e102a 100644 --- a/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html +++ b/public/blog/2021/11/14/running-k3s-in-lxc-on-proxmox/index.html @@ -73,12 +73,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -107,8 +113,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • @@ -404,6 +414,21 @@ k3sup install --ip $CONTAINER_IP --user root --k Previous Previous post: Replacing docker with podman on macOS (and Linux) +
    + + Next post: Backing Up Gmail With Synology +
    diff --git a/public/blog/2022/03/13/backing-up-gmail-with-synology/index.html b/public/blog/2022/03/13/backing-up-gmail-with-synology/index.html new file mode 100644 index 00000000..1853bde5 --- /dev/null +++ b/public/blog/2022/03/13/backing-up-gmail-with-synology/index.html @@ -0,0 +1,393 @@ + + + + + + + + + + + + + + + + Backing Up Gmail With Synology • davegallant + + + + + + + + + + + + + + +
    +
    +
    + + + +
    + + +
    +
    +
    +
    +

    Backing Up Gmail With Synology

    + + +
    + + + +
    +
    + + + + +
    +

    I’ve used gmail since the beta launched touting a whopping 1GB of storage. I thought this was a massive leap in email technology at the time. I was lucky enough to get an invite fairly quickly. Not suprisingly, I have many years of emails, attachments, and photos. I certainly do not want to lose the content of many of these emails. Despite the redundancy of the data that Google secures, I still feel better retaining a copy of this data on my own physical machines.

    +

    The thought of completely de-googling has crossed my mind on occassion. The convenience coupled with my admiration for their engineering has prevented me from doing so thus far. Though, I may end up doing so at some point in the future.

    +

    Synology MailPlus Server

    +

    Synology products are reasonably priced for what you get (essentially a cloud-in-a-box) and there is very little maintenance required. I’ve recently been in interested in syncing and snapshotting my personal data. I’ve setup Synology’s Cloud Sync and keep copies of most of my cloud data.

    +

    I’ve used tools such as gmvault with success in the past. Setting this up on a cron seems like a viable option. However, I don’t really need a lot of the features it offers and do not plan to restore this data to another account.

    +

    Synology’s MailPlus seems to be a good candidate for backing up this data. By enabling POP3 fetching, it’s possible to fetch all existing emails, as well as periodically fetch all new emails. If a disaster ever did occur, having these emails would be beneficial, as they are an extension of my memory bank.

    +

    Installing MailPlus can be done from the Package Center:

    +

    image

    +

    Next, I went into Synology MailPlus Server and on the left, clicked on Account and ensured my user was marked as active.

    +

    Afterwords, I followed these instructions in order to start backing up emails.

    +

    When entering the POP3 credentials, I created an app password solely for authenticating to POP3 from the Synology device. This is required because I have 2-Step verification enabled on my account. There doesn’t seem to be a more secure way to access POP3 at the moment. It does seem like app password access is limited in scope (when MFA is enabled). These app passwords can’t be used to login to the main Google account.

    +

    I made sure to set the Fetch Range to All in order to get all emails from the beginning of time.

    +

    After this, mail started coming in.

    +

    image

    +

    After fetching 19 years worth of emails, I tried searching for some emails. It only took a few seconds to search through ~50K emails, which is a relief if I ever did have to search for something important.

    +

    Securing Synology

    +

    Since Synology devices are not hermetically sealed, it’s best to secure them by enabling MFA to help prevent being the victim of ransomware. It is also wise to backup your system settings and volumes to the cloud using a tool such as Hyper Backup. +Encrypting your shared volumes should also be done, since unfortunately DSM does not support full disk encryption.

    +

    Summary

    +

    Having backups of various forms of cloud data is a good investment, especially in these uncertain times. I certainly feel more at ease for having backed up my emails.

    +
    + + + + + +
    + + + + +
    +
    +
    +
    +
    +
    + +
    + +
    +
    + +
    +
    + +
    +
    + + + + + + + diff --git a/public/images/backing-up-gmail-with-synology/install-mailplus-server.png b/public/images/backing-up-gmail-with-synology/install-mailplus-server.png new file mode 100644 index 00000000..5aa08863 Binary files /dev/null and b/public/images/backing-up-gmail-with-synology/install-mailplus-server.png differ diff --git a/public/images/backing-up-gmail-with-synology/mail-plus-incoming-mail.png b/public/images/backing-up-gmail-with-synology/mail-plus-incoming-mail.png new file mode 100644 index 00000000..ccf992ee Binary files /dev/null and b/public/images/backing-up-gmail-with-synology/mail-plus-incoming-mail.png differ diff --git a/public/index.html b/public/index.html index cc895c87..02d7e637 100644 --- a/public/index.html +++ b/public/index.html @@ -9,7 +9,7 @@ - + @@ -75,12 +75,18 @@ if (!doNotTrack) { aws
  • aws-vault +
  • + backup
  • containers +
  • + degoogle
  • docker
  • dotfiles +
  • + gmail
  • grafana
  • @@ -109,8 +115,12 @@ if (!doNotTrack) { proxmox
  • python +
  • + ransomware
  • security +
  • + synology
  • tailscale
  • @@ -243,6 +253,22 @@ if (!doNotTrack) {