> Sounds more like you just introduced a new self-created problem that would require yet another workaround.. ;-)
Definitely wrong. Appending .dir to directories and .folder to folder files keeps files completely distinct and name collissions are not possible. > But what was not clear from your mail, is what exactly you identified as "the problems" with standard Maildir++ setup? Having regular files filenames beginning with a . is a no-go and flawed by design. Extremely error-prone No serious designer would ever do that. Furthermore, it make it difficult to backup files from particular folder, since not in distinct folder (and thus not mbox-design). Even worse, both folders foo/bar and foo.bar both get the filename .foo.bar Maildir++-setup is broken by design in several ways. That's the problem with Maildir++. Appending smileys doesn't help. Hadmut On 24.08.2015 15:28, Maarten Bezemer wrote: > > On Sun, 23 Aug 2015, Hadmut Danisch wrote: > >> astonished to see, what problems come with Maildir++ and how complicated >> dovecot tries to deal with them. > .. > [fast fwd to "solution"] > >> INBOX -> ~/mail/inbox >> abc -> ~/mail/abc >> abc/def -> ~/mail/abc.dir/def or ~/mail/___abc___/def > > This would not work. > For example, how would you handle a folder named "abc.dir"? In your > scheme, that would end up as ~/mail/abc.dir which would still result > in a name clash. > How would you handle abc/def/ghi? Something like > ~/mail/abc.dir/def.dir/ghi or? That would not make it very workable > either. > > > >
