3 ms·
I pay for a second inexpensive mailbox at Mailfence and sync the contents of the Fastmail account to a subfolder of the Mailfence account. There is rate-limiti
by spinax 5y ago
I pay for a second inexpensive mailbox at Mailfence and sync the contents of the Fastmail account to a subfolder of the Mailfence account. There is rate-limiting involved, so my config is dialed down on "pipelinedepth" to ensure I don't hit that problem (you can easily overrun the Mailfence side pushing too much too fast). The cron runs via a unique user account on a cloud server every 4 hours using unique passwords (see below).
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.
- deeblering4 5y agoNice idea to copy between imap accounts, I might set that up in addition to my local backups. How do you like mailfence overall?
- spinax 5y agoIt seems just fine? As it's my secondary account it's mostly SMTP idle so I can't give an honest opinion about delivery (like emails from your bank) but it seems to be doing very well as a service. Like Fastmail, they have a detailed domain setup wizard to ensure all your DNS for SPF/DKIM/dmarc etc. is all properly configured for best results. I have no complaints for what I use it for, really. I do wish that I had finer grained app password control like Fastmail but it's not a deal killer. 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.
- gnull 5y agoFor anyone reading mbsync(1) and getting confused now: they have renamed Master-Slave into Far-Near in the latest versions.
- maest 5y agoWhich one is which? Is Master = Far and Slave = Near? I'd lean towards the opposite but I can't tell for certain.
- spinax 5y agoIt looks like they did this in 1.4.0 released in February 2021, the online man page on the project website has not been updated for this new code. If you read the man page source [1], the word replacement seems to be that Far==Master and Near==Slave - the surrounding text is identical. [1] https://sourceforge.net/p/isync/isync/ci/master/tree/src/mbsync.1#l522 https://sourceforge.net/p/isync/isync/ci/master/tree/src/mbs...
- _Anima_ 5y agoI also use fastmail and I copied your config, with the only difference I'm saving in a local folder. 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 https://github.com/JakeWharton/docker-mbsync
- spinax 5y agoI am using Debian isync-1.3.0-2 and it's working - that Dockerfile shows it's using 1.3.3 and I spot a possible fix in 1.3.4 which could be related (or not, who knows). Your running mysync version might be different depending on the last time you rebuilt that running docker instance, the Dockerfile doesn't seem to pin it to a specific release version. 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/c8b73acad2a3c698d82ab52d239fd86b48c50c8e/ https://sourceforge.net/p/isync/isync/ci/c8b73acad2a3c698d82... [2] https://nl.alpinelinux.org/alpine/edge/community/x86_64/ https://nl.alpinelinux.org/alpine/edge/community/x86_64/