The mbsync command inside mailsync has to be modified in order to read
the isync config file in .config/isync/mbsyncrc.
If no file is found, the config is read in the default location.
* changed ping address to a more friendly location
`1.1.1.1` is not a friendly address for users from some parts of the world (e.g., China). Changed to `example.org` which should be more friendly to access.
* changed internet check by fallback
This is probably better since for most people it does the same thing and the first back up is Cloudfare's other DNS address which surprisingly can be accessed in more places (e.g., China) now. And changed the finall fallback as example.org.
I believe this addresses issue #456 where if you add a protonmail account you get an error. This is caused by prematurely returning from the case statement that queries whether you have a protonmail account or not.
Co-authored-by: rjl6789 <rlives6789@gmail.com>
I think a recent change tried to send output from crontab to dev/null to avoid messages appearing a) when setting the crontab, b) whenever mailsync is run. However the redirection was for the string concatenation meaning a null string was piped to cron obliterating the crontab (thank goodness for backups). I have put the redirection in the correct location (similar to a few lines above when removing the mailsync line). I have also redirected all output of the mailsync (both errors and normal messages) to dev null.
Co-authored-by: rjl6789 <rlives6789@gmail.com>
If no options are passed but the accounts are specified then the blank opt flag causes a (harmless) error message from mbsync about an empy channel.
Co-authored-by: rjl6789 <rlives6789@gmail.com>