Mastodawn

Et, hop !

La gestion de l'ensemble des seize boîtes mails auxquelles j'ai accès est enfin complète.

Tout est harmonisé, synchronisé, indexé et archivé régulièrement… Le tout est fait avec un petit script maison, mbsync, git, notmuch, et des services systemd.

C'est tout beau et tout propre.

Et comme ça je peux faire de la place côté serveurs, tout en conservant les vieux messages dans un coin, au cas où, l'esprit tranquille. 😎

#git #email #mbsync #isync #notmuch

Gold Ayan May 10

This week #kanchilug meet we discussed about syncing mail to local system using #mbsync (from #isync package). #archwiki is the one we relayed on and it worked flawlessly

https://wiki.archlinux.org/title/Isync

isync - ArchWiki

AliveDevil Aug 30, 2025

Migrate #EMail from server A, to server B.
- #Thunderbird and drag them.
- #isync #mbsync, and read docs
- #imapsync, setup an Arch VM, because it's packaged there (as opposed to Debian/Ubuntu).

#isync, mon amour.

I tried #isync + #gitAnnex + #notmuch which is cool, but weirdly only one-way and only really works when run from a single machine as it's stateful. I can't move around mails and make folders etc and git annex drop mails and keep others to decide what's on the server and what's not. It gets messy. Feels like it's a very nice solution to grab mail from the server and then manage it only locally and sync it around with git annex, but not if you want your mails e.g. on your phone client as well.

Helge Heß Nov 4, 2024

"Ready to synchronize T68i". #brushedmetal #iSync

Show thread

Parleur Oct 4, 2024

@alexconquer C'est un des outils du paquet #isync.

https://isync.sourceforge.io/

Celui-ci en particulier permet la synchronisation de comptes IMAP, en ligne de commande. #CLI

isync: free IMAP and MailDir mailbox synchronizer

Jarkko Sakkinen Aug 6, 2024

I created a ticket for #isync addressing the #Fedora 40 issue: https://sourceforge.net/p/isync/patches/19/

Isync / Patches / #19 Fix Fedora 40 crash caused by LTO

Jarkko Sakkinen Aug 5, 2024

I started my own fork of #isync (or #mbsync)

https://codeberg.org/jarkko/isync

It has now couple of commits:

❯ git log --oneline -2
8ea62c9 (HEAD -> main, origin/main) fix: compile with -fno-lto
f5782aa refactor: open code FORCEASYNC far and near parameters

The first is the fix for crash in #Fedora. The second open codes FORCEASYNC:

diff --git a/src/common.h b/src/common.h
index 940e74d..22bd827 100644
--- a/src/common.hb
+++ b/src/common.h
@@ -120,7 +120,8 @@ BIT_ENUM(
        ZERODELAY,
        KEEPJOURNAL,
        FORCEJOURNAL,
-       FORCEASYNC(2),
+       FORCEASYNC_F,
+       FORCEASYNC_N,
        FAKEEXPUNGE,
        FAKEDUMBSTORE,
 )

I plan to do this for all of those, as it allows to cut some slack out from bit_enum_get.pl. That will lead to a roadmap where eventually the whole ugly script can be rendered out replaced with BIT_UL macro from kernel (msync is GPL 2.0 licensed).

There is also a #zig branch but before build can be defined properly the C codebase first needs to be made sound in terms of the build. Then it is relatively easy task to repeal and replace main.c with main.zig.

#email

isync

Codeberg.org

Jarkko Sakkinen Aug 1, 2024

(gdb) print boxes
$1 = {0x5555556c4540, <optimized out>}

I noticed this so I tried:

diff --git a/src/main_sync.c b/src/main_sync.c
index 226e324..afb23ca 100644
--- a/src/main_sync.c
+++ b/src/main_sync.c
@@ -623,6 +623,7 @@ sync_opened( main_vars_t *mvars, int t )
if (!mvars->chanptr->boxlist && mvars->chan->patterns) {
mvars->chanptr->boxlist = 2;
char **boxes[2];
+ __asm__ __volatile__("" :: "m" (boxes));
boxes[F] = filter_boxes( mvars->boxes[F], mvars->chan->boxes[F], mvars->chan->patterns );
boxes[N] = filter_boxes( mvars->boxes[N], mvars->chan->boxes[N], mvars->chan->patterns );
box_ent_t **mboxapp = &mvars->chanptr->boxes;

That literally fixed the bug! I.e. could this be a #GCC bug?

RT @gromit, @adamw

#mbsync #gcc #fedora #bug #isync