Ended up going with #isync, primarily because I haven't tried it before.
I had good experiences with #OfflineIMAP in the past, but the python2->python3 migration hit me hard, because OfflineIMAP became unusable for a rather long period of time because of it. Such a thing is unlikely to happen in the foreseeable future, but one such experience ended up being enough to sway me to the alternative.
As part of reorganizing my stuff, I'll be reorganizing how I deal with e-mail. In the past, I've used #OfflineIMAP to sync, and #notmuch to tag, organize, and otherwise deal with it. I stopped doing that when Debian started transitioning to Python3 and it broke.
Now it has been ported to py3, but since I'm redoing this whole thing, I'm looking for other options too.
I don't need much: download mail, sync read status back, run notmuch after.
Any other options other than OfflineIMAP & #isync?
Do any of y'all use #isync/#mbsync to pull down emails via IMAP?
I have it *mostly* working. But I'd like it to pull down my emails automatically, in the background.
That's easy enough to set up…*except* that I have the password to my inbox secured with a yubikey. So, right now, there's no way to pull new emails without pressing the yubikey.
Is there a good way to keep that password in memory without sacrificing *too* much security? (I.e., I don't want it in plaintext)
Do any of y'all use #isync/#mbsync to pull down emails via IMAP?
I have it *mostly* working. But I'd like it to pull down my emails automatically, in the background.
That's easy enough to set up…*except* that I have the password to my inbox secured with a yubikey. So, right now, there's no way to pull new emails without pressing the yubikey.
Is there a good way to keep that password in memory without sacrificing *too* much security? (I.e., I don't want it in plaintext)
@LovisIX@pleroma.tamanoir.foucry.net Et sinon, il semble que ça commitait encore sur #isync récemment, en tout cas en septembre dernier (j'avoue que je ne m'étais jamais posé la question).
https://sourceforge.net/p/isync/isync/ci/master/tree/
@LovisIX@pleroma.tamanoir.foucry.net Le problème d'#offlineimap, en version courte, c'est une librairie qui ne sera probablement jamais mise à jour vers #Python3.
https://mstdn.fr/@whilelm/103004304852565309
Je ne sais pas à quel point le paquet #isync est maintenu, mais malgré ça #mbsync a toujours été plus fiable et moins consommateur qu'offlineimap (peut-être plus rapide aussi, mais je ne suis plus sûr de mes souvenirs).
#offlineimap #python3 #isync #mbsync