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. My hopes where high when my company switched the server to outlook365, only to realize that the IMAP server is the _same_ implementation, but now shared among a larger user base, higher latency, and essentially 10 times slower. It's unbelievable how you could take the slowest, oldest IMAP server you can think of (uwimapd?), combine it with /any/ random MTA, and replace exchange with a 10 years old server and STILL increase throughput while actually be compliant to booth! Again, Idiots. > - i have no clue how to integrate this with the transaction system. > possibly, the log replay would also need some multiplexing > callback. Talking about transactions, how robust is mbsync transaction system in case mbsync itself is killed? 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. > as you can see, this isn't a project for a few hours, and the likelihood > that i'll embark on it myself anytime soon is about zilch. Thank you a _lot_ for this. Indeed, I feared it wasn't something I could work a weekend onto, but you digested the work in several pieces that look more approachable. I'll keep you updated. ------------------------------------------------------------------------------ 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
