Abdó Roig-Maranges

Oh, that migration thing was precisely to move md5 sums to a nametrans-ed folder name, in order to avoid this exact problem. See c84d23b.

>If we look at the bigger picture, I'd say that the FMD5 is always wrong. IMAP provides the UIDVALIDITY for the folders and this is what Offlineimap should use. I'm...

> If we change the FMD5 meaning (which would make sense), I think we should start versioning the filename. Which new meaning do you refer to? I'm not really sure...

> I do believe the best FMD5 is the remote fully qualified folder name. Agreed, in principle. In practice, I'm not convinced it is worth the pain. In a sense,...

> Force the reversed nametrans to be correct regarding the remote nametrans. That's the best IMHO. You mean, constrain if it exists, but allow for no local nametrans, isn't it?...

> Most importantly, as soon as the name of whatever is used for the hash changes (sometimes due to the user, sometimes due to code changes), the users are exposed...

I would say the mission of the FMD5 is invalidate uids if you do something locally that can cause uid clashes on the remote, and lead to a fake synced...

I'm landing here only now due to @nicolas33 mention. I'm not sure what this issue is about anymore... Regarding the certificate problem originally reported, yes, with ssl, we need to...

At the time I wrote this feature, I looked at a couple of mail user agents (mu4e and mutt) and stuck with a choice that made them all happy. [This](http://does-not-exist.org/mail-archives/mutt-dev/msg08249.html)...