Michael Tatge wrote: > Michal 'hramrach' Suchanek ([EMAIL PROTECTED]) muttered:
> > I found these problems for which I know *no* 100% workaround: > > > - I'm unable to browse Maildirs reliably. They can contain both messages > > and subfolders but when I enter a maildir the message index is > > displayed automatically > This is perfect behaviour. A Maildir should not have subdirs other then > cur, new, tmp. > If you need subdirs, use normal directories. [...] > > (should be handled the same way IMAP browsing is described in > > documentation). > > - subfolders in Maildirs arent displayed in browser - start with dot > > (set mask to show .subforder and ignore new|cur|tmp) - suggest > > maildir_mask > > IMAP folder may have subdirs. Maildirs not. perhaps the OP is confusing courier's 'maildir++' documentation with Maildir itself. courier imapd does actually allow subfolders, and this is the default. folders start with a '.' by default. you can put: set mask="^\\." to show only folders starting with a leading dot. personally, i've found that the better way to use both courier IMAP and local Maildir folders is either to put your actual mail folders in ~/Mail/ and then create symlinks from ~/Mail/foo/ to ~/Maildir/.foo/, or to do the opposite and link ~/Maildir/.foo/ to ~/Mail/foo/. courier's strange way of doing things makes sense when the only access to the system is via IMAP, but it's a pain to use with local folders. -- Will Yardley input: william < @ hq . newdream . net . >
