krjw wrote: > +-- On 29082002 12:16:11 +0000, darren chamberlain uttered: > | * krjw <[EMAIL PROTECTED]> [2002-08-29 11:57]:
>>> 1) Firstly, does mutt support or will mutt ever support extended >>> maildirs? I've never seen extended maildirs 'till I started using >>> maildrop, but they're kinky. They allow for folders-within-folders >>> which is very handy. >> I don't know, but have you tried it? It seems like it would work. > Ya. I have a test maildir FOO, with a 'folder' bar, and bar has yet > another 'folder' called blah. The structure looks like this (as created > with the "maildirmake" prog that comes with maildrop): > > FOO > FOO/tmp > FOO/new > FOO/cur > FOO/.bar > FOO/.bar/tmp > FOO/.bar/new > FOO/.bar/cur > FOO/.bar/maildirfolder > FOO/.bar.blah > FOO/.bar.blah/tmp > FOO/.bar.blah/new > FOO/.bar.blah/cur > FOO/.bar.blah/maildirfolder > > (maildirfolder is a regular file.) > > mutt sees FOO but has zero knowledge of bar or blah AFAICT. What if you change folders to .bar or .bar.blah/ ? I'm pretty sure that should work fine. There are a few approaches to the (annoying, IMHO) maildir++ approach of courier. 1) there is a patch for maildir++ support in the archives. the author says it's a total hack, but it should work. 2) make symlinks from ~/Mail/ or whatever to the courier folders (it Mail/bar/blah is a link to ~/Maildir/.bar.blah/ (or do it the other way around). 3) Use mutt via IMAP (folders will be in INBOX.) 4) call them by their regular name, but set mask="^\\." so that you see them in the browser. -- Will Yardley input: william < @ hq . newdream . net . >
