Framapiaf

1 message1 participant0 message aujourd’hui

Debacle<a href="https://masto.snoozetown.org/@ephzero" class="u-url mention">@ephzero</a><a href="https://framapiaf.org/tags/mu4e" class="mention hashtag" rel="tag">#mu4e</a> with <a href="https://framapiaf.org/tags/mbsync" class="mention hashtag" rel="tag">#mbsync</a> (package <a href="https://framapiaf.org/tags/isync" class="mention hashtag" rel="tag">#isync</a> on <a href="https://framapiaf.org/tags/Debian" class="mention hashtag" rel="tag">#Debian</a>)<a href="https://framapiaf.org/tags/Emacs" class="mention hashtag" rel="tag">#Emacs</a> <a href="https://framapiaf.org/tags/email" class="mention hashtag" rel="tag">#email</a>

Parleur<a href="https://mastodon.parleur.net/tags/isync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isync</a>, mon amour.

Yann Büchau :nixos:I tried <a href="https://fosstodon.org/tags/isync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isync</a> + <a href="https://fosstodon.org/tags/gitAnnex" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#gitAnnex</a> + <a href="https://fosstodon.org/tags/notmuch" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#notmuch</a> 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ß"Ready to synchronize T68i". <a href="https://mastodon.social/tags/brushedmetal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#brushedmetal</a> <a href="https://mastodon.social/tags/iSync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#iSync</a>

Parleur<a href="https://network.conquerworld.fr/@alexconquer" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@alexconquer</a> C'est un des outils du paquet <a href="https://mastodon.parleur.net/tags/isync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isync</a>.<a href="https://isync.sourceforge.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://isync.sourceforge.io/</a>Celui-ci en particulier permet la synchronisation de comptes IMAP, en ligne de commande. <a href="https://mastodon.parleur.net/tags/CLI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CLI</a>

Jarkko SakkinenI created a ticket for <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a> addressing the <a class="hashtag" href="https://social.kernel.org/tag/fedora" rel="nofollow noopener noreferrer" target="_blank">#Fedora</a> 40 issue: <a href="https://sourceforge.net/p/isync/patches/19/" rel="nofollow noopener noreferrer" target="_blank">https://sourceforge.net/p/isync/patches/19/</a>

