On Monday 18 June 2012 12.54:03 Jeroen van Meeuwen wrote:
On Monday, June 18, 2012 12:56:01 AM Timothy Murphy wrote:
> Rex Dieter wrote:
> >> When I click on a top-level account in KMail on an IMAP client,
> >> the File->New->Add Folder option is greyed out,
> >> although it is available to create a sub-folder of an existing folder.
> >
> > Maybe seeing this?
> >
> >
https://bugs.kde.org/show_bug.cgi?id=218935
>
> Thanks.
>
> I saw someone (possibly you?) mentioned another bugzilla,
> which mentioned that the problem was solved
> in a version of KMail coming shortly.
My colleague Christian Mollekopf (in CC:) will work / has worked on
resolving this issue / these issues, IIRC. I'll let him speak for himself.
Hey,
A workaround has been commited already
(
https://bugs.kde.org/show_bug.cgi?id=292418, fixed in 4.8.5), which should at
least allow creating toplevel folders, however acl's and such are still not
checked properly.
I opened a bug for that:
https://bugs.kde.org/show_bug.cgi?id=302139
Cheers,
Christian
A client needs to take two things into account for this
"thing" that is
root- level folders and sub-folders, which are;
- First, the result of the NAMESPACE command. The response to this command
lists the roots and hierarchy separators for personal, 'other users' and
zero or more 'shared' namespaces.
The traditional root for one's personal namespace has been INBOX, but
evolvement from the legacy NNTP name-space and convention has resulted in
both the use of alternative namespace (INBOX is a root-level folder, but
sub- folders of INBOX are presented as root-level folders as well - they
are often still folder/sub-folder on the mail server's filesystem), as well
as the '/' hierarchy separator (so mailbox names can contain dots '.'
characters).
- Second, as a consequence of using alternative namespaces, "INBOX" cannot
contain any "sub-folders" - "sub-folders" being presented as
root-level
folders and all. To this end a \NoInferiors flag is included in the LIST /
LSUB command responses, indicating no child folders can be created.
I hope this clarifies a bit, where things can go wrong.
Kind regards,
Jeroen van Meeuwen