On Wed Dec 18, 2024 at 21:29, Oswald Buddenhagen via isync-devel <isync-devel@lists.sourceforge.net> wrote: > On Wed, Dec 18, 2024 at 02:33:51PM +0100, Bence Ferdinandy wrote: >>it was probably not the best idea, but I moved computers, by coping all >>my >>maildir and isync config, but not the isync state (in retrospect, I probably >>should have done that). >> > yeah ... > >>I ran isync (1.5.0) and some emails got duplicated, but >>not everything and more heavily in Archive folders. Is this the >>expected behaviour? >> > no. i expect that there is some confounding factor. > maybe misleading sort order? > or some messages were never pushed up because of reasons?
There were probably messages never pulled, but who knows. Anyway, I'm now professional in mail de-duplication. > >>I was hoping that without zero state, isync would just rescan and >>match up everything nicely if slowly. >> > no, isync does not look at the content, not even message ids. > one could implement that as a fallback if one was so inclined ... > >>For future reference? Is copying everything, including state the >>preferred way of moving? >> > yes. > unless your connection to the imap server is faster then a local > transfer. then just sync up, and sync from scratch on the new box. Well, now I know :) Thanks, Bence _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
