291973 - TB ignores folders with "NoSelect" and "HasChildren"

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Pawel S. Veselov]

User-Agent:       Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040610
Build Identifier: 

Using dovecot 0.99.14, I find that TB doesn't work with subfolders.
Apparently, in maildir mode, dovecot maps folders to files, preserving
directory structure for subfolders. So, when TB issues LIST, dovecot says:

* LIST (\NoInferiors) "/" "Aligo"
* LIST (\Noselect \HasChildren) "/" "CDS"
* LIST (\Noselect \HasChildren) "/" "JSR"
* LIST (\Noselect \HasChildren) "/" "sparc"
* LIST (\NoInferiors) "/" "Amazon.com"

TB just shows "CDS" "JSR" and "sparc" as grayed non-selectable items in the 
subscription menu, not letting to open them. Changing the "Server doesn't
support folders that contain sub-folders and messages" option in TB does not
change the behavior. 

This bug is actually absolute opposite to 284312, where the problem was that
TB was attempting to issue mailbox commands on a pure folder.

Reproducible: Always

Steps to Reproduce:
1. Set up dovecot server with maildir and subfolders
2. Register an account, and open 'subscribe' menu
3. Check the subfolders.

Actual Results:  
Subfolders are grayed out and completely inaccessible even if there are
actual populated folders underneath.


Expected Results:  
Subfolders should not be subscribable/selectable themselves (Noselect), but they
should be expandable for subfolder subscritpion (Haschildren)

All I got from RFC3501 and RFC3348, is that they don't say whether \NoSelect and
\HasChildren can be together or not, however 3501 defines "NoSelect" as 
"it is not possible to use this name as a selectable mailbox", that doesn't
disallow it to have children.

Comment 1

[Pawel S. Veselov]

I'm sorry, the dovecot is set up using 'mbox', NOT 'maildirs', my bad.

Comment 2

[Pawel S. Veselov]

This was reproduced on TB 1.0.2

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.