Jarkko SakkinenI started my own fork of <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a> (or <a class="hashtag" href="https://social.kernel.org/tag/mbsync" rel="nofollow noopener noreferrer" target="_blank">#mbsync</a>)<a href="https://codeberg.org/jarkko/isync" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/jarkko/isync</a>It has now couple of commits:<pre><code>❯ git log --oneline -2 8ea62c9 (HEAD -> main, origin/main) fix: compile with -fno-lto f5782aa refactor: open code FORCEASYNC far and near parameters </code></pre>The first is the fix for crash in <a class="hashtag" href="https://social.kernel.org/tag/fedora" rel="nofollow noopener noreferrer" target="_blank">#Fedora</a>. The second open codes <code>FORCEASYNC</code>:<pre><code>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, ) </code></pre>I plan to do this for all of those, as it allows to cut some slack out from <code>bit_enum_get.pl</code>. That will lead to a roadmap where eventually the whole ugly script can be rendered out replaced with <code>BIT_UL</code> macro from kernel (msync is GPL 2.0 licensed).There is also a <a class="hashtag" href="https://social.kernel.org/tag/zig" rel="nofollow noopener noreferrer" target="_blank">#zig</a> 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.<a class="hashtag" href="https://social.kernel.org/tag/email" rel="nofollow noopener noreferrer" target="_blank">#email</a>

Jarkko Sakkinen(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 <a class="hashtag" href="https://social.kernel.org/tag/gcc" rel="nofollow noopener noreferrer" target="_blank">#GCC</a> bug? RT <a class="u-url mention" href="https://chaos.social/@gromit" rel="nofollow noopener noreferrer" target="_blank">@gromit</a>, <a class="u-url mention" href="https://fosstodon.org/@adamw" rel="nofollow noopener noreferrer" target="_blank">@adamw</a> <a class="hashtag" href="https://social.kernel.org/tag/mbsync" rel="nofollow noopener noreferrer" target="_blank">#mbsync</a> <a class="hashtag" href="https://social.kernel.org/tag/gcc" rel="nofollow noopener noreferrer" target="_blank">#gcc</a> <a class="hashtag" href="https://social.kernel.org/tag/fedora" rel="nofollow noopener noreferrer" target="_blank">#fedora</a> <a class="hashtag" href="https://social.kernel.org/tag/bug" rel="nofollow noopener noreferrer" target="_blank">#bug</a> <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a>

Jarkko SakkinenI found a modern actively updated alternative for <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a> (or <a class="hashtag" href="https://social.kernel.org/tag/mbsync" rel="nofollow noopener noreferrer" target="_blank">#mbsync</a>): <a class="hashtag" href="https://social.kernel.org/tag/m2sync" rel="nofollow noopener noreferrer" target="_blank">#m2sync</a>It is part of <a class="hashtag" href="https://social.kernel.org/tag/vomit" rel="nofollow noopener noreferrer" target="_blank">#vomit</a> project: <a href="https://sr.ht/~bitfehler/vomit/" rel="nofollow noopener noreferrer" target="_blank">https://sr.ht/~bitfehler/vomit/</a>Compared to the complexity of ~/.mbsyncrc, my config is now dead simple:<pre><code>cat .config/vomit/config.toml [kapsi] local = "~/.cache/mail/kapsi" remote = "mail.kapsi.fi:993" user = "jjs" pass-cmd = "pass show imap/mail.kapsi.fi" </code></pre>I love vomit!

Jarkko Sakkinen<a class="hashtag" href="https://social.kernel.org/tag/mbsync" rel="nofollow noopener noreferrer" target="_blank">#mbsync</a> always crashes here in <a class="hashtag" href="https://social.kernel.org/tag/fedora" rel="nofollow noopener noreferrer" target="_blank">#Fedora</a> (even when compiled from upstream): Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000055d33068a967 in sync_chans (mvars=0x7ffef80ee330, ent=<optimized out>) at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/main.c:906 906 char *sname = boxes[N] ? boxes[N][sb] : NULL; Any ideas? I used coredumpctl to discover this location but for comparative testing I also compiled the latest upstream of mbsync, and it crashes in the exact same location. <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a>

Jarkko SakkinenNow that I have <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a> working, the next thing I'm gonna do is to setup <a class="hashtag" href="https://social.kernel.org/tag/vdirsyncer" rel="nofollow noopener noreferrer" target="_blank">#vdirsyncer</a> to sync my contacts and calendar from <a class="hashtag" href="https://social.kernel.org/tag/icloud" rel="nofollow noopener noreferrer" target="_blank">#iCloud</a>, and access my contacts and calendar with khard and khal. <a class="hashtag" href="https://social.kernel.org/tag/email" rel="nofollow noopener noreferrer" target="_blank">#email</a> <a class="hashtag" href="https://social.kernel.org/tag/contacts" rel="nofollow noopener noreferrer" target="_blank">#contacts</a>

Jarkko SakkinenI'm pretty happy with <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a>. I used to use <a class="hashtag" href="https://social.kernel.org/tag/fdm" rel="nofollow noopener noreferrer" target="_blank">#fdm</a> but since my imap access is fast, it was not transparent enough to be worth of trouble. isync has sort of best of both worlds.

Jarkko SakkinenI used to use <a class="hashtag" href="https://social.kernel.org/tag/fdm" rel="nofollow noopener noreferrer" target="_blank">#fdm</a> for many years, last few I've simply used <a class="hashtag" href="https://social.kernel.org/tag/imap" rel="nofollow noopener noreferrer" target="_blank">#IMAP</a> access a Finnish server, an since yesterday <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a>. It gets less in the way than fdm (especially with verbatim folders) but still provides offline access and allows to use <a class="hashtag" href="https://social.kernel.org/tag/notmuch" rel="nofollow noopener noreferrer" target="_blank">#notmuch</a>, which integrated to <a class="hashtag" href="https://social.kernel.org/tag/aerc" rel="nofollow noopener noreferrer" target="_blank">#aerc</a>. :-) <a class="hashtag" href="https://social.kernel.org/tag/email" rel="nofollow noopener noreferrer" target="_blank">#email</a>

Jarkko SakkinenImproved my <a class="hashtag" href="https://social.kernel.org/tag/email" rel="nofollow noopener noreferrer" target="_blank">#email</a> workflow a bit with <a class="hashtag" href="https://social.kernel.org/tag/isync" rel="nofollow noopener noreferrer" target="_blank">#isync</a>. So the basic config in <code>~/.mbsyncrc</code> is:<pre><code>IMAPAccount kapsi Host <a href="http://mail.kapsi.fi" rel="nofollow noopener noreferrer" target="_blank">mail.kapsi.fi</a> User jjs PassCmd "pass show imap/mail.kapsi.fi" SSLType IMAPS IMAPStore kapsi-remote Account kapsi MaildirStore kapsi-local SubFolders Verbatim Path ~/.mail/kapsi/ Inbox ~/.mail/kapsi/INBOX Channel kapsi Far :kapsi-remote: Near :kapsi-local: Patterns * Create Both Expunge Both SyncState * </code></pre>Essentially only other change I had to do was repeal and replace sources in <code>~/.config/aerc/accounts.conf</code> (I was already using msmtp since many many years ago):<pre><code>[personal] source = maildir://~/.mail/kapsi outgoing = msmtp -a <a href="http://iki.fi" rel="nofollow noopener noreferrer" target="_blank">iki.fi</a> default = INBOX from = Jarkko Sakkinen <jarkko.sakkinen@iki.fi> copy-to = Sent [kernel] source = maildir://~/.mail/kapsi outgoing = msmtp -a <a href="http://iki.fi" rel="nofollow noopener noreferrer" target="_blank">iki.fi</a> default = INBOX from = Jarkko Sakkinen <jarkko@kernel.org> copy-to = Sent folder-map = ~/.config/aerc/folder-maps/kernel.map </code></pre>For the record <a href="http://kernel.map" rel="nofollow noopener noreferrer" target="_blank">kernel.map</a> (also existed previously unrelated to this change) is just: <pre><code>personal = INBOX INBOX = kernel </code></pre>I use this magic given that @<a href="http://kernel.org" rel="nofollow noopener noreferrer" target="_blank">kernel.org</a> routes to a sub-address of the same account.Have been planning to level up here for a long while so thought now is the time given tomorrow is first workday after holidays.

jtmoulia 🐁More struggles with <a href="https://mstdn.social/tags/offlineimap" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#offlineimap</a> email sync handling malformed spam (unicode in the headers). I'd found a hack with manually adding the offenders' UIDs to skip lists but manual intervention is a pain.Trying out <a href="https://mstdn.social/tags/isync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isync</a> (aka mbsync) instead and already impressed by 1) easy config, 2) useful and minimal UI and 3) speeeeed.isync's speed is hitting gmail IMAP quota issues, but that was a gig or so into a multithreaded sync -- so it goes.

Marcos Dione<a href="https://en.osm.town/tags/til" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#til</a>* <a href="https://en.osm.town/tags/isync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isync</a> / <a href="https://en.osm.town/tags/mbsync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mbsync</a> works very well, but you can't have your email pre-sync'ed with f.i. <a href="https://en.osm.town/tags/rsync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#rsync</a>. you have to let the thing sync all your emails and note it, otherwise you might end up with duplicated emails like me.

Fabio Natali<a href="https://fosstodon.org/@abcdw" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@abcdw</a>That's a great point and I very much agree on your list, those would be my top choices too indeed.Other projects that come to mind: <a href="https://octodon.social/tags/borg" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#borg</a>, <a href="https://octodon.social/tags/borgmatic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#borgmatic</a>, <a href="https://octodon.social/tags/autossh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#autossh</a> - not implying that they're not actively developed, just that they feel like solid components that I tend to set up and then rarely interact with.A bit more low-level and niche, but same for: <a href="https://octodon.social/tags/isync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isync</a>, <a href="https://octodon.social/tags/msmtp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#msmtp</a>, <a href="https://octodon.social/tags/direnv" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#direnv</a>.<a href="https://www.borgbackup.org/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.borgbackup.org/</a> <a href="https://torsion.org/borgmatic/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://torsion.org/borgmatic/</a> <a href="https://www.harding.motd.ca/autossh/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.harding.motd.ca/autossh/</a> <a href="https://isync.sourceforge.io/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://isync.sourceforge.io/</a> <a href="https://marlam.de/msmtp/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://marlam.de/msmtp/</a> <a href="https://direnv.net/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://direnv.net/</a>

... (FKA Gergely Nagy 🐁)Ended up going with <a href="https://trunk.mad-scientist.club/tags/isync" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#isync</a>, primarily because I haven't tried it before.I had good experiences with <a href="https://trunk.mad-scientist.club/tags/OfflineIMAP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OfflineIMAP</a> 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.

Recherches récentes

Options de recherche

Administré par :

Statistiques du serveur :

#isync