With this it's easy to pick up and move to a different provider or recover from outages, account closure, etc.
If you couple this with your own domain your email will be very portable.
With this it's easy to pick up and move to a different provider or recover from outages, account closure, etc.
If you couple this with your own domain your email will be very portable.
cron runner's ~/.mbsyncrc
# Source
IMAPAccount imap-src-account
Host imap.fastmail.com
Port 993
User <user@domain.com>
PassCmd "cat <redacted>/.secure/psrc"
SSLType IMAPS
SystemCertificates yes
PipeLineDepth 1
# Dest
IMAPAccount imap-dest-account
Host imap.mailfence.com
Port 993
User <username>
PassCmd "cat <redacted>/.secure/pdst"
SSLType IMAPS
SystemCertificates yes
PipeLineDepth 1
# Source map
IMAPStore imap-src
Account imap-src-account
# Dest map
IMAPStore imap-dest
Account imap-dest-account
# Transfer options
Channel mailsync
Master :imap-src:
Slave :imap-dest:SubFolder/
Sync Pull
Create Slave
Remove Slave
Patterns *
CopyArrivalDate yes
Note: use the Fastmail option to set up a READ ONLY IMAP user password! (it's a really cool feature of Fastmail that many others do not support) Mailfence also has per-service passwords, set one up for IMAP as well. Do not use your main login passwords if you can avoid it - $0.02.How do you like mailfence overall?
I went with Fastmail as my primary due to the enhanced feature set and crazily enough - the Notes and Files feature in their mobile app. I can take a picture, toss it into that folder and get it on my desktop quicker than finding a USB cable or running a foldersync - the Notes are similar, I replaced Google Keep by just using the Fastmail Notes functionality.
I'm getting this error for each email: IMAP error: unable to parse INTERNALDATE format
Do you also get that? Is this a problem?
I use this Docker image: https://github.com/JakeWharton/docker-mbsync
The Dockerfile is using Alpine Linux and the repos that it points to have already updated to isync-1.4.2 two days ago[2] - in general, I will make a guess your version of mbsync/isync has a bug? You're sort of using some random version, basically.
[1] https://sourceforge.net/p/isync/isync/ci/c8b73acad2a3c698d82...
[2] https://nl.alpinelinux.org/alpine/edge/community/x86_64/
Is Master = Far and Slave = Near? I'd lean towards the opposite but I can't tell for certain.
[1] https://sourceforge.net/p/isync/isync/ci/master/tree/src/mbs...
What's the point of using mbsync?
And then if something goes wrong I make a copy of my backup, and invert the configuration to sync local -> imap.
The service is to send & receive email. But the storage capacity was less and the service only has a imap & smtp address and no webmail. Basically the service focuses on ensuring the emails are sent & received. The person has a webserver hosted at home that copies the emails from that server and incase of sending email, sends via that server. Then all the content of the home server is backed up at some off-site backup service.
Any idea which is the services being used and how would such a system be rated? It sounds like you are doing something similiar.
I mean the idea is great but wouldnt you need a backup mailbox provider allowing you to restore daily snapshots?
I'm not sure what happens if the remote emails are overwritten though.
* https://github.com/samhh/dotfiles/blob/master/home/.config/o...