On Sat, Jul 09, 2016 at 10:10:27PM +0200, Yuri D'Elia wrote: > On Sat, Jul 09 2016, Oswald Buddenhagen wrote: > > - 1. UIDVALIDITY change recovery > > - background: some servers (ms exchange in particular) like to > > change > > If I could punch the idiots behind exchange, I would. > i think that's politics, not idiocy. they implemented the imap gateway because customers pressured them, but they delivered the least they could get away with. the goal is of course making the experience as unpleasant as possible without being inacceptable, so people feel compelled to use their native outlook client (and windows) => more licence fees. and they don't even have to intentionally sabotage it - simply not assigning anyone to fixing it is sufficient.
> Talking about transactions, how robust is mbsync transaction system in > case mbsync itself is killed? > it's supposed to be robust to the degree that short write()s are atomic (the journal uses a line-buffered FILE*). that means that it should survive the process being killed, while a system crash may botch it. > I recklessly run mbsync under timeout(1), and noticed that in some > occasions I had to remove the journals. I didn't have time to look more > deeply though. > just the last lines of such truncated journals may give me enough of a clue. ------------------------------------------------------------------------------ Attend Shape: An AT&T Tech Expo July 15-16. Meet us at AT&T Park in San Francisco, CA to explore cutting-edge tech and listen to tech luminaries present their vision of the future. This family event has something for everyone, including kids. Get more information and register today. http://sdm.link/attshape _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
