Hello Oswald, On 05/08/2018 at 09:35 Oswald Buddenhagen writes:
> On Mon, May 07, 2018 at 05:34:00PM -0400, George Clemmer wrote: >> On 05/07/2018 at 05:55 Ciprian Dorin Craciun writes: >> > On Mon, May 7, 2018 at 3:05 AM George Clemmer <myg...@gmail.com> wrote: >> >> So ... this led me to wonder ... Would using a "stable" name based >> >> on a checksum be a useful improvement? Naturally, since I am a Git >> >> addict, I am thinking of 'git hash-object' ;-) >> > >> > >> > Myself would think this would be a lovely idea, however due to the >> > `X-TUID` header it would be pointless... >> >> I haven't had a chance to look at `X-TUID` but I wonder if a hashed >> file name couldn't replace it. >> > the whole *point* of the tuid is that it is random, so even duplicated > messages (which you could produce with your MUA) are reliably > propagated. This sounds like a "corner case" that is not important to me. I think I would rather have the files in my local Maildir be identical to Gmail files. IIUC, they now differ by the addition of the X-TUID. Is that correct? > but the t in tuid stands for temporary, and you can just remove them > after the sync is done. caveat: per imap spec, that's illegal, because > messages shall be immutable. violating this particular aspect is > unlikely to cause problems, though, especially when the maildir is > actually never accessed via imap. Is X-TUID central to the isync design? Could the option to turn it off (at the risk of duplicates not being propagated) be easily added? TIA - George ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
