martin f krafft <[EMAIL PROTECTED]> writes:
> also sprach Craig Dickson <[EMAIL PROTECTED]> [2001.12.21.0505 +0100]:
> > mkdir Mail/folder
> > mkdir Mail/folder/cur
> > mkdir Mail/folder/new
> > mkdir Mail/folder/tmp
>
> mkdir -p Mail/folder/{cur,new,tmp}
>
> :)
>
> > Seems to work well enough. Mutt is perfectly happy with such folders.
>
> and they are absolutely valid. maildirmake really just does all this.
> the reason why it should be used instead is because of abstraction -
> because you as a user should not even worry about the existence of
> {cur,new,tmp}: the implementation details are unimportant.
Another good reason is that maildirmake handles permission settings
correctly, depending on whether you make private or shared maildirs. If
you just use mkdir, you'll get world-readable dirs, which you probably
don't want.
--
Brian Nelson <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
http://bignachos.com
