search for: ___abc___

...ed dovecot tries to deal with them. I wonder why dovecot is not using a much easier approach and just uses a configurable prefix and/or suffix like .dir or ____ for directory names, e.g. INBOX -> ~/mail/inbox abc -> ~/mail/abc abc/def -> ~/mail/abc.dir/def or ~/mail/___abc___/def which would make all that trouble with .subscriptions and .index much more easier. In my eyes the Maildir++ layout is overcomplicated because of the heap of workarounds to the self-created problems. regards Hadmut

..., 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 ver...

...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